CSS-Tricks Redesigns Its Site and Revamps Content Navigation

CSS-Tricks has previewed a site redesign with updated reference navigation, a reworked WordPress theme, and new development tooling. A detailed breakdown is promised for later.

· 5 min read · 4 comments

On November 6, 2026, CSS-Tricks told its RSS subscribers about a soft launch of its site redesign. The announcement covers more than a new look: the team has updated the pages people use to find content, reworked the WordPress theme, and refreshed its development tools. It does not say exactly when the changes went live. A detailed breakdown and comparison with the previous design are promised for Monday.

What’s Changed for Readers

The site now has a theme switcher and a cream-colored light theme. CSS-Tricks was previously mostly dark, although article backgrounds were white. The brief announcement does not explain how the switcher works or whether it remembers a reader’s choice on their next visit.

Another noticeable detail is the Jawbreaker texture. The author of the update named it after a colorful candy he loved as a child; the motif now appears throughout the site. It is too early to tell whether it helps readers find their way between sections or simply gives the design character: a comparison with the previous version has yet to be published.

The biggest changes are to the pages readers use to find reference material. Almanac has been rebuilt as an index of CSS features, designed to get readers to the topic they need quickly. The Guides page now has a featured guide, a section for new and updated guides, and a grid of the remaining content organized by category below. These are two different ways to organize a large archive: an index and curated topic collections.

On author pages, the sidebar has moved from right to left. The photo and bio now sit in that column, so articles start higher up the page. It is a small change, but it affects an important step for readers: moving from information about the author to the article itself.

What’s Changed Inside the Theme

The redesign also involved reviewing a theme that had accumulated elements from earlier versions of the site over 19 years. The author of the announcement says he found this legacy material and began clearing it out. He has not yet explained which specific decisions had to be revisited.

The development workflow, which was about five years old, has been updated too. The announcement lists Prettier, GitHub Actions, automatic file version updates for cache busting, and a tool it calls “Styleint.” We are keeping the source’s spelling: a single preliminary announcement is not enough to confidently change it to the name of another tool.

After the Sass rework, the CSS shrank from 180 to 169 KB, and from 31.7 to 24.6 KB compressed. The author does not consider the reduction huge, but does not dismiss it either. The announcement gives no load-time data or other site performance metrics, so it is too soon to draw conclusions from those figures about speed for visitors.

To make the design more consistent, the team added semantic tokens for colors, fonts, text sizes, and other recurring values—the foundation of what the author describes as something like a design system. Fonts and text styles in the WordPress admin area also received minimal styling connected to the public-facing site. That is not a new feature for readers, but it is part of the broader work on the theme.

Separately, the author asked Claude to help with a comprehensive security review. He asked the tool to examine recent WordPress security release notes and identify places where the theme could be strengthened in light of platform changes. The announcement includes neither a list of issues found nor a list of fixes. Mentioning the review does not, by itself, confirm that the risks have been addressed.

What This Means for Content Sites

For site owners, this example helps separate the jobs a redesign needs to do: visitors need clear paths to content, while the team needs a theme that is easy to maintain. Marketers and editors may want to look at how Almanac and Guides are organized; developers, at how the team is dealing with accumulated code and shared design rules. For now, though, this is a description of changes, not proof of results: CSS-Tricks provides no data showing that readers are finding what they need faster.

My Take: The Path to the Content Comes Before Decoration

I like that the announcement discusses guides and reference pages alongside color and texture. For a content site, that is the right balance: a distinctive visual element works when it supports the content rather than distracting from it. I would judge the redesign first and foremost by how easy it is for readers to find what they need. The promised comparison with the previous design should make it easier to form a more informed opinion.

I am comfortable with Claude’s involvement in the review, but I would not expect too much of it. A tool like that can suggest where to look, but it cannot replace an understanding of the context or the judgment of the people responsible for the theme. I would be interested to learn from the full breakdown exactly what the team changed after the review; the preliminary announcement does not answer that yet.

Sources

Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.

  1. RSS Club: CSS-Tricks Redesign Preview css-tricks.com

About the author

Ola Nowak

Web designer and art director

I design websites for cultural and small commercial projects in Kraków. I often help teams agree on what can be simplified without losing meaning.

All posts by the author

Leave a comment

Not published. We’ll send a link to confirm your comment.

No links or ads. Your first comment is published after review. By sending a comment you agree to the privacy notice.

  1. One small thing I’d love to see in the promised breakdown: how the new reference navigation works on a narrow screen, especially alongside the theme switcher. I’m experimenting with content-heavy layouts for class, and mobile navigation is where a tidy desktop redesign can get tricky fast 😅

    1. a narrow-screen walkthrough would be useful; desktop nav has a way of looking perfectly innocent until the theme switcher joins the queue

      1. I’m not sure the theme switcher necessarily makes the mobile nav more complicated; if it’s kept out of the main navigation flow, the reference links are still the real constraint. I’d be more interested in seeing whether the reference section stays easy to browse on a narrow screen.

    2. @noorvanbeek, on a content-heavy project I worked on, putting reference links and the theme control in one mobile menu made the menu feel crowded, so we tested them as separate entry points instead. For CSS-Tricks, I’d check whether readers can reach the references quickly without opening the theme switcher by mistake.