2020-07-31
1044
#css
Ogundipe Samuel
22732
Jul 31, 2020 ⋅ 3 min read

A guide to theming in CSS

Ogundipe Samuel Software engineer and technical writer.

Recent posts:

react children prop how to properly type

How to type React children correctly in TypeScript

Learn modern best practices for typing React children in TypeScript, including ReactNode, PropsWithChildren, ComponentProps, and why React.FC is no longer recommended.

Ohans Emmanuel
Dec 19, 2025 ⋅ 7 min read
complete guide to internationalization next js

The complete guide to internationalization in Next.js

Learn how to internationalize Next.js apps with Lingui and next-intl, covering App Router, RSC, routing, locale detection, and dynamic language switching.

Ivan Vlatkovic
Dec 19, 2025 ⋅ 13 min read

Vite vs. Webpack for react apps in 2025: A senior engineer’s perspective

Vite vs Webpack in 2025: a senior engineer’s take on performance, developer experience, build control, and when each tool makes sense for React apps.

Peter Aideloje
Dec 19, 2025 ⋅ 3 min read
vitest 4 adoption guide

Vitest 4 adoption guide: Overview and migrating from Jest

Learn how Vitest 4 makes migrating from Jest painless, with codemods, faster tests, native ESM, browser testing, and a better DX.

Onuorah Bonaventure
Dec 18, 2025 ⋅ 15 min read
View all posts

5 Replies to "A guide to theming in CSS"

  1. Thanks a lot for this amazing article. Before this article theming concept was just a nightmare for me. But Man u nailed it.

  2. Thanks for the great article! A couple confusing parts:
    – You write “ N/B: When declaring CSS variables, the syntax is **–**”… I would remove the asterisks as it’s unclear for beginners if asterisks are actually part of the syntax of your custom way of highlighting the double dash
    – “ perfect for creating theme0aware websites” the 0 should be a hyphen

  3. Thank you for this very informative post! I have to admit, however, that I spent quite a few moments trying to decipher your code for the white text/black text example. It was confusing because the ‘white text’ is actually black and visa-versa. I had my eyes crossing before I realized that. Perhaps you should change the white text to say “Black Text” (since it is) or simply take away the ‘Text’ part of the string. But great content!

Leave a Reply

Hey there, want to help make our blog better?

Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.

Sign up now