What Is a Type?
Learn about the concept of page types and custom types and how to create and structure a new one.
Types are models for your documents. They are the place where you define and configure fields for your content. They give structure to documents: pages, posts, articles, events, products — whatever blocks of content you need for your project.
Single and reusable types
You can limit your types to a single usage. A single type might be a home page, a settings file, or a global banner.
Otherwise, your type will be reusable, which means you can create unlimited documents with it. A reusable type might be for landing pages, blog posts, or authors.
Page types and custom types
Types have two formats: “page” or “custom”.
A page type has default metadata fields and a slice zone for composing the content of web pages.
A custom type is a generic type that you can use to create menus, taxonomies, configurations, and other entities.
Create a page type or custom type
Create page types and custom types in their respective sections in Slice Machine.
From the Page types tab, click Create a page type*.* Select the type (reusable or single), give it a name, and save.
Create slices in the Slices tab of Slice Machine. You can use slices in multiple custom types.
In the slices tab, create your slices, save their models to the filesystem, synchronize them with your repository, and see slice simulations with mock data.
Click on + Add a new Field to see the list of fields you can add to custom types and slices.
Organize with tabs
You can use tabs within a custom type to organize your content fields and make document editing more user-friendly. Click the + Add a new tab button in the custom type builder to add a tab.
What happens when you modify a type?
Editing a type does not change the content in your repository — it only changes the model. Changes won’t take effect until you open and save documents individually.
If you delete a field in a type, that field will no longer appear in the Page Builder. Until you resave each document individually, all existing documents will still have that field and its data, and the field will still appear in the API response.