This repository has been archived by the owner on Jun 27, 2022. It is now read-only.
Make custom.css easier to preserve #38
Assignees
Labels
Comments
|
What about a half-way house where you include a custom.template.css file and instructions to rename it the first time? |
clinkingdog
changed the title
|
Yep, that's a nice one - description updated. Another alternative that occurred to me was to change the |
This was referenced Oct 24, 2017
Open
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Although it's nice for the zip to provide an empty custom.css file the first time the prototype is built, it's actually unhelpful afterwards because if it's unzipped over an existing version with stuff added to custom.css, it overwrites that stuff with an empty file - potentially losing a lot of valuable work.
Instead the zip should provide an empty custom.template.css, with text content advising the user to rename it to custom.css in order to use it.
The
<link>in the HTML<head>should then continue to point to custom.css, rather than the template one.The text was updated successfully, but these errors were encountered: