Blueprints for consistent pages
Define the fields and building blocks that a page needs, so editors work inside a useful structure.
Your content.
Its own shape.
Define page blueprints, reusable components, and custom content types around the information your business owns. Give structure to complexity without forcing everything into the same template.
Available in Content and Commerce
Landing page · fieldsTitleTextA field with purpose
CapacityNumber24
CoverMediacover.jpg
Structured for your frontend
Built around
the way you work.
Components worth reusing
Model a hero, a product highlight, or a FAQ once and use that structure across your experience.
Types for your own domain
Create structured records for things such as locations, events, or services, with relationships between them.
From the first step
to a useful result.
Content models & blueprints is part of a connected platform. Here is how it fits into your project.
Define
Choose fields for the information you own.
Connect
Relate entries and reusable components.
Render
Build frontend components around the model.
Put it to work
in your next project.
Location directories
Represent addresses, opening hours, and media as structured location records that your frontend can query.
Explore solutionsComplex websites
Give different page types the fields and components they need, from a campaign to a detailed service page.
Explore solutionsReusable page systems
Create a shared component vocabulary so new pages follow a consistent content structure.
Explore solutionsA closer
look.
Talk to us about the capability and the setup your project needs.
How are custom fields different?
Content models define new structures. Custom fields extend existing Ominity models, such as a product or customer.
Can AI manage these structures?
The MCP server supports managing blueprints, components, and custom content types through compatible AI tools.
Available in Content and Commerce
Check the edition, plan allowances, and any extension requirements for your instance.
Compare plans