More room for your ideas.
Less friction to publish.
Build campaigns from reusable blueprints. Keep your content, languages, and media together while your developers shape the experience.
A campaign needs
more than a publish button.
Prepare the message, adapt it for each language, and make every change easy to review. Build a repeatable way to launch the next campaign.
Keep the campaign moving.
Keep the structure dependable.
Build a landing page from blueprint components instead of a blank content field. A hero, collection story, and signup form give each campaign a familiar structure while leaving the wording and frontend design flexible.
- Compose pages from a shared component library
- Edit content without rewriting the frontend
- Reuse a useful structure for the next campaign
Workshops
Event teaserDefault language (English)
Learn to brew at the roastery
Default language (English)
Each month, join us at the roastery for filter coffee, espresso, and milk foam. Maximum eight participants.
Choose a blueprint.
Insert a component at this position.
Interactive example. Select a component to inspect its fields.
The whole campaign.
In the languages you need.
Translate a selected set of pages and content to multiple target languages in one task. Default-language inheritance keeps shared values clear, and optional field overrides let each market have its own wording.
- Prepare a complete set with bulk auto translation
- Override only the fields that need local wording
- Review the result alongside the source content
More content. One task.
Select a content set and the languages to prepare.
Ask for help.
See what will change.
Let the assistant prepare a page or propose content changes. It presents the actions for approval, so your team can inspect the scope and choose whether the proposed writes should proceed.
- See the records and actions in the proposal
- Approve useful changes or deny the proposal
- Follow execution after an action is accepted
I will create the page from the Default layout, then insert the Event teaser blueprint. Both steps change content, so I need your approval first.
cms_create_pageWRITEname: Spring workshops, layout: Default
cms_add_page_componentWRITEblueprint: Event teaser, position: 1
Make the response
as useful as the campaign.
Create a form around the information your campaign needs. A workshop registration and a project enquiry ask different questions; both can use typed fields and the rendering integration in your frontend.
- Choose questions for this campaign’s goal
- Use field types and validation deliberately
- Keep the branded form experience in your frontend
The field definition stays structured.
Your frontend controls the presentation.
Local rendering preview. No answers are submitted.
Look beyond
the landing page.
Use visitor tracking to connect the relevant interactions around a campaign. Choose the events that answer your team’s question, from reaching the page to opening the form or exploring a related story.
- Follow the interactions you choose to instrument
- Connect frontend activity to useful project context
- Integrate the reports or external services you need
{ event: "page.viewed", page: "/summer" }Your implementation chooses its tracking events and when they run.
{ event: "story.opened", page: "/stories/roastery" }Your implementation chooses its tracking events and when they run.
{ event: "form.opened", page: "/enquire" }Your implementation chooses its tracking events and when they run.
Explore the details.
The capabilities, examples, and integration choices behind this solution.
Your next campaign.
A clearer way to launch it.
Compose the content, prepare the languages, and connect the interactions that matter to your team.