A page is a one-of-a-kind part of the site with a fixed address: the home, About, Contact, Pricing. Each page has its own fields, so the panel shows exactly what that page needs — a headline and a list of services on the home, an address and opening hours on Contact. Pages are declared in site.json, the file that describes the site's structure, and the admin panel is generated from it.
Page or content type?
Decide first what each part of the site is. One question settles it: will the client want to create another one of these alone?
- No — there is one About, one Contact: it's a page.
- Yes, and they all share the same fields — posts, cases, services: it's a content type (see Content types).
- Yes, but each one has its own purpose — a campaign, an event: it's a page the client creates from a page template, below.
Getting this wrong is the costliest structure mistake to fix once there is content.
Ask the AI
Create the pages for Clínica Movimento, a physiotherapy clinic in Curitiba. For now only Home, About and Contact. Home: a short line above the title, the main title, an intro paragraph, the button text and a list of treatments, each with a name and a one-line summary. About: title, intro and a formatted text. Contact: address, phone, WhatsApp number and opening hours. No blog and no forms yet. Validate site.json at the end.
Each item on the list becomes a field the client edits: describing the information is designing the panel. Saying what's out keeps the AI from inventing a blog you would have to remove.
What the AI does
It adds each page to site.json with its fields and its template (the PHP file in theme/templates/ that turns those fields into HTML), writes the templates, validates the file and creates the page records in the database. The pages then appear in the panel, ready to fill in.
A page points to its template by file name, never by its address. That's why renaming an address never breaks the layout.
schema:validate also warns when a page's template file is missing from the theme and there's nothing to fall back on: that address would answer with a 404.In the panel
Pages, in the side menu, lists every page with its address and a View link. Each page opens with its fields and, at the end, the built-in SEO & sharing section with meta title, description and share image, so never ask for SEO fields.
On a page declared in site.json, the client edits the content; its name and address come from the file, so changing them is a request to the AI. These pages can't be deleted in the panel.
Subpages
A page can sit under another: Treatments at /treatments, Pilates at /treatments/pilates. Ask in words — “put Pilates and Hydrotherapy under Treatments” — and the AI sets the parent page in site.json. An address only has to be unique among pages with the same parent. Since v3.9.0, the panel's View link shows a subpage's full address.
Pages the client creates
Some sites need new pages over time: one per campaign, per event, per partner. For that, the AI registers page templates (page_templates): models of pages the client creates without you, each with its own fields and look. Once one exists, the Pages screen shows a + Create page button.
Ask the AI
Add a page template called Workshop for Trigo Bakery, which runs baking classes, so the team can create one page per workshop on their own. Fields: date, duration, price, a short description, a photo and the sign-up button (text and link). The team will create these pages under the Courses page.
From then on, a new workshop is a page the team creates in the panel. Nobody touches the theme for it.
How the client creates a page
-
Start
In Pages, click + Create page and type the title and the address: lowercase letters, numbers and hyphens, like
black-friday-2026. -
Choose the template
Pick the page template and, if the page goes under another one, the parent page. The panel refuses an address already used by another page, a content type or a taxonomy (a set of categories or tags).
-
Fill in
Click Create page: the fields of that template appear. Fill them in and save.
-
Manage
Pages created this way carry a panel badge; the client can rename them, move them, switch their template or delete them.
The home and the 404 page
The home is the page at /, usually the one with the key home. A custom 404 page — what visitors see at an address that doesn't exist — is a page like any other, with its own fields and template; the AI points not_found_page to it. It has no address of its own, stays out of the sitemap (the list of addresses offered to search engines) and answers with a 404 status. Since v3.9.0, an address whose template file is missing also shows it, instead of an error page.
Ask the AI
Create a custom 404 page: a short message, a button back to the home and links to the three main treatments. The client should be able to change the message in the panel.
It shows up under Pages like the others, with its own fields. Without one, Velk shows a generic 404.