Components

A deterministic style system for brochure-quality local-business sites — built to feed Slipstream. Reverse-engineer real sites into Style-Guide presets, evaluate frameworks, and assemble field-bound sections.

New here? Start here
How to use this tool

Start here — the logical flow

What Components is, the three words you'll see everywhere, and the step-by-step path from a real website to a part Slipstream can assemble: capture → inspect → pick a look → compose → verify → ship.

Read how to use it →
Work together
Shared worklist · Isaac × Claude

Component worklist

Every component with a status and a notes field you fill in; Claude reads it and replies per-component, so we share the same context. The queue for working through manual component changes together.

Open the worklist →
Review the looks — presets × libraries
Whole page · 5 presets × 4 libraries

Page compare

One full page (Celebrate With Helena) rendered under every Preset (skin) and every Library (framework: Shoelace · Open Props · daisyUI · Pico), switchable independently. The fastest way to see all the looks at once.

Compare presets × libraries →
Style × Sample × Library + the dials

Style inspector

Render any sample under any Preset and any Library, with the live dial/provenance panel beside it — captured vs derived vs platform-default, and the leak check.

Open the inspector →
Every section

Sections gallery

The component-composed sections, each rendered across the four libraries side by side.

Browse the sections →
Every component · light × dark

Component gallery

Every component stacked as a standalone dummy, filterable, on a light and a dark surface side by side — reskinned live by any teardown × framework. Also reachable via the showcase's All-components toggle.

Open the component gallery →
Sections & manifest — the current focus
The page, assembled

Layout preview — johncooksey

The north-star page rendered end-to-end: all 10 sections in order, one business's data through their bindings, under any captured Style Guide. Layout × Sections × Data × Style Guide → a real page you can look at.

View the assembled page →
Process, don't generate

Section Processor

Reads any slipstream-sections package and computes the visual guide: data-slot ↔ field bindings (✓/✗), every style value classed (token / section-fixed / ⚠ ungoverned), and a spec sheet of business-types, pages & budget.

Open the processor →
Describe → compose → bind → emit

Section authoring panel

The input end of the pipeline: describe a new section, compose it from catalogue components, bind each slot to a real data field (new fields flagged as requests), and emit the section spec the emitter turns into a package.

Author a section →
Background slots

Section surfaces

A section in four states — page / alt / emphasis / inverse — all derived from the brand, aligned to slipstream-prod's Style-Guide v2. Click a chip to cycle a section's surface.

See section surfaces →
Library × Preset × Niche

Section Workbench

The 3-axis composer: render a Section Spec by binding niche fixtures, swap library anatomy and Style-Guide preset.

Open the workbench →
Teardown × framework

Teardown showcase

Any captured teardown's real style rendered through the 4 framework components (Shoelace · Open Props · daisyUI · Pico) with a selector — distinct component construction, not the old generic shim.

Open the showcase →
Framework evaluation — the experiment
3 changes on a beautiful framework

Framework presets

The deterministic recipe: a base framework + a captured Style Guide + a short, ordered list of deliberate deltas — each with its rationale. Toggle the changes live; copy the portable recipe to seed a Slipstream Style Preset.

Open the preset builder →
Verified + shortlist

Frameworks & real-world examples

All 20 frameworks with links to sites that actually use each (new tab) + honest adoption tags. Includes the shortlist workshops: Web Awesome, daisyUI, Pico, Open Props.

Open examples & workshops →
Same components, real CSS

Framework comparison

The first ten frameworks side by side with a live Style-Guide dovetail switcher. Links through to page 2 (ten more considered systems).

Compare frameworks →
More considered systems

Comparison · page 2

Ten frameworks whose defaults carry real design opinion — shadcn-without-React, Vanilla, Primer, USWDS, Tabler and more.

See page 2 →
Deterministic check

Adoption test

Applies a sentinel Style Guide through the real theming code and asserts colour/radius/font/weight actually land — per framework, ✓/✗.

Run the test →
Teardowns, QA & reference
The rigour gate

QA — results, rules & conventions

One deterministic gate over every library and teardown: pass/cross per item, the rules in plain English, and the global conventions.

Open QA →
Reverse-engineer

Style teardown tool

Paste a URL; it mines the real CSS into a captured Style-Guide preset + character report. Each opens three sides: A (captured), B (proposed), C (derived).

Open the teardown tool →
Distinctness map

Style scores

Where each teardown sits on the character vector — how distinct they are from each other and from Bootstrap.

See the map →
Catalogue × Library

Component library

Every component in the base library, with gaps shown, cross-checked against Bootstrap & Bulma. Plus the captured presets grid.

Open the library →
What we capture

Capture coverage & roadmap

Values captured today vs the backlog of stylistic things worth adding to future captures.

See coverage →
Scope check

Bootstrap spec ↔ our tokens

Every variable Bootstrap enumerates, beside our equivalent token — a check that ours is a finite, determined spec.

See the scope →
Shared language

Glossary

Catalogue · Library · Teardown, skin vs library-character, captured-facts-only, and the rest.

Read the glossary →

Live at components.makelabs.com.au · feeds Slipstream (slipstream-prod / slipstream-sections).
Teardowns show captured facts only; proposals live on the B-side. Frameworks are a headstart on beauty, not a commitment.