re: What should production CSS look like? Share your layout-to-web workflow VIEW POST

re: i think mattia is talking about components as in javascript classes or functions that render a single visual component, like you find in react, ang...

Exactly. But non only with vue/react/svelte etc.. i trust it as mindset. An approach that you can apply even with plain html/css/js and drop the monolithic frameworks approaches that are born many years ago to fix different problems.

Thank you @worc for explaining. Your description makes a lot of sense. I like the idea of writing super lean plain html/css/ vanilla js... but I would need to master JS first. Then would come the question of should I CSS functions or still use SASS? I don't want to be obsessed with rigour but I'm trying to understand what's a professional standard. I'm both studying to "pass the test", but also want to self-improve from what was a previously anti-technical, anti-framework, anti-rigour kind of artistic point of view.

correction: Makes a lot of sense for reusable components/features*, and large scale applications, which I should be gearing up to get used to

Yes. But this approach and mindset can be applied even on small website. Every html elememt and composite block is a "reusable component" by default.

styled-components is a good working example in the react ecosystem. @jen chan, in general, you don't need to use sass if you're building CSS blocks in javascript. javascript gives you access to variables and functions and extensibility natively. it's probably not the best looking syntax around, but i've seen it help a ton in keeping CSS definitions from leaking across components and keeping the scope of a styling problem/solution very narrow.

code of conduct - report abuse