Northwind sells coffee to people who will go home and make it badly. So: three brew guides — pour-over, cafetière, AeroPress — each a sequence of steps with a photograph of the right vessel part-way through.
Two ideas in this part have not appeared yet, and the first is the mirror image of part 5.
Structure without independence
A guide is a list of steps. Each step has a heading, a body, sometimes a time and a picture. That is clearly structured content, not a wall of prose — so it is a Contract, guide-step.
And a guide-step has no life of its own whatsoever. It is never referenced by anything, never published separately, never shared between guides, and it does not appear in the Component library at all. Each guide holds its steps inline.
Run part 5’s three questions over it and every answer is no, which is the same result the coffee photograph got and the exact opposite of the origin. That is the point of putting them side by side:
Being a Contract is about having a shape. Being a Component is about having an independent life. They are different questions, and inline content answers yes to the first and no to the second.
A lot of content modelling goes wrong by assuming that anything worth a Contract is worth a Component. Most structured content is furniture inside something else.
A figure inside the prose
The second idea: a picture that belongs in a paragraph’s flow, not beside it.
A step’s body is rich text, and the markdown contains a token:
Rinse the filter, then discard the water.
{{embed:vessel}}
Add the grounds and level them.
The document’s own embeds map says what vessel is — here, a Presentation: a Template plus the content to run through it. The SDK splits the text around the token and dispatches that embed to src/presentations/figure.tsx, exactly as it dispatches a page section.
That is the part worth noticing. There is no special "inline image" path anywhere in this app. An embedded figure and a page section are the same mechanism arriving in a different place, so anything you can put in a section you can put in a sentence, and a new one costs a renderer rather than a feature.
An embed binds the same two ways a Presentation field does: a Component by reference, or content written inline. The three figures here are references to real image Components in the library — and that is a decision rather than a default, made by running this part’s own three questions over a diagram of a V60 and getting the opposite answer to the one a product photograph gets. A brew vessel is shared, separately publishable and worth finding. A photograph of one bag of coffee is none of those.
A query, or a list somebody wrote
/coffees is a stream. /guides is not — it is a list, authored by hand, in an order a person chose.
That looks inconsistent and is the whole decision:
A catalogue should be complete and maintain itself. Publish a coffee and it belongs in the catalogue; forgetting to add it would be a bug. Nobody curates it, so a query is exactly right.
A set of guides is editorial. Somebody decided a beginner should read pour-over first and that three is the right number. That decision is content — it is a judgement, it will change, and it belongs to whoever owns the guides rather than being inferred from a publish date.
The test is whether being missing from the list would be a mistake or a choice. If a mistake, query it. If a choice, let somebody make it.
The second checkpoint
This step has a bundle: 17 Contracts, 9 Templates, 23 Components, 21 nodes, one stream and 16 blobs. Same rules as part 7 — fresh identity, and everything arrives as drafts.
Where this leaves us
The site has products, a catalogue and editorial content. What it does not have is any of the small pages every real site turns out to need.
Next: two of them at once, including the first time this series leaves Content entirely.
