Pages and languages
A page exists because a thing on your site — a service, a person, an article — claims an address. Give it an address and it has a page.
A thing with an address is a page
Everything on the site is a structured entity: an Article, a Person, an Event. An entity with an address — /about, /team/joey — is a page at that address. The site renders it by what kind of thing it is, falling back to a plain page layout; your designer can refine the template per kind, you never choose one (How a page finds its shell).
Two things claiming the same address are flagged before publishing. So is an address in the default language that starts with one of the site’s other language codes (/nl/… on a site that carries Dutch): the site reads that as the language, not the page. The home page is the entity designated as home.
An overview — the blog index, a list of services — is a page like any other, whose template asks the site for the rows of a type (newest first) or of a curated list, and shapes them; nothing is copied, the rows point at the entities. In a draft preview a staged post already sits on top of its overview.
Things without an address — an opening-hours table, a testimonial, an image — appear inside the pages that use them. They are not private for it: every live entity, page or not, is listed in the site’s index and readable at its own file address under /data. And no page can claim /data itself, or anything under it — that prefix belongs to the files.
Languages
A site has one default language and can have more. Each entity carries its address per language: /diensten in Dutch, /services in English. The alternate-language links search engines read, the per-language sitemap and the language switch all derive from that map; none is maintained by hand.
A translation is not required: an entity without an address in a language does not exist there — no page, no menu entry, no sitemap line, no line in that language’s index. The entity’s file is one and carries every language; only its readings — the index and the .md form — are per language. A link to something that only exists in another language points at the real page there. A visitor sees either a translation or honestly the default, so you see at a glance what you forgot.
Moving a page
Change an entity’s address and the page moves: sitemap entry, language links and identity follow. Bookmarks, search results and links on other sites do not, so a redirect from the old address is added; the site’s check reminds you of internal links that still take the detour.
What to ask your agent
| You say | The agent does |
|---|---|
| “Make a page about our new workshop” | Creates an Event entity with an address and stages it |
| “Add an English version of the about page” | Adds the English address and translated content to the same entity |
| “Take the old vacancies page offline” | Takes it back to draft — refused while a template or another page’s text still links to it; fix those first |