roadmap
What is coming, and what never will.
A roadmap is only useful if it includes the second half. The bottom section is the one worth reading — those items are not delayed, they are decided against, and no amount of waiting will produce them.
next
Being worked on
No dates. A date on a €69 product is a promise that gets broken at the worst possible moment, and you would remember the broken promise rather than the working software.
001A cookbook
Four worked examples — add a block, an object, a document type, a field — each showing the prompt given and the diff that came back.
002Dataset export
The counterpart to seed:import, so you can turn your own content back into a seed file.
003Security headers
CSP, HSTS and the rest, as a documented default you can loosen rather than a blank you have to fill.
004More blocks
The fourteen here exist because this page needed them. Others will arrive the same way — because something real needed one.
not coming
Decided against, not delayed
Each of these would change what the product is. If one of them is what you need, the comparison table on the homepage points at where to find it.
001TypeScript
Migrating would mean rewriting every convention the toolkit teaches. That is a different product at a different price, not a version bump.
002Sanity typegen
It depends on TypeScript. Same answer, for the same reason.
003Multi-language
Genuinely large, and half of it is worse than none of it. Single-locale is a stated design decision, not an omission.
004A component library
No UI kit to theme. Fourteen blocks that demonstrate the conventions, then it is your code and your design.
changelog
What has actually changed
The full history ships in the repository as CHANGELOG.md, so you can read it before buying and diff it after an update.
## Unreleased ### Fixed- An empty dataset no longer 500s every route. A missing metadata singleton threw in the root layout.- In-page navigation actually navigates — the header linked to fragments that matched no element on the page.- Colour utilities follow an inverted section. They compiled to hex, so only inherited colour ever inverted. ### Added- Five blocks: Marquee, FeatureCards, TerminalBlock, ComparisonTable, MediaGrid.- Light and dark sections, via a theme field on any block.- check:blocks — every block schema has a component, a group and a registry entry, and no component lacks a schema.