The About page works because an About page really is mostly one block of prose. A front page is not. It is a headline with a call to action, then a paragraph, then something else — assembled out of parts, in an order somebody decides and later changes.
Modelling that badly is one of the two or three ways a content model goes wrong permanently, so it is worth going slowly here.
The wrong answer first
The tempting move is to add fields to page for the things a front page has: hero-heading, hero-body, hero-cta-label, feature-one-heading… It works, briefly. Then a page needs two features instead of three, or the same blocks in a different order, or a section the page type was never given fields for — and every one of those is a Contract change, which means a schema change, which means it needs a developer.
You can see where it ends: a page Contract with forty fields, most of them empty on most pages, and a rule nobody wrote down about which combinations are legal.
Sections are a repeating field of Presentations
The answer is a single field. page gains sections: enumerable, of type Presentation.
A Presentation value is the same pairing the node payload used in part one — a Template, plus the content to run through it. Making it a field means a page holds an ordered list of them, and an author adds, removes and reorders sections without anyone changing a Contract.
Northwind’s front page is authored entirely out of sections. So is almost every page from here on. The body field stays, for the pages that really are prose.
One Contract, two Templates
Here is the part that makes the earlier discipline pay.
Northwind needs a hero — big type, a call to action — and it needs plainer statements further down the page. Those look nothing like each other. They are the same content: a heading, some body copy, and zero or more calls to action.
So there is one Contract, statement, and two Templates over it: hero and prose. Both declare statement as a supported Contract, so either can bind to the exact same Component.
Moving a section from prose to hero changes no content whatsoever. There is no migration, nothing is copied, and the words are still one thing in one place. Now try to imagine doing that if the Contract had been called hero and had a field named hero-heading.
Name a Contract for what it holds, never for where you first happened to show it.
That rule is the whole reason statement is called statement. Naming it hero is how you end up with hero-2 next year, when the second design arrives and the good name is already spent.
A curated palette, not a free-for-all
A Presentation field with no constraints lets an author put any Template anywhere, including ones that make no sense on a page. So sections carries allowedTemplateIds: the Templates that belong in a page’s section list, and no others.
The picker then shows an author a short list of real choices rather than every Template in the system. Constraints like this are worth adding as you go — they are the difference between a model somebody can use confidently and one they have to be trained on.
There is a small ordering wrinkle worth knowing about, because you will hit it: the Templates name the Contracts they render, and the Contract’s sections field names the Templates it allows. They point at each other. Whatever you use to build the model — the UI, or a script — has to create one side, then the other, then come back and fill in the first. Nothing is wrong when that happens; it is just what a cycle looks like.
Links that cannot go stale
The hero has a call to action, and that call to action points at another page on this site. There are two ways to store that, and only one of them is right.
Storing /coffees as a URL means storing a guess about where that page will always live. Rename the slug and the link is silently broken, with nothing anywhere to detect it.
So an internal link stores the target node’s identity, and the Delivery API resolves the current path for it on every request. Move the page and every link to it follows. Unpublish the page and the link honestly reports that it resolves to nothing, rather than pointing at a 404.
The API will refuse /about typed into an external-URL field, which is exactly the right refusal even if it is briefly annoying. An internal link written as a URL is a stale link waiting to happen.
The header stays hard-coded, on purpose
The site now needs a header and a footer, and this is where we do something that will look wrong: the navigation is a plain array in a React component.
const NAV = [
{ label: "Coffees", href: "/coffees" },
{ label: "Guides", href: "/guides" },
]
Every argument this series has made so far says that is content. It is. Adding a nav item means an edit, a commit and a deploy, for a change with nothing to do with code.
It stays that way for now for one reason: much later there is a step that moves it into the CMS, and that step is the single most useful one here for anyone with an existing site — because almost nobody starts greenfield, and "we already have a header" is where every real migration begins. A clean after needs a clean before.
If it helps, think of it as the one piece of technical debt in this project that has a scheduled repayment date.
The first checkpoint
This is a checkpoint step, which means there is a bundle. Import it and your organization holds everything the model has so far — the Contracts, the Templates, the Components, the pages — without your typing any of it.
Two things to know about importing. Choose fresh identity when the import screen offers it: that rewrites every id and every reference between them, so the content is genuinely yours rather than a copy carrying another organization’s identifiers. And an import writes drafts — nothing is delivered until you publish it, which is the same rule as part one, arriving in bulk.
Where this leaves us
Two pages, a small palette of section Templates, and a header we have promised to fix.
What Northwind still does not have is anything a coffee roaster would recognise as its actual business. Next: modelling a product — images, repeating fields, and the first Contract that is about the thing being sold rather than about a page.
