About
Our story
Why nertia exists, and what a recipe is.
A site on nertia is a recipe with three parts.
- The content is your text, media and links. It comes from the editor, from a file, or from a spreadsheet.
- The style is the look. It is a set of design tokens on a shared base, so any style works with any structure. Swapping the style changes the fonts and colours without touching the structure.
- The structure is how things are arranged. The same idea repeats at every size. A section arranges its parts, a page arranges sections, and a site arranges pages.
The code and the developer docs call the structure a pattern and the style a skin.
Content plus style plus structure is the recipe. It is the complete site in one portable file. The editor reads and writes it, and the renderer turns it into pages. A section is one block of that site: a hero, a pricing table, a contact form.
Why it matters
Most builders are designed to keep you. The structure of your site lives inside their editor. Export is an afterthought. Once the product matures, the price starts to climb.
nertia turns that around. The recipe is the site. Downloading it is a button, not a support ticket. The builder stays free.
AI is the frosting, not the cake
The recipe carries the site. AI carries the polish. Shared standards, shared compositions and your own content are the cake. AI helps you refine them. It does not rebuild the stack every time you type a prompt.
Keep reading
- About nertia: the problem, what we hold to, and the stack
- Belief system: the worldview behind the product
- Architecture: how the builder, the CLI and MCP share one engine
- Using nertia: the how-to guides