Build modern Headless WordPress siteswhile WordPress stays your CMS.

Flx Headless is an open source framework for Headless WordPress — an API-first content layer, flexible rendering strategies, and a composable, framework-agnostic frontend architecture.

Open source and under active development.

Get Started →View on GitHub →

Why Flx Headless?

Keep WordPress as your CMS

Editors keep the WordPress admin they already know. Content, media, and workflows stay exactly where they are.

Use a modern frontend architecture

Build the frontend in the framework of your choice, decoupled from WordPress's PHP rendering layer.

Improve performance and flexibility

Choose the rendering strategy that fits each page — server-rendered, statically generated, or incrementally revalidated.

Stay open source

No proprietary lock-in. Flx Headless is developed in the open and can be inspected, forked, and extended.

Adopt incrementally

Move a single template or route to a headless frontend first, then expand at your own pace.

Features

Flx Headless is built around three capabilities.

API-First Content Delivery

WordPress as a headless CMS

Content served over the WordPress REST API and GraphQL
Editors keep the WordPress admin they already use
No PHP theme layer required in the frontend
Works with existing WordPress content and plugins

Flexible Rendering Strategies

SSR, SSG, and ISR

Server-side rendering for dynamic, request-specific pages
Static generation for content that rarely changes
Incremental static regeneration for content that changes occasionally
Choose the strategy per route, not per project

Composable Architecture

Framework-agnostic frontend

Decoupled frontend, independent of WordPress's PHP runtime
No required frontend framework — bring your own
Clear separation between content, API, and presentation
Adopt incrementally, one route at a time

View Documentation →

Latest Articles

View all articles →

2026-06-25
API-first Commerce
API-first commerce treats the commerce layer as an internal service with a defined contract. The storefront, checkout, and operations tooling all consume that API rather than sharing a runtime.
2026-06-20
Rendering Strategies
SSR, SSG, ISR, and partial prerendering each make different tradeoffs for headless WooCommerce storefronts. The right choice depends on what each route needs to know at request time.
2026-06-15
Why Headless Projects Fail
Most headless WooCommerce projects fail for the same structural reasons — not technology choices, but incorrect assumptions about what the API layer can own.