Recipes
Complete, checked examples of the tasks an agent meets most when building a Meridian site, from adding a content type to a DMO directory, a partner portal and an extension, each with the commands, the files and how to verify them.
Each recipe is a complete change: the commands to run, every file to write, and how to prove it works. Every configuration and template snippet on these pages has passed engine-dmo check in a scratch project, and those that render without a running server were rendered with engine-dmo render.
The core recipes continue one example, a walking site started with engine-dmo init: a walk type with a distance, a difficulty, a photo and a route description, routed at /walks/{slug} with an index at /walks. The DMO recipes start from a project with the core listing and area types. Replace the names with your own.
| Recipe | Use it to |
|---|---|
| Add a content type | Create a custom type with its fields |
| Add a field | Add, change, rename or remove a field, including selects and relations |
| Add a route and its template | Give a type addresses and pages |
| Listing page with filters and pagination | An index page with facets, a count, cards and a pager |
| Navigation menu | Header and footer menus editors can change |
| Responsive images | Image transforms, img(), figure(), credits and seeded photographs |
| Enquiry form | A contact form that stores and mails submissions |
| Multilingual site | A second locale with its own paths, strings and translations |
| Search page | A search route and its template |
| DMO directory | Listings with areas, categories, place facets and a map |
| Partner portal | Tiers, member editing rules, a portal screen and an invitation |
| Landing pages | Place and category pages at clean addresses |
| Claims | A “this is my business” link on a listing, and seeding what it needs |
| Extension | A template filter written in Go, when templates cannot do it |
Before each recipe, run engine-dmo guide to see the project as it is, and after it, follow the loop: engine-dmo check, engine-dmo schema plan, engine-dmo schema apply, engine-dmo render <path> --json.
Commands for agents
The engine commands a coding agent uses to read, change and verify a Meridian project (describe, guide, docs, help --json, the dev verbs, check, schema plan and apply, render --json, a11y audit, content, seed and mcp), what each returns, what it needs and when to use it.
Add a content type
How an agent adds a custom content type to a Meridian project with dev type add and dev field add, what the generated schema file holds, and how to verify the type is applied and has an id for every field.