JSON-first editor core
Page, layout, block, preset, migration, validation, and structured-data contracts are implemented as typed JSON documents.
This is the current engineering surface, not a mock roadmap. Everything listed here is already implemented in the workspace and exercised in the playground runtime.
Page, layout, block, preset, migration, validation, and structured-data contracts are implemented as typed JSON documents.
Astro routes can turn a page document into preview HTML, head tags, and JSON-LD with one render artifact contract.
D1 stores page metadata and versions, KV stores preview cache, and R2 is available for large document snapshots.
Current draft and published live versions are now separated with explicit publish and unpublish operations.
The implementation is intentionally split so the editor contract can be reused across standalone Astro apps and Cloudflare-backed projects such as to.gether.
Typed contracts, validation, presets, migrations, and structured data collection.
Typed AI proposals with host-authorized document changes and auditable execution results.
Astromer-flavored layout and block registry pack.
Astro preview rendering, head tags, and JSON-LD output helpers.
D1, KV, and R2 repository helpers for page versions and previews.
Product-focused document helpers for affiliate and commerce integrations.
Reusable editor commands, fields, outline, preview, publishing, and persistence surfaces.
Shared draft, session, save, and host-adapter state for editor interfaces.
The demo page renders a sample document through the same pipeline used by the preview route and exposes the current API surface for storage and publishing checks.
Preview the sample page output, generated head tags, FAQ structured data, and registry-backed block rendering in one place.
GET /api/editor/healthInspect runtime bindings and migration statement availability.POST /api/editor/pagesCreate a page row and initial version document in D1.POST /api/editor/pages/[slug]/publishPromote the current version to the live published version.GET /preview/[key]Render a KV-cached preview document through the Astro pipeline.The current deployment uses a Cloudflare Worker with static assets. Astro server routes and editor APIs run through the Worker while static files use its Assets binding.
| Cloudflare Worker + Static Assets | Serve the Astro playground, SSR routes, and editor API routes from the configured Worker entrypoint. |
|---|---|
| D1 | Page rows, version rows, publish state, and ownership metadata. |
| KV / R2 | KV caches previews; R2 stores uploaded media and large JSON snapshots. |