WordPress × Cloudflare · Static export + standalone CMS
Single pages are exported to R2 as static HTML, while lists render live from D1. Move an existing WordPress site onto Cloudflare in one go — or leave WordPress behind and build with the built-in CMS.
Keep WordPress, or start a brand-new site. Same data layer, same rendering layer.
Keep the editing experience you know. The plugin generates static pages, syncs to D1, uploads to R2, and can capture your current theme as a style pack.
Explore the plugin → 02 / CMSNo WordPress required. D1 holds content, R2 holds single pages, and the admin ships with Markdown and rich-text editors, a media library, and comment moderation.
Deploy the CMS →Purely static is rigid; purely dynamic is slow. This splits the two so each does what it does best.
Posts are pre-rendered to HTML and stored in R2; lists, categories, tags, and archives query D1 live, so publishing updates instantly.
Internal template render → front-end fetch → hardcoded fallback. Large exports no longer fail wholesale on a single timeout.
A style is just a directory plus a tpl.json. Switching takes effect immediately, with 14 built-in styles ready to use.
Beyond Cloudflare, publish to S3, GitHub, Netlify, Vercel, FTP, WebDAV, or a local directory.
Comments live in D1 and are injected when the page is served. Approved comments appear instantly without a rebuild — and can sync back to WordPress.
A subset of the WordPress REST write API plus application passwords. Obsidian plugins, scripts, and any HTTP client can publish.
The free tier is enough for a personal site. Install the plugin, fill in three IDs, hit publish.