TechPrufer
Get started
Cloudflare
Cloudflare logoCloudflare · Feature trail

Content Management System (CMS) Evolution

15 posts · Mar 2020 – Sep 2026

What this trail covers

Cloudflare Pages has evolved to support headless CMS integrations through Deploy Hooks, enabling automated deployments triggered by content updates. This enhances the developer experience by decoupling content management from code deployments and allows marketing teams to update sites autonomously. Partnerships with Sanity, Strapi, Contentful, and WordPress are highlighted, with ongoing efforts to build further integrations. Deploy Hooks allow external services to trigger site builds on Pages via EmDash 1.0 is a stable, free, and open-source CMS built on Astro, ready for production websites, agency platforms, and hosting company site-building experiences. It integrates editorial, media, localization, migration, and deployment workflows. A decentralized plugin registry allows developers to publish without central marketplace ownership, and site owners can discover and install plugins directly from within EmDash. Key features include production-tested editorial workflows, media management, localization, migration, and deployment capabilities. Performance optimizations include KV object caching, Hyperdrive database adapter, and Workers Cache compatibility, spawned from the Cloudflare Blog migration project. The plugin registry is built on AT Protocol, enabling decentralized publishing and discovery.

All Cloudflare trails
  1. EmDash 1.0: the stable CMS with a secure plugin registryEmDash 1.0 is released as a stable, free, and open-source CMS built on Astro. It integrates editorial, media, localization, migration, and deployment workflows. Performance optimizations like KV object caching, Hyperdrive database adapter, and Workers Cache compatibility are now widely available. A decentralized plugin registry is launched, built on AT Protocol, allowing developers to publish plugins without central marketplace ownership and site owners to discover and install them directly from EmDash.
  2. The Cloudflare Blog – Brought to you by EmDashThis post details the migration of the Cloudflare Blog to EmDash, a new CMS built on Astro and Cloudflare Workers. The migration involved significant technical work on the backend architecture, including the use of Cloudflare Workers, Workers Cache, Workers KV for an object cache, and Hyperdrive integration with PlanetScale. Performance testing using k6 was conducted to ensure scalability under various traffic loads. The frontend was redesigned using the Kumo design system, incorporating light/dark modes and improving UX for email subscriptions and navigation. A proxy Worker was implemented for a zero-downtime rollout strategy, demonstrating a safe migration pattern.
  3. Redirects for AI Training enforces canonical contentThis post introduces 'Redirects for AI Training,' a new feature that leverages existing canonical tags to enforce that verified AI training crawlers are redirected to up-to-date content. This directly addresses the challenge of AI crawlers ingesting deprecated documentation and other content, ensuring that AI models are trained on current information. It also enhances Radar's AI Insights with response status code analysis for AI crawlers, providing visibility into how the web responds to them.
  4. Introducing EmDash — the spiritual successor to WordPress that solves plugin securityIntroduced EmDash, a new open-source, serverless CMS built on TypeScript and Astro, as a spiritual successor to WordPress. EmDash addresses WordPress's plugin security crisis by running plugins in isolated Dynamic Worker sandboxes, granting them only explicitly declared capabilities via bindings. This model allows plugins to have any license and be trusted without revealing their source code. EmDash also includes built-in support for the x402 payment standard for content access.
  5. Payload on Workers: a full-fledged CMS, running entirely on Cloudflare’s stackThis post details the technical implementation of deploying Payload CMS, a Node.js/Express.js and Next.js application, entirely on Cloudflare's Developer Platform. It covers the creation of custom adapters for Cloudflare D1 (SQLite-based managed database) and R2 (object storage) to integrate with Payload's existing database and storage mechanisms. Key technical contributions include: a custom D1 adapter that maps D1 results to the format expected by libSQL/Drizzle ORM, enabling database migrations via Wrangler remote bindings; a custom R2 storage adapter that leverages the R2 binding for uploads and downloads, addressing Miniflare compatibility issues; and the use of Hyperdrive to front an external Postgres database for connection pooling and query caching. It also discusses performance optimizations for D1 using read replicas with the 'first-primary' session type and the serverless benefits of running a CMS on Cloudflare Workers.
  7. Open source all the way down: Upgrading our developer documentationThis post details the migration of Cloudflare's developer documentation site from Hugo to Astro/Starlight. The migration involved significant technical work, including the use of Markdown ASTs and the 'astray' utility to transform content structures (e.g., code block front matter to meta attributes). It highlights the benefits of Astro and Starlight, such as enhanced content organization, extensibility, improved development experience with type-checking and linters, and better CSS management. The post also quantifies the migration effort in terms of files changed and lines of code removed, and discusses lessons learned, including the value of community involvement.
  8. We rebuilt Cloudflare's developer documentation - here's what we learnedThis post details the migration of Cloudflare's developer documentation website from Gatsby to Hugo and its convergence onto a single Cloudflare Pages instance. Key technical contributions include: the development of a migration script utilizing AST parsing (mdast-util-from-markdown, mdast-util-to-markdown, astray) to convert MDX to standard Markdown, the implementation of a code formatter script using Prettier to ensure code snippet validity and syntax correctness, and the creation of a Makefile to orchestrate the migration process. The migration resulted in over one million automated changes across nearly 5,000 files.
  9. An Open-Source CMS on the Cloudflare Stack: Introductory PostThis post introduces the 'production-saas' open-source project, a feature-complete SaaS application built entirely on the Cloudflare stack, serving as a template for developers to launch their own SaaS applications. It details the evolution of CMS architectures and outlines the development roadmap in milestones. Phase 1 focuses on building a robust JSON API using Workers and Workers KV for core CMS functionality (workspaces, content management, schema validation), with plans to integrate Stripe, SendGrid, and Cloudflare for SaaS. Phase 2 will introduce a Svelte/Tailwind CSS dashboard hosted on Cloudflare Pages, integrating with the Phase 1 API and leveraging Pages features like preview deployments and automated rollbacks.
  10. Cloudflare Pages now partners with your favorite CMSThis post introduces Cloudflare Pages' Deploy Hooks feature, which allows for automated deployments triggered by HTTP POST requests. It explains how to create and configure these hooks within the Pages interface and integrate them with headless CMS platforms like Sanity, Strapi, Contentful, and WordPress. The core technical contribution is the mechanism for external systems to trigger site builds and deployments on Pages.
  11. Dark Mode for the Cloudflare DashboardThis post introduces the implementation of dark mode for the Cloudflare Dashboard, highlighting how the existing design system and color primitives facilitated rapid development. It details the technical approach of inverting luminosity scales and the iterative process of refining colors and component states for optimal accessibility and user experience in a dark theme.
  12. Introducing Deploy Hooks for Cloudflare PagesIntroduced Deploy Hooks for Cloudflare Pages, allowing external services to trigger site deployments via HTTP POST requests. This enables automated content updates from headless CMSs and other services without requiring a git push. Users can create named deploy hooks targeting specific branches. The feature also provides a cURL snippet for manual or CI/CD triggered deployments.
  13. Migrating to React land: GatsbyThis post details the migration of Cloudflare Workers' developer documentation from Hugo to Gatsby. It highlights the challenges of using Hugo's templating language for complex, interactive content and the benefits of Gatsby's React-based framework for improved developer experience, code readability, and future feature development. The post also outlines the technical steps involved in migrating markdown files and creating pages using MDX and Gatsby's GraphQL data layer, emphasizing a piece-by-piece conversion to preserve existing styling and logic.