Lineage
The ideas Calaca UI stands on and the people who published them. A page of thanks to mentors who never knew they were.
Standing on shoulders
Calaca UI invents little. It combines ideas that others researched, named and gave away over the last fifteen years, then makes them hold under real teams by enforcing them with tests where the originals relied on discipline.
These are the people whose writing shaped this system. None of them know it. That is what makes them mentors in the honest sense: their published thinking was the teaching.
Nicole Sullivan: structure and skin
OOCSS (2009) separated an object’s structure from its skin and a container from its content. Calaca’s core and skins are that idea made mechanical: the split test proves the two layers can never set the same property.
Jonathan Snook: a place for every rule
SMACSS (2011) taught the web to sort CSS into base,
layout, module, state and theme. Calaca keeps the sorting instinct and swaps
is-* state classes for data-* attributes that say what an element is.
BEM: naming as a contract
Yandex’s block__element--modifier grammar survives in every ca-* name:
not for its looks, but because a regular grammar is one a machine can check.
The naming test is BEM’s real legacy.
Harry Roberts: specificity as architecture
ITCSS ordered a stylesheet from the generic to the specific, an inverted triangle of increasing reach. Calaca’s five layers are that triangle; tests took over the source-order discipline it depended on.
Miriam Suzanne: the cascade, on purpose
Author of the @layer specification and longtime Sass toolmaker. Her
writing and tools teach the cascade as a feature to
design with, not a bug to survive: the deeper reason Calaca assigns each
layer its own properties instead of escalating specificity.
Andy Bell and Heydon Pickering: composition over components
CUBE CSS and Every Layout
gave us the composition layer. ca-stack, ca-cluster and ca-grid descend
directly from their primitives, and a block layout that only sets variables
is CUBE’s “blocks set custom properties, exceptions live on attributes”
wearing a different prefix.
Rachel Andrew: layout as a system
Her books, talks and grid advocacy taught the
industry that layout is a system of relationships between tracks and items,
not a list of breakpoints. ca-grid and ca-cluster inherit that mindset.
Zell Liew: type that scales
Years of his articles, books and courses made responsive
typography a craft instead of a guess: modular scales, rem-based sizing,
type that answers to its context rather than to a table of breakpoints.
Calaca’s type tokens (--ca-type-xs through --ca-type-9xl, with leading,
tracking and weight as named scales) are a modular scale turned into
contract.
Josh Comeau: explain the mechanism, not the recipe
His courses and articles showed that CSS makes sense once you teach the mechanism instead of the trick, and that motion is part of the design, not decoration. Calaca’s named ease and duration tokens, and the way these guides explain why before how, carry that forward.
Brad Frost: a shared vocabulary
Atomic Design gave the field its taxonomy of small parts composing into bigger wholes. Calaca’s elements, components and blocks follow it.
Adam Wathan: the utility floor
Tailwind CSS is the ground every skin compiles to. Instance utilities outranking component classes is its most useful inheritance.
The WAI-ARIA Authoring Practices Guide
The APG patterns define what a dialog, tab list, listbox or tooltip owes its users. The core encodes them once, so no product has to rediscover them.
Chris Coyier: the field’s shared notebook
For fifteen years CSS-Tricks was where the industry kept its notes: show the technique, name the edge cases, credit where it came from. Calaca’s component pages (every class listed, every behavior named, every gap admitted) are written to that standard.
Tania Rascia: learning in public
Her tutorials and notes prove that a personal site can be a serious place to teach: fundamentals explained plainly, no pretense. This site, and this page, exist in that spirit.
Tobias van Schneider: a site of your own
His essays on design, taste and the craft argue that a personal site is where a designer’s voice actually lives: not on a platform, not in a portfolio template. Building your own system, then writing about why it works the way it does, is that idea taken literally.
Why this page exists
A system is easier to trust when its debts are on the table. If you build on Calaca UI, you are building on all of them too.