How to style a modern web application

Jan 20, 2021☕ 4 min read

I did a Twitch stream not so long ago, showcasing the main different ways (that I know of) to style a modern Next/React application. The result of that stream is a repository I created on my GitHub account, styles. If you want to check its code, the components I'm talking about are there, as an example of the different styling methods.

On the stream, I created a Next template app using create-next-app, and then I took the different ui components in pages/index.js and moved them over the components folder. There, I used different ways to apply styles to each individual component.

I don't think there is a method that is better than the others, but here are my opinions (pros and cons) on each one:

CSS Modules

components/card uses CSS modules, supported by Next out of the box. It's just a CSS file with a .module.css extension.

Simple solutionCSS syntax can get longer/more verbose
No extra dependenciesYou may lose some special functions
Avoids class collisions without using BEM or other ugly approach.

SCSS Modules

components/footer uses SCSS modules, a twist to the original CSS modules. SASS is a meta-language on top of CSS, and SCSS is an extension of the syntax of CSS, so it's a SCSS file with a .module.scss extension.

This just requires sass to be installed as a project dependency.

Still a simple solutionStylesheets are still separated from the code
Only one (light) dependency, no extra configurationYou may have duplicated code for similar styles
SASS is cleaner and better structured than CSS

Tailwind CSS.

components/grid uses TailwindCSS.

Tailwind CSS is a so-called "utility-first" CSS framework, which means that every CSS class is a low-level CSS composition. This allows simplification and standardization of UI components, but CSS classes can be quite long (e.g. "w-32 h-32 md:w-48 md:h-auto md:rounded-none rounded-full mx-auto").

Design system already built for you, with expandability/customization in mindAs the classes can be long, the code can grow exponentially if it's not properly fragmented.
It's fully compatible with other CSS methods, and you can use @apply to use Tailwind classes with your own stylesIt's not as powerful as other solutions, and you may need to add a lot of classes and/or custom CSS on top for advanced stuff.
All the code and styles live in the (React) component.

Styled components.

components/main uses styled-components.

Styled components is a library that uses tagged template literals to style your components, that is, inline CSS in JS. You can see there's only one file for the component, for the presentational component and its style.

JS and CSS live together, simple/cleaner file(s)Again, mixing all together adds lines of code and complexity. You can solve this by still separating the styles in a separate js file.
You can have access to props in the CSS properties, and create complex logicSometimes code editors don't highlight the syntax of CSS-in-JS or CSS inside a template string, as the file doesn't have a .css (or similar) extension.

This is all my very limited and personal opinion with all the different solutions I tried so far in React and Nextjs applications. Please clone the repo, check the components, and try for yourself! You can let me know your thoughts on Twitter.