Key concepts

Content

• Collection — a list of alike records: posts, team members, products. A collection whose records have pages of their own has a Slug field, so the site can find a record by its address.
• Single — a one-off part of the site with exactly one record: the homepage, the footer, the site settings.
• Field — one value of a record, with a key the code reads (title, cover) and a type: short and long text, rich text (Markdown), slug, image, file, number, boolean, date, date and time, choice, URL, email, color, location, JSON, a relation to records of another collection, a group of sub-fields, a list of components, or a computed value. Every field can carry a help text that editors see under it.
• Record — one item of a collection, or the content of a single.

A field's key can be renamed later, and the old key keeps working as an alias until someone removes it — but the site's code reads keys, so choose them with care.

Drafts and releases

Editors always work on drafts. A record is Draft until its first publish, Published when the live site shows exactly what the editor sees, and Edited when it changed since the last publish.

Review & publish shows what is changing; Publish now makes a release — a numbered snapshot of everything published. The site reads its content only from releases, so a half-finished edit never reaches it. Live data collections are the exception: their records are written and read by the site's backend at once, without Publish. A publish can also be scheduled, and an older release can be brought back.

Keys

• Delivery key (mk_live_…) — reads the published content of collections with access Public, and nothing else. It is the one key that is safe in a browser. Find it in the project's settings → Integrations → Your site.
• Webhook signing secret — signs the ping Mapled sends to a site's revalidation route on every publish. It lives in the site's server environment as MAPLED_WEBHOOK_SECRET, never in the browser.
• Server key — for Live data (Pro and Max): records the site's backend writes and reads at once, without Publish, such as orders or bookings. Server side only.

Fields marked Sensitive are left out of everything the delivery key reads, of Preview and of what AI agents see. Editors keep them in Mapled, and on Live data the site's backend can still read them with the server key — so keep the server key on the server.

People

• Owner and Editor edit content and publish; a Viewer only looks.
• Changing the structure — collections, fields, forms — takes an Owner or Editor who builds the project: the person whose plan holds the project's slot, or a member on Pro or Max.
• An AI agent works through a connection a person authorized. It changes drafts and structure, never publishes, and asks a person to confirm anything destructive. Connections are listed in Integrations and can be revoked there.

The integration

• Binding — where the site renders a field. The site's manifest of bindings lets Mapled warn editors before a change would break a page (Structure → Bindings).
• MAPLED.md — a guide Mapled writes for the site's repository: the content model, where each page reads what, the working rules and the commands that check the integration. The next agent or developer starts from it.