Northwind has four shops and a wholesale enquiry. Neither is interesting enough for a part of its own, and together they cover two things worth having seen.
Shops: nothing new, and that is the point
A store Contract — name, address, opening hours, a map link — and a store-list page holding them inline, in an order somebody chose.
That is guide-step from part 9, again, for the same reasons: nothing points at a store, no store has a page of its own, and nobody is going to look one up in the library. Run the three questions and get three noes.
It is worth noticing when a decision stops needing to be made. The first time inline-versus-reference came up it took a whole part. By the third time it is a ten-second question with an obvious answer, and that is what having a rule is for.
The first link that leaves the site
Every link so far has been an experience link — storing the target node’s identity, so the CMS resolves the current path on every request and moving a page never breaks anything pointing at it.
A shop’s map link is not that. It genuinely points at somewhere we do not control, and no amount of resolution will help, so it is the external arm: a URL, stored as a URL.
The field says so, rather than leaving it to whoever authors the fifth store:
allowedKinds: ['external']
Both arms exist on the same field type for a reason — a "link" is one idea with two implementations, and which one is legal here is a modelling decision rather than something to work out per value. Constrain it and the picker offers one kind of thing; leave it open and eventually somebody types /coffees into an external URL field.
The third time we have edited an array to publish a page
Adding /stores means adding it to the navigation, which means editing a hard-coded array in Header.tsx and another in Footer.tsx, then committing and deploying.
That is the third time in this series. Part 3 promised it gets fixed, and part 11 is next. Keeping count is deliberate: it is easy to stop noticing a small friction that recurs, and the whole argument of the next part is the diff between doing this and not.
Contact: leaving Content
The second page is a wholesale enquiry, and it needs a form. Northwind does not build one.
This is the first time the series leaves Content: the page embeds an ebitex Form, which is a different product in the same suite, integrated over its own public surface exactly as any customer would integrate it.
The Contract has one field
form-embed holds one mandatory field: which form. That is all.
Everything else about an embed — the organization slug, where Forms is served from — is configuration, and lives in the app’s .env rather than in content. That is a decision worth being explicit about, because a per-page slug field looks more flexible:
This site embeds its own forms. A field that lets an author name a different organization buys nothing anybody wants and makes it possible to embed somebody else’s form by accident.
Flexibility that nobody needs is surface area, and surface area on a public page is a liability. The rule generalises: if a value is the same for every instance and always will be, it is configuration.
The embed is the real embed
The renderer produces an iframe and Forms’ own embed.js. It does not re-render the form from its definition, and that restraint is the interesting part.
Re-rendering would look better — a form styled entirely by this site, no iframe, full control. It would also mean that every change to the form needs a matching change in this repository: add a field in Forms and the site does not show it until somebody ships. The embed keeps the form’s behaviour where the form is.
So the CMS decides which form and where on the page, and has no opinion at all about how it gets there. That division is the same one part 2 drew between a Contract and a Template, arriving at a product boundary instead of a field.
When it is not configured
Without the environment variable the renderer shows a sentence explaining what is missing, rather than an empty iframe. A sample cannot assume the reader has created a form yet, and "nothing appeared" is the least useful thing a page can say.
That is worth stealing generally. A renderer that depends on configuration should say which configuration, in the place the content was going to be.
Where this leaves us
A site with shops and a contact page, and a navigation that still lives in a code file.
Next: the part most readers will actually need, because almost nobody starts greenfield.
