Many content types.
One understandable system.
Connect structured content, relationships, languages, and custom fields so a growing website stays coherent behind the scenes.
Complex information.
A structure people can follow.
Model the relationships first, then compose pages around them. Give languages, media, access, and delivery a clear place as the website grows.
A directory, a story, a person.
Connected by design.
Use custom content types for meaningful records such as locations, authors, and articles. Relationships let a page use the right information while keeping its source record clear.
- Describe each record with purposeful fields
- Connect related people, places, and stories
- Avoid copying shared information into every page
Make the page flexible.
Keep the information coherent.
Blueprint components give editors a structured way to assemble pages. The page can arrange a hero, record collection, story, or form without asking contributors to redefine the content model each time.
- Build a reusable library of page components
- Keep editorial fields separate from layout code
- Render consistent patterns through your frontend
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.
Assets belong
to the information they support.
Connect images and files to the content records that use them. Start with the plan’s included media allowance or configure your own S3-compatible storage when the project needs its own provider.
- Connect cover images, galleries, and documents
- Use the included allowance for your plan
- Bring your own S3-compatible provider
Assets stay connected to the content records that use them.
Assets stay connected to the content records that use them.
The same model.
The wording each language needs.
Keep the structure consistent across languages while allowing field-level translations. Inherit source content where it should stay shared and prepare selected sets through bulk auto translation.
- Use optional field-level language overrides
- Keep default-language inheritance visible
- Translate a complete content set together
More content. One task.
Select a content set and the languages to prepare.
Give each contributor
an appropriate role.
Use administrator accounts and permissions to define who can work with the website’s content and configuration. Keep meaningful changes traceable through the execution pipeline.
- Resolve the actor and allowed operation
- Keep configuration access deliberate
- Follow the changes and decisions in their timeline
Explore the details.
The capabilities, examples, and integration choices behind this solution.
More content.
A clearer system.
Map the content and relationships your website owns, then choose the models and workflows that keep it understandable.