A model is a paradigm—a pattern for something else. Builder offers three kinds of models that define content types:
You use these models as the defining source for content entries. Like a rubber stamp, the model provides a basic foundation. Each time you use a rubber stamp, the fundamental characteristics are the same but you might use the resulting image differently by varying other factors such as color and surface.
Similarly, with models in Builder you can define what a Page, Section, or collection of Data is and use those models over and over to build your site and populate it with content. And you can create as many models as you like.
The following graphic compares Builder models. Follow the Try it out link to play with a demo of each.
All models in Builder support:
- A/B Testing: Test different versions of your content.
- Targeting and Scheduling: Deliver the right content to the right people at the right time.
- Roles and permissions: Admins and Developers can edit models by default, but you can also specify permissions by content model using Custom Roles.
This means that you can granularly grant permissions, test, and precisely deliver content.
When you use models to build your app, you can create exactly the Pages, Sections, and Data specific to your use case. With your integrated app, you can, for example, use your Sections in the Pages you choose as well as reuse Data wherever you need it.
Examples of models include:
- A seasonal announcement banner placed on a page between certain dates.
- Marketing tile targeting a specific persona on certain pages.
- Blog authors whose profiles you want to link to from different parts of your site.
By creating models for each type of content you need, you can ensure consistency while making the process of iterating more efficient. The developer creates and integrates a model and non-developer teammates can use that model to create as many content entries as they need.
The following diagram shows a typical Builder documentation page. The left side navigation is a Section, the body of the document is a Page, and the font colors are stored in a Data content entry.
To get the most out of Builder Models, be sure to integrate and learn about each type of model:
- Page Model: Learn what a Page model is and how to use one.
- Integrating Pages: Integrate Page building with your code base so non-dev team members can create as many pages as they need and developers can focus on code.
- Section Models: Learn about Section use cases and how to use Sections in your app.
- Integrating Sections: Integrate Builder Sections with your codebase so teammates can create and use Sections wherever they need them.
- Data Models: Give shape to data and learn how to query that data.
- Integrating CMS Data: Integrate data to create reusable data across your site.
- Custom Fields: Learn about the wide array of options available for shaping your models.
Looking to hire a third party to help with your project?
Submit a project request and our partnerships team will reach out to connect you with an Expert from our partner ecosystem.