01Guide
Content that is code: using Shapio's code field
You will have a code field for a game's dialogue script, an app's config and a site's head tag, and know how each one reaches its client.
· 4 min · Astro
Blog
What we think, and how to do things.
Guides for building on Shapio, and arguments about how a CMS should work. Releases live in the changelog.
All posts
Inside this post · 2 images - 02Guide
I didn't build redirects into my CMS
I took redirects off Shapio's feature list because a content type and a build step already do the job.
· 4 min · Astro · Next.js · SvelteKit
- 03Guide
See saved drafts on your development server
You will have a local site that reads saved drafts, shows a Drafts badge, and lets you check changes without publishing.
· 3 min · Astro · Next.js · SvelteKit
- 04Opinion
Drafts had to be a permission, not a flag
Testing saved content on a development server should require permission to read drafts, without turning Publish into a development tool.
· 3 min · Astro · Next.js · SvelteKit
- 05Guide
Move a Strapi 5 project to Shapio with the importer
You will have your Strapi 5 models, media and content in Shapio, as drafts plus a change set that publishes them when you ship it.
· 4 min
- 06Guide
Deploy a Shapio site to Cloudflare Pages and rebuild on publish
You will have a static Astro site on Cloudflare Pages that rebuilds when you publish, with deployment status tracked in Shapio.
· 4 min · Astro
- 07Guide
Schema as code: pull your content model into git and apply it live
You will have canonical schema files and their lock file committed in git, ready to apply to production with a per-model version guard.
· 4 min
- 09Opinion
Why headless
I want content to be data, the front end to be mine, and the schema to be a contract both sides can work against.
· 3 min
