Sample data
The flow replayed with sample data. Use ↻ to play it again.
Register several sites in one workspace (a Japanese owned-media site, an e-commerce blog, an overseas site) and switch between them to manage articles and publish state.
Dashboards and article lists filter by site, so each owner sees only their own site's pending reviews and this week's schedule.
Each site has its own destination and routing, so the same article can reach another site without being copied.
- Several sites in one workspace
- Dashboards and article lists filtered by site
- Per-site destination and routing
- Reach several sites without copying articles
How it works
- 1An admin registers the headless and WordPress sites you publish to.
- 2Configure per-site routing to decide which paths content maps to.
- 3When creating an article or page, choose a headless page or WordPress as the destination.
- 4Publish after approval and check the publish state for every site in one place.
FAQ
Do we duplicate an article to publish it on several sites?
No. One content model is the source for several sites per market or brand.
Can sites on different stacks be mixed?
Yes. Headless Next.js sites read from the public API and WordPress sites are direct publishing targets, all managed in the same operation.
Can each market have its own destinations?
Yes. Each market can target its own set of channels.