The technology behind everything on your site that responds to a click. Instead of reloading the whole page, only the part that should change does.
Every click reloads the page, starting over each time.
The next step is simply there — it feels like an app.
- Everything is a part
Header, card, button — each piece exists exactly once and is used wherever it's needed.
- Changes happen in one place
If the card should get a border, it gets one on every page at the same time. Nothing to chase, nothing forgotten.
- State drives what you see
Whether a menu is open is held as state — the display follows from it, not the other way round.
- Only what changed is redrawn
When a value changes, the affected piece is rebuilt, not the whole page.
- Page
- Header
- Content
- Footer
- Card
A page is a tree of parts. The card exists once — it appears on forty pages and is changed in one place.
A library for interfaces. The page is split into building blocks, each with its own state. When something changes, only the affected part is swapped instead of rebuilding the whole page.
- Version
- 19
- Principle
- building blocks
- Update
- only the changed part
- Reach
- largest ecosystem on the web
Enquiry flows that move forward step by step
Dropdowns and galleries that react immediately
Forms that flag mistakes as you type, not at the end
Every block has to run in the visitor's browser. On pages without interaction that's dead weight — there I deliberately build without it.
The enquiry configurator runs through four steps without a single reload.