Your choices about data
We use cookies that are required for this site to work. Anything beyond that — measuring how the site is used, or personalising what you see — happens only if you say yes.
Pages are data, not markup.
Including this one — it is a JSON stream
See pricing
This page is the argument for the feature.
Every marketing surface here is a stream of typed blocks rather than hand-written JSX, which is why a Spanish version is a sibling file instead of a project, and why a parity test can fail the build when one language drifts from the other. The cost is that a malformed block invalidates the page rather than degrading it — a trade worth making, because a page that half-renders is harder to notice than one that does not.
What it buys you
Three consequences that only show up later.
Two languages
Spanish as an equal
One file per language, guarded by a test that fails when the structures diverge or when the Spanish is a copy of the English.
Pictures
Diagrams from the source
Visualizations generated from the same data the docs describe, so a diagram cannot quietly go out of date.
Who can change it
Editable without a deploy
Content lives beside the code but is not the code, so changing a sentence does not require someone who can read TypeScript.