Skip to main content
Placeholder standing in for a wide masthead photograph.

Linney

A base theme that starts finished

The component library, the theming contract and the motion are already built and already audited. What is left for a project is the brand and the content.

A fork changes values, not files

Everything a project retunes lives in one stylesheet: the palette, the typefaces, the type scale, the spacing, the radii and the motion timings. The semantic layer above it is an audited set of relationships rather than a set of values, so changing a brand cannot quietly break the contrast it was checked against.

Typeface, weight and button radius are runtime options rather than compiled constants, which means a rebrand that touches only those needs no build at all.

Placeholder standing in for a three-by-two photograph.

Composed by an editor, not a developer

Every block is a row an editor adds, orders and reorders, with its own Content and Options tabs. None of them assumes what sits above or below it, which is the only way a page built by somebody who has never seen the design still holds together.

A control that can produce an illegible or empty result is treated as a bug in the control rather than as a mistake by the person using it.

Judge a change by what it costs a developer forking the theme, not by what it adds to any one site.

The first product principle PRODUCT.md

Placeholder marks, like everything else here

Reference

The rest of this site is the library

One page per block, each holding that block and every variation of it. Both this page and those are written by scripts/seedDemoContent.php, which can be run again to put the demo back the way it started.