Content Hub
Reusable modules with a single source of truth. Place a shared section on many pages; edit it once in the Hub and every placement updates.
- Shared modules & “where used”
- Version history & restore
Compose pages visually, on the real frontend you already built. Edit structured content safely. Publish to Next.js — without giving up developer control of the code.
Compozer brings editors, developers and content operations into one governed workflow. Teams can build experiences visually, manage reusable structured content and prepare that content for delivery through a developer-friendly Content API.
Open a project. Click any section on the canvas. The inspector adapts to that section's schema, and edits flow straight into the live frontend through the preview bridge — no flicker, no mocked styles.
A short film in memory of Adam, Sophiia and Tetiana.
Content lives in the platform, not trapped in one page. Reusable modules live in the Content Hub; every image and file lives in the Media Library. Edit once, reuse across projects — with scope-aware sharing that decides where each resource is visible.
Reusable modules with a single source of truth. Place a shared section on many pages; edit it once in the Hub and every placement updates.
Every image, video and document in one place, with alt text, captions and usage tracking. Replace an asset and it swaps wherever it's referenced.
Resources carry a scope — Project, Workspace or Organisation. Promotion is one verb; sharing is a consequence of scope, not a separate library to maintain.
Compozer doesn't ask you to rebuild. Point it at an existing Next.js repository — it reads your section components, infers the schema, and seeds a working page tree you can edit on day one.
Authorise GitHub, read-only. Compozer never pushes to main unless you ask it to.
Your components/sections are parsed into typed section schemas — hero, media-text, card-grid and the rest.
Existing routes become editable pages, each mapped to its sections, with content pulled from the code.
Open the visual editor and start composing. Publishing writes back through the bridge to your real frontend.
The editor, the API and your frontend import the same typed schema. Add a field and the inspector, the validator and the renderer all know about it — at compile time, not by convention.
Compozer AI is designed to help teams draft, rewrite, localise and prepare structured content inside the same schema, roles and review process as the rest of the platform. It can assist with imports, suggest schema mappings, prepare scheduled content, and propose new sections or component changes for review — without bypassing governance.
Generate and refine content inside typed fields, not free-form page blobs.
Assist with WordPress and legacy CMS imports by mapping pages, blocks and assets into Compozer sections.
Prepare campaign content, scheduled updates and reusable modules for editor review before publishing.
Suggest schema changes, new sections or component mappings as reviewable changes, not hidden magic.
We're onboarding a small number of teams during the private preview. If you ship a component-based site and want structured, visual editing without losing the codebase — let's talk.