Astro-native block editor stack for Cloudflare

Astrologistic

A reusable JSON page block editor foundation for Astro projects that need fast rendering, predictable schema contracts, Cloudflare storage adapters, and structured data that stays attached to the block model.

Open DemoGitHub

Current Capabilities

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.

JSON-first editor core

Page, layout, block, preset, migration, validation, and structured-data contracts are implemented as typed JSON documents.

Astro render pipeline

Astro routes can turn a page document into preview HTML, head tags, and JSON-LD with one render artifact contract.

Cloudflare storage flow

D1 stores page metadata and versions, KV stores preview cache, and R2 is available for large document snapshots.

Publish workflow

Current draft and published live versions are now separated with explicit publish and unpublish operations.

Workspace Packages

The implementation is intentionally split so the editor contract can be reused across standalone Astro apps and Cloudflare-backed projects such as to.gether.

editor-core

Typed contracts, validation, presets, migrations, and structured data collection.

editor-astromer

Astromer-flavored layout and block registry pack.

editor-astro

Astro preview rendering, head tags, and JSON-LD output helpers.

editor-cloudflare

D1, KV, and R2 repository helpers for page versions and previews.

Demo Surface

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.

Sample Render

Preview the sample page output, generated head tags, FAQ structured data, and registry-backed block rendering in one place.

Open /demo

Current API Routes

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.

Deployment Direction

The current recommendation is to deploy the Astro-facing playground on Cloudflare Pages and reserve Workers for service extraction when the editor backend grows beyond the site boundary.

Cloudflare PagesPlayground, docs, demo, and Astro SSR frontend.
Cloudflare WorkersFuture extracted editor APIs, auth flows, and service-level runtime control.
D1Page rows, version rows, publish state, and ownership metadata.
KV / R2Preview cache, transient state, and large JSON snapshot storage.