Integrate by hand
Connect a site to Mapled yourself, with the CLI and the SDK for your stack, and no AI agent.
Everything an AI agent does to connect a site can be done by a person. The integration has the same shape on every stack:
- Model the content in Mapled — collections, singles and their fields — and fill it in.
- Publish once. A site only ever reads published releases.
- Link the repository with the CLI and generate TypeScript types for the content.
- Replace the hardcoded content with reads, using the delivery key.
- Refresh on publish — a webhook for a site with a server; a site rendered in the browser reads the newest release on every load.
- Preview drafts from Mapled's Preview button.
- Record the integration — the manifest of where the code reads what, and
MAPLED.md. - Check everything with
npx @mapled/cli doctor.
Pick the package for your stack
| The site | Package | Guide |
|---|---|---|
| Next.js (App Router or Pages Router) | @mapled/next | Next.js, step by step |
| Astro | @mapled/astro | @mapled/astro README |
| Nuxt | @mapled/nuxt | @mapled/nuxt README |
| A React single-page app (Vite and the like) | @mapled/react | @mapled/react README |
| Plain HTML, no build step | @mapled/vanilla | @mapled/vanilla README |
| Anything else in JavaScript — Remix, SvelteKit, an Express server, a build script | @mapled/client | @mapled/client README |
| Any other language | — | The delivery HTTP API |
SDK packages compares them and shows the first read in each. The CLI reference covers every command the guides use.
- Next.js · The whole integration of a Next.js site by hand — model, read, refresh on publish, preview, forms — ending with a green doctor.