You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.