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:

chatgpt atlas for developers featured image

How to use ChatGPT Atlas for frontend debugging, testing, and more

Learn how ChatGPT’s new browser Atlas fits into a frontend developer’s toolkit, including the debugging and testing process.

Emmanuel John
Nov 20, 2025 ⋅ 10 min read

Why composition – not reactivity – leads UI’s future

Users don’t think in terms of frontend or backend; they just see features. This article explores why composition, not reactivity, is becoming the core organizing idea in modern UI architecture.

Oscar Jite-Orimiono
Nov 20, 2025 ⋅ 6 min read
the replay nov 19

The Replay (11/19/25): React 19.2 async, GitHub Octoverse, and more

Discover what’s new in The Replay, LogRocket’s newsletter for dev and engineering leaders, in the November 19th issue.

Matt MacCormack
Nov 19, 2025 ⋅ 33 sec read

React 19.2: The async shift is finally here

Jack Herrington writes about how React 19.2 rebuilds async handling from the ground up with use(), , useTransition(), and now View Transitions.

Jack Herrington
Nov 19, 2025 ⋅ 5 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

Would you be interested in joining LogRocket's developer community?

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