Getting started
What Mapled is, how a site reads it, and the fastest way to connect yours.
Mapled is a hosted headless CMS for sites built with AI. The site's owner edits texts, images and lists in Mapled; the site reads the published content through a small SDK; an AI agent connects the two from a single prompt.
How it works
- Model the content. A project holds collections — lists of alike records, such as posts, team members or products — and singles, the one-off parts of a site, such as the homepage or the footer. Each has its fields.
- Edit and publish. Editors change drafts at app.mapled.io and press Publish. A publish makes a release, a snapshot of the published content. No edit reaches the live site before that — only Live data, the records a site's backend writes itself (orders, bookings), skips Publish.
- The site reads the release. It asks Mapled's delivery API with the project's delivery key — through
@mapled/next,@mapled/react,@mapled/vanilla, another SDK or plain HTTP. A webhook tells a site with a server when to refresh.
Two ways to connect a site
- Connect with AI — recommended. Paste one prompt into Claude Code, Codex or Cursor opened on the site's code. The agent finds the hardcoded content, proposes a content model, moves the content into Mapled and wires the site. You approve in the browser.
- Integrate by hand — the same integration step by step, with the CLI and the SDK for your stack, and no agent.
Next
- Create a project · Sign up, start a project from a template or from scratch, and choose how to connect your site.
- Key concepts · Collections, singles, records, releases, keys and roles — the words the rest of the docs use.