BlogsCloudflareContent Management System (CMS) Evolution

Content Management System (CMS) Evolution

Content Management System (CMS) Evolution

13
posts
2020–2026

Cloudflare's approach to content management has evolved from traditional project-based work to treating content as a product, with a dedicated focus on content design and data-driven improvements. This shift involves adopting product development mindsets, agile methodologies adapted for content, and leveraging open-source platforms. The introduction of EmDash, a new open-source, serverless CMS built on TypeScript and Astro, represents a significant advancement. EmDash aims to be a spiritual successor to the example CMS built on the Cloudflare stack, which demonstrated the power of Workers, Workers KV, Cloudflare for SaaS, and Rate Limiting, with subsequent additions of Pages and Durable Objects. The example CMS progressed through phases, starting with a robust JSON API built on Workers and Workers KV, and evolving to include a Svelte-based dashboard hosted on Cloudflare Pages, demonstrating full-stack development capabilities and best practices for testing, deployment, and organization.

2026

Redirects for AI Training enforces canonical content

4/17/2026

This 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.

Introducing EmDash — the spiritual successor to WordPress that solves plugin security

4/1/2026

Introduced EmDash, a new open-source, serverless CMS built on TypeScript and Astro, as a spiritual successor to WordPress. EmDash addresses WordPress's plugin security issues by running plugins in isolated Dynamic Worker sandboxes, granting capabilities via bindings. It also includes built-in support for x402 for Internet-native payments and content monetization.

Astro is joining Cloudflare

1/16/2026

This post announces the acquisition of the Astro Technology Company by Cloudflare. It highlights Astro's role as a framework for content-driven websites and its adoption by Cloudflare for its own developer documentation and website. The post details Astro 6's new Vite-powered development server that runs locally using the Cloudflare Workers runtime (workerd) and supports various Cloudflare services like Durable Objects, D1, and KV. It also mentions the stabilization of Live Content Collections and the addition of first-class Content Security Policy (CSP) support in Astro 6.

2025

Payload on Workers: a full-fledged CMS, running entirely on Cloudflare’s stack

9/30/2025

This post details the technical implementation of deploying Payload CMS on Cloudflare Workers. It covers creating a custom D1 adapter for Payload's SQLite support, building a custom R2 storage adapter, and integrating with Hyperdrive for database connection pooling and query caching. It also discusses performance optimizations using D1's global read replication with the 'first-primary' session type.

Open source all the way down: Upgrading our developer documentation

1/8/2025

This 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.

2022

Working in public — our docs-as-code approach

7/15/2022

This post details Cloudflare's adoption of a 'docs-as-code' approach for its product documentation. It outlines the use of Git, public GitHub repositories, GitHub Actions, and Cloudflare Pages for CI/CD, including automatic link checking and previewing changes. The post also highlights the benefits of this approach, such as leveraging familiar developer workflows, enabling external contributions, and improving team velocity through fast deployments and local builds. It further discusses strategies for handling non-public content and future plans to make the style guide and content strategy public.

We rebuilt Cloudflare's developer documentation - here's what we learned

5/27/2022

This 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.

How we treat content as a product

5/26/2022

This post details the shift in Cloudflare's Product Content Experience (PCX) team's methodology from a project-based approach to a "content as a product" strategy. This involves adopting product development mindsets, user feedback loops, and iterative development for content. The team moved content to an open-source platform, specifically Cloudflare Pages, to improve authoring tools, consolidate platforms, and foster an open-source community. This enabled them to publish content as fast as products ship and get ahead of the backlog, focusing on accessibility, consistency, and approachability. The post highlights the importance of aligning content with product release cadences and the benefits of this strategy for user experience and rapid delivery.

2021

An Open-Source CMS on the Cloudflare Stack: Introductory Post

11/19/2021

This post introduces an open-source, feature-complete SaaS application built entirely on the Cloudflare stack, serving as a template for launching SaaS applications. It details the development of an example content management system (CMS) with a focus on serverless architecture and edge-first design. The initial phase (Phase 1) focuses on building a robust JSON API using Workers and Workers KV for core functionality, including data management, schema validation, and workspace organization. Future phases will integrate Cloudflare Pages, Durable Objects, and a Svelte-based dashboard. The project emphasizes best practices for testing, automated deployments, and long-term maintainability, with a live demo and open-source repository available.

Cloudflare Pages now partners with your favorite CMS

11/17/2021

This post announces the integration of Cloudflare Pages with popular headless CMS platforms (Sanity, Strapi, Contentful, WordPress) via Deploy Hooks. This enables automated website deployments triggered by content updates within the CMS, significantly improving the developer and content creator experience by decoupling content management from code deployments.

Dark Mode for the Cloudflare Dashboard

9/29/2021

This 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.

Introducing Deploy Hooks for Cloudflare Pages

8/6/2021

This post introduces Deploy Hooks for Cloudflare Pages, enabling external systems like headless CMSs to trigger deployments. This extends the capabilities of Cloudflare Pages beyond Git-based deployments, allowing for automated content updates from various content sources and improving the workflow for content creators.

2020

Migrating to React land: Gatsby

3/26/2020

This 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.