[jbob2000]

The component paradigm that react is built around is all about working with very small objects, where everything you need for that component is in one file. It's a fantastic model when you are working with a complex interface that has many components to it. It's a paradigm that needs to be managed and used carefully though, otherwise you'll end up with massive 2000 line files.

I never thought there was a separation between JS and CSS, that sounds a little outdated, to be honest. As a front-end developer, I would be expected to do JS and CSS.

[xirdstl]

Where I work, we're a small dev team of a few full stack developers and a designer. Our designer does the CSS, and the devs the JS. The separation works well enough for us. YMMV.

[qudat]

So anytime the designer makes a change to the structure of the application, where HTML element changes are required, do they send you a request so you can change it?

It seems odd to only allow the "designer" to manipulate properties of elements and not the elements themselves. If they are allowed to modify DOM elements then in the React world, that is manipulating JS. For us the important separation is at the component level, which includes everything that component needs to render and function (HTML, CSS, JS).

[xirdstl]

I was unclear about that part. The designer will edit the HTML also, which is outside of JS.

We are not using React.

[airnomad]

I'd say CSS is part of a stack for a long time now.