Hi Douglas, Glad I stumbled upon this thread as we're currently working towards using Web Components with Sass developed with an OOCSS mindset (BEM class naming conventions etc) and I'm struggling slightly to see how I will be able to fit the two together at the moment :S.
Broadly speaking it seems like Web Components have tried to tackle the similar issues with CSS that the likes of the OOCSS/BEM/SMA conventions are tackling. It would be great to keep in contact to see how you get - maybe we can swap some notes? Rob/Eric - can you keep me posted on how you guys are getting on with tackling this issue internally? I'd love to be able to help some how. *Just to note...I am not using Bootstrap, but my own custom set of tools I've built up over the past 2/3 years (files are broken into small modules and placed within a file structure similar to this: tools, base, objects, components) and are compiled at present into a single CSS* Cheers, Dan On Tuesday, 27 May 2014 23:51:12 UTC+1, Douglas Hubler wrote: > > > On Tuesday, May 27, 2014 4:42:56 PM UTC-4, Elliott Sprehn wrote: >> >> I would definitely suggest breaking up your CSS into chunks specific to >> each component. We need to break free of the idea of having one massive CSS >> file and one massive JS file like we did in the past. With web components >> write small css files and embed them inside your self contained elements. >> > > fair point, maybe I'll strive for something in-between one css and one css > per polymer-element. Some logical grouping. > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/a60dc10e-9982-48c0-928d-cc9e1011c0fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
