Are we headless yet?
But there’s plenty we could improve for Wagtail’s developers
News
How to use Wagtail within a MACH architecture
An in-depth analysis of how Wagtail aligns with MACH architectures and the changes required to run it headlessly.
Believing is seeing: Why a world-class museum of visual culture chose headless Wagtail
Meet Nicolas Leung from M+ in Hong Kong and discover how they used headless Wagtail to build the perfect digital foundation for their brand new museum.
Topics
REST API
REST is one API option for Headless Wagtail
GraphQL
GraphQL is one API option for Headless Wagtail
Page Preview
Previews need a separate package currently
Images
Additional image considerations are needed for Headless Wagtail
Page URL Routing
Headless Wagtail requires different routing
Rich Text
There are currently two approaches for managing Rich Text
Multi-site support
Multi-site works differently in Headless Wagtail
Form submissions
Wagtail forms are currently unsupported in Headless
Documentation
Documentation support is in the developer docs
Private pages
Password-protected pages are currently excluded from the API
Internationalisation
This page is still TODO.
Next.js
Next.js is a frontend option for Headless Wagtail
Nuxt.js
Nuxt.js is a frontend option for Headless Wagtail
StreamField
StreamField data is available in the API
Gatsby
Gatsby is a frontend option for Headless Wagtail
OpenAPI (Swagger)
Not currently supported.
Netlify
Netlify is a frontend option for Headless Wagtail
Vercel
Vercel is a hosting option for Headless Wagtail
Decisionmaker guide: Do you need Headless Wagtail?
Not sure if Headless Wagtail is for you? Use this guide to weigh the pros and cons
Headless Wagtail vs. Traditional
Background information on headless Wagtail vs. traditional Wagtail
Issues
Github issues tagged #headless