Cloudflare announced that its official blog migrated to EmDash, a CMS designed to work with Astro and Cloudflare. The update included a redesign with dark mode and other user-facing improvements as part of a broader migration effort. Cloudflare states it acted as Customer Zero—testing and refining the platform in production to benefit its own products and customers.
ARCHITECTURE AND PERFORMANCE FOUNDATIONS
The new blog runs on EmDash hosted on a Cloudflare Worker, behind the Workers Cache, and uses EmDash’s object cache built on Workers KV. It also leverages Cloudflare’s Hyperdrive integration with PlanetScale. Multiple caching layers are employed to improve speed and resilience, with about 99.5% of static files served from cache and roughly 70% of requests served from cache. TechStaged has also covered Google Details AAOS SDV: Secure-by-Design Android Automotive OS Renews Vehicle Software Trust with Virtualization, Hardware Identity, and Memory Safety.
FRONTEND REDESIGN AND DESIGN LANGUAGE ALIGNMENT
Beyond backend changes, the migration aligned the blog’s frontend with Cloudflare’s updated visual language. The frontend was rebuilt using patterns from the Kumo design system, creating visual and structural consistency with other Cloudflare properties. The redesign also added native light and dark modes, with accessibility considerations applied across themes.
USER-FACING UX IMPROVEMENTS
Several UX details were addressed during the migration, including moving the email subscription prompt to a dedicated call-to-action block at the bottom of posts to reduce confusion with the search field. Additionally, two new sidebar features were introduced on interior post pages: an On This Page table of contents on the right and a Discuss Online section on the left to encourage engagement.
ZERO-DOWNTIME ROLLOUT AND TRAFFIC ROUTING
To ensure a safe transition, Cloudflare deployed a proxy Worker that routes traffic between the legacy blog and the new EmDash-powered site using a version cookie. If the new site encountered issues, traffic could fallback to the legacy blog. The rollout started with 1% of traffic, then expanded to 5%, 15%, and beyond, eventually shifting all traffic to the new platform.
EARLY PERFORMANCE INDICATORS AND LOAD HANDLING
Early data show the new architecture delivered a faster, more stable reading experience, with p95 latency remaining flat under load versus the previous setup. The system has been able to serve up to 850 requests per second in production and withstood a DDoS event of 28,000 RPS without noticeable impact, thanks to Cloudflare’s protections.
DEVELOPER TOOLS AND NO-COST AGENT CAPABILITIES
As part of the migration, Cloudflare introduced an MCP (Model Context Protocol) server for the blog and for EmDash, enabling agents and authors to browse, create, edit, publish, schedule posts, and manage media. The MCP is provided as part of the platform at no additional cost, reflecting a broader trend toward agent-facing tooling in the CMS space.
WHAT HAPPENS NEXT
Cloudflare notes ongoing improvements based on internal testing and reader feedback, including bug fixes for scheduling and editor quirks observed during the migration. The company highlighted the Birthday Week as a test period for the new system and indicated that fixes for scheduling-related issues would be addressed by the EmDash team.
RELATED COVERAGE
- Google Details AAOS SDV: Secure-by-Design Android Automotive OS Renews Vehicle Software Trust with Virtualization, Hardware Identity, and Memory Safety
- AudioWorldSim: Realistic Binaural Audio Datasets For World Models Debuts on arXiv
- Time-Aware Transformer-Based Prediction Model for AECOPD Debuts on arXiv
- New arXiv preprint examines Graph-JEPA's category-conditional collapse and proposes diagnostics and repairs
- Software articles
SOURCES
- Cloudflare Blog: The Cloudflare Blog – Brought to you by EmDash Published · Primary source
