Is there any value in people who cannot write JavaScript?
Mandy Michael
16K128

Agree with this sentiment, there’s a crucial role on a product concerning styling and accessibility. However, one thing that’s worth mentioning is applications written entirely in JavaScript (e.g. ReactJS with embedded styles — CSS in JS) are not excluded. In fact, they need this role as much as a traditional server side markup sites with no JavaScript.

Taking the example, a site written with ReactJS may not have any HTML or CSS. The CSS engine and browser DOM are managed by React through the browser API. At the end of the day, HTML and CSS are just serialized formats that the browser understands to feed into its own API. A well structured ReactJS application should have special modules where global styles are kept. It should also have well defined layout components. Just because these styles are in JavaScript objects it doesn’t mean they can’t be separated from the application logic. These styling modules will contain a list a CSS rules as JS objects. CSS forces this approach (a separation of technology), JS-only projects need to adopt the same good practices.

So, I think it’s dangerous to label people as “CSS/HTML” engineers. It’s better to focus on their role as designer/styling/accessibility and layout. That may mean editing JavaScript objects that model those styles, but the properties are the same.

In addition, consider mobile applications written using ReactNative. There’s no CSS, again the styles are typically written using JavaScript. The rules might be a little different, but the role is the same.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.