From realignment to release
Rather than beginning on an empty design canvas and an empty code editor, the v18 work started from the existing site and pushed things around — though enough things moved that nearly every file was touched, which is why it earned the version number. As ever, the process opened in a design tool: three or four Figma passes, with a return visit once building was underway to flesh out the footer.

Once the visuals were roughly settled, the work moved into code, where the remaining decisions — considerably more of them — were made. The final result stays close to the mockups but differs in a number of details.
The organising idea: simplification
The 20% simplification at the core of v18 isn't obvious at a glance. The header lost its dedicated mobile version and its open/closed state logic; in v18 it is a handful of links that wrap to the next line on small screens. A "back to top" link appears in the footer once the reader has scrolled away from the top, driven by IntersectionObserver — the same detection that "spins the star" on the way back up. The header is expected to be one of the areas that keeps evolving as v18 matures.

Search followed the same pattern. Where v17 had open/closed states and bespoke result templates, the site now relies fully on Jetpack Search and simply opens it when the search icon is clicked. Because that search is JavaScript-powered, the trigger doubles as a valid hyperlink to Google results for resilience.
<a
href="https://www.google.com/search?q=site:css-tricks.com%20layout"
class="jetpack-search-filter__link"
>
<span class="screen-reader-text">Search</span>
<svg> ... </svg>
</a>

v17 had carried several page layouts (sidebar left or right) and header styles (including video in the header); now there is largely one of each.

The footer, which in v17 sprawled across separate sections for the newsletter form, social media, related sites and more, is compacted into something more traditional.

Cards likewise collapse to one base look and template for articles, videos, guides and so on, with slight variations depending on whether an author, tags or a call-to-action apply. The main variant is the "mini" card, used mostly consistently across popular articles, the monthly mixup and related-article units inside content.




Newsletters were simplified too: /newsletters/ was a landing page in v17 with the latest issue in a sidebar, while now it redirects to the latest newsletter, readable like any other piece of content, with navigation to past issues.

Featured images built for sloppiness
WordPress's one-featured-image-per-article concept is in use here, and it integrates naturally into other systems — it becomes the social media image automatically, for instance. v17 used it as a subtle background-image. A perfect site might pair a perfect content strategy with an exactly matched featured image for every article, but this isn't that world, so the design embraces any image dropped into it. A site-branded gradient is laid over the top and mix-blend-mode'd onto it so they all feel related; otherwise they are simply sized and cropped as needed. The images appear across many contexts around the site.





CSS, weight and performance
Comparing the CSS between the two versions with help from Project Wallace:

Minified and Gzipped, the main stylesheet comes to 16.4 kB. That may not match the smallest possible all-utility stylesheet, but it is not a size worth worrying about — particularly since it trended downward with little deliberate effort.
The site is not built for maximum speed. If speed were the top priority, the resource load would be cut first, at the cost of making the site less fun; instead the goal is a relatively fast site that stays visually rich. A lighter, opt-in version of the site enabled through standards is a possible direction down the road. The weight breaks down as follows:
- Images are the largest cost, with most pages carrying 10+ of them. They are served from a CDN, in an optimized format, sized with the responsive images syntax — a good start rather than a finished job.
- JavaScript totals roughly 180 kB. Jetpack Search is the weightiest module, and a polyfill it appears to load should be checked for removal. jQuery is still in place but slated for removal in the next round, since most of the code is written in vanilla JavaScript anyway. Google Analytics accounts for some, and the rest are (ironically) small scripts for performance or advertising.
- Fonts add about 163 kB, with no particularly fancy loading strategy.
All three are targets for future improvement. Even so, the Desktop Lighthouse report is respectable:

Those numbers come from the homepage, one of the heavier pages because of its large content grids. Several best practices remain in place:
- Everything is served from global HTTP/2 CDNs and cached
- Assets are optimized, minified and combined where possible
- Assets and ads are lazy-loaded where possible
- Premium hosting
- HTML over the wire plus instant.page
SpeedCurve reports run before and after the launch brought encouraging news:

The hope is that browsing the site, and returning to it, feels snappy.
Type, accessibility and housekeeping
All type remains Hoefler&Co.

Article typography is largely untouched, since it was one of the last design sprints of v17 and it landed somewhere worth keeping. With clamp() now available, though, much of the site uses fluid typography — headings, for example:
font-size: clamp(2rem, calc(2rem + 1.2vw), 3rem);
Pages were tested before launch with the axe DevTools plugin, which surfaced a handful of fixes. This wasn't a deep accessibility dive — and not a full rewrite, so little change in that department is expected overall — but problems found are of particular interest for fixing.
Some bugs are certain to remain. Reports belong at [[email protected]] rather than in a comment thread.



