Widget anatomy
A reference page bundle: the widgets/ folder laid out for both classes of widget — static and interactive — plus the _shared layer, to copy from.
New guides and big updates only. No spam, one-click unsubscribe.
Every guide carries one or two curated tags: a narrow topic like #widgets or #palettes that cuts across rubrics and series. Click a tag — I'll gather every guide on the topic into one feed.
click a tag — the picks show up here · full feed is on the home page
A reference page bundle: the widgets/ folder laid out for both classes of widget — static and interactive — plus the _shared layer, to copy from.
Reference for reader controls: search and panel keys, focus mode, the View popover, and what's remembered locally.
Customization without a fork: a palette in one toml file, custom.css, hook partials, a section of your own and a second language.
A guide scaffold in one command, the front matter canon, shortcodes, captions for code and a live widget in two touches.
What the theme does, three ways to install it, the minimal config and the content layout — from an empty folder to a built site.
A regression testbed: every shortcode, callout, code block, diagram and widget on one page.
What the theme does at build time: OG covers from a style folder, Pagefind full-text search and the version chip.
Palettes as data: a toml file in data/themes/, out of which the build makes CSS blocks and the picker's swatches.
How series work: a series is a folder in its rubric — and the “part N of M” kicker, the panel and the bridge count themselves at build time.
The theme's content model: an article is a leaf bundle, where its widgets, styles and cover sit next to the text.