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
{{ message }}
This repository has been archived by the owner on Sep 16, 2019. It is now read-only.
In the latest changes the main css output has been renamed from app.css to foundation.css. Maybe it's just me but foundation.css sounds like the Foundation css rather than the entire theme css that also includes my own custom css. I'm just curious, why the change?
Anyway, now that it is changed, should bower.json also change? It seems to refer to the old names of css and js output files:
"main": [
"css/app.css",
"js/app.js"
],
The text was updated successfully, but these errors were encountered:
Yes they all have been updated recently....bower, grunt....thus compiling to different folders thus paths also changed in functions.php. I'm currently sticking to the previous version before updating as it would mess with my in progress work.
@Aetles : I noticed that Zurb have changed the naming of app.css to foundation.css in the main repository for Foundation. I suppose this is to avoid confusion between Foundation for Sites and Foundation for Apps? It's not a big deal in a larger context, but I think it is a good idea to stay close to the conventions of Foundation.
Regarding your comment on the bower.json file, you're right. Well spotted, thanks! Fixed 06d60b6
In the latest changes the main css output has been renamed from
app.css
tofoundation.css
. Maybe it's just me butfoundation.css
sounds like the Foundation css rather than the entire theme css that also includes my own custom css. I'm just curious, why the change?Anyway, now that it is changed, should bower.json also change? It seems to refer to the old names of css and js output files:
The text was updated successfully, but these errors were encountered: