Reasonable System for CSS Stylesheet Structure

Re:Reasonable System for CSS Stylesheet Structure by at-fates-hands on Tuesday November 03, 2015 @12:01PM (#10500812)

Naming conventions seems to be old school now that virtually everything is being done with JS.

Using webpack's css-loader changes the game completely as pointed out by Mark Dalgleish here:

https://medium.com/seek-ui-engineering/the-end-of-global-css...

Writing maintainable CSS is now encouraged, not by careful adherence to a naming convention, but by style encapsulation during development.

I'm sure there will continue to be more JS solutions to getting rid of CSS naming conventions, since it seems everything is being done with JS these days.

[ Parent | on HN ]

Re:Reasonable System for CSS Stylesheet Structure by kevin_thibedeau on Tuesday November 03, 2015 @12:35PM (#10501090)

At which point you no longer have graceful degradation when JS is disabled. Web "designers" need to stop breaking the web with their code spew everywhere ruining the basic functionality of HTML and CSS.

[ Parent | on HN ]

Re:Reasonable System for CSS Stylesheet Structure by jackmoore on Tuesday November 03, 2015 @01:10PM (#10501335)

Sure you can... there is no reason why those JavaScript styles can't be outputted to a css file in your preprocessing step.

[ Parent | on HN ]