惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - 三生石上(FineUI控件)
博客园 - 叶小钗
博客园 - 聂微东
博客园 - 司徒正美
Hugging Face - Blog
Hugging Face - Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Google DeepMind News
Google DeepMind News
Recent Announcements
Recent Announcements
IT之家
IT之家
J
Java Code Geeks
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
I
InfoQ
爱范儿
爱范儿
Vercel News
Vercel News
Apple Machine Learning Research
Apple Machine Learning Research
阮一峰的网络日志
阮一峰的网络日志
博客园 - Franky
U
Unit 42
酷 壳 – CoolShell
酷 壳 – CoolShell
腾讯CDC
F
Fortinet All Blogs
V
Visual Studio Blog
人人都是产品经理
人人都是产品经理

That HTML Blog

Liquid Glass 2.0 in CSS (Aqua’s Revenge) Cross-Document State Management (An In-Depth Tutorial) Designing an Autogenerated Live Color Scale in CSS The Best Introduction Guide to SVG You Will Read Masonry Layout Solved! Hello CSS Grid Lanes Two Paradigms for Enhancing HTML Tags The Web Platform is a Triumph of Object-Oriented Programming The Nuances of JavaScript Typing using JSDoc Write Custom Extensions for htmx to Make it Your Own Personal Toolkit Add Terrific DX to Your UI Web Components with nimble-html Give “fetch” a Bit More Oomph with “ffetch”
So Many Ways to Design Systematize a Component
Jared White · 2026-08-17 · via That HTML Blog

  Permalink

Screenshot of card component variants overlaid on colorful opal gems.

This post is part of Intuitive+Learn, an exclusive series on That HTML Blog available with your Intuitive+ membership. Sign up here, or sign in to obtain your unlock key.

Design systematize: is that a phrase I made up? Perhaps so!

My thesis is a lot of folks these days “get” thinking in terms of design system components—at the “design system” level of course. You’ve got your buttons, your dialogs, your form inputs, and—of course—the humble card. All good stuff.

But what happens when you’re not working in your design system itself, but out in the “real world” where the shit hits the fan and you’re suddenly having to deal with all of the problems you didn’t think you’d have when you were working in the pure landscape of the system?

CSS has always acted as a blunt instrument where, sure, you can override a bunch of crap and brute force your way to an updated design solution quickly. But as we regularly end up learning the hard way, that quickly devolves into an unmaintainable spaghetti mess.

Modern CSS provides the ability to work with much more nuance, to think in a more modular and—dare I say—object-oriented fashion. You now have the ability to create component APIs which are blessed paths for downstream users of components to customize their appearance at the template or feature level.

In a past course for The Spicy Web, CSS Nouveau, I unpacked many of these concepts in an introductory fashion. In this tutorial, I now would like to zero in on a particular component tree, and consider a number of ways we might want to change the styles of these components without needing to brute force much at all (or mess around with the internals of the components).

Let’s get started!

Included in this tutorial when unlocked:

  • A detailed explanation of several plausible “bespoke” styling contexts.
  • Demos of standard card component and array of template-related variations.
  • Working through the scenarios in a methodical manner and explaning the process along the way.
  • Helpful guidance on appearing like a genius as new design requirements arise.
  • You’re encouraged to ask follow-up questions in the Human Web Collective Discord.

🙏 I’m excited to offer this new series in conjunction with Intuitive+, and I hope you enjoy it!