8 ms·
>Does it imply some web component framework? Not particularly. You can use pretty much any modern framework, they are all using a component based architecture
by aphextron 8y ago
>Does it imply some web component framework?
Not particularly. You can use pretty much any modern framework, they are all using a component based architecture for the most part. Vue, React, Polymer, even native web components are usable now. Here's an example of how Ember does it:
https://github.com/ebryn/ember-component-css https://github.com/ebryn/ember-component-css
It's just about breaking down your pages and views into small components which can be reused and maintained separately. Instead of having one giant stylesheet with a deep inheritance of cascading classes, you just have a a bunch of components that are imported and namespaced by the compiler. That extra layer of abstraction gives you the ability to organize your project in a way that isn't beholden to the specific quirks of CSS, and removes the mental burden of things like SMACSS from the developer.
- vanadium 8y agoThis is easily done using SASS components as well. No framework needed.
- kakarot 8y agoIt depends on how you want to structure your app. If you want all stylesheets living under src/stylesheets or if you would rather have them each live inside a component folder. The latter allows for better portability of components but you generally will need a build system.
- vanadium 8y agoAll of our components are contained in a folder specific to that component, and include the JS (Vanilla ES6), SASS, and template markup.