Major CSS file include problem in the main Yeoman-Angular demo

[Muzietto]

The celebrated "Let's scaffold a web app with Yeoman" demo is slowly revealing itself as the anteroom to a world of pain.

After hacking across repeated bower hangups while loading jquery and other 5MB (!!!) of apparently indispensable stuff, I fire the server and retrieve the following, mangled page.

I've been able so far to retrieve the following CSS file from a public working example of the same demo and inject it using good old Chrome Developer Tools between two <style> tags in the head of the doc.

Page looks now as shown in the codelab pages. But file styles/site.css is sorely missing from the app I created following the instructions on the Yeoman site.

Needless to say, as soon as I refresh my page at localhost:9000, I lose the good CSS.

After having to manually installing a plethora of dependencies required by the mission-critical grunt-cdnify task (obviously not specified inside its package.json), I've managed in some way to run a complete grunt build operation. Hacked a few tags in the head of index.html, but still the CSS file is not included. Ended up chucking manually the <style> tag inside index.html, just to be able to get ahead of the CSS issue.

I hope I'll be able to understand how to make that file known to the build mechanism and automatically included in the page.

In the meantime, please verify and comment on this issue: is or is not the homepage in the app looking as nice as it should? Is the file styles/site.css present in the scaffolding built by Yeoman?

[Muzietto]

Adding up apparent Yeoman glitches in the demo: I had to copy manually directory fonts from the bootstrap area into the app area to get the glyphicons going, as I am used to do when I do the config things myself.

[samfearn]

Can confirm I have the exact same problem as reported by @Muzietto

[samfearn]

@Muzietto see http://stackoverflow.com/questions/31015812/grunt-wiredep-not-injecting-bootstrap-css-files-in-yeoman-angular-tutorial.

I added the code there to the bower file and now it works fine.

[luis-miguel-goncalves]

same issue with a clean install on a mac OS X Mavericks.
Solved adding the site.css to the index.html supplied by @Muzietto