Inline Schemas

Inline schemas let you create reusable content components that can be used across your site. Think of them as custom building blocks - once you create one, you can use it anywhere.

What are Inline Schemas?

An inline schema is a content structure that can be embedded inside other content. For example:

• A Hero Banner with heading, image, and button
• A Testimonial Card with quote, author, and photo
• A Feature Block with icon, title, and description

Once you create these, they appear as field types you can add to any entity.

Creating an Inline Schema

1. Go to Settings > Entity Types
2. Click Create Entity Type
3. Fill in the details:
   • Name: “Hero Banner”
   • Key: hero-banner (auto-generated)
4. Add fields:
   • Heading (text, required)
   • Subheading (text)
   • Background Image (image)
   • Button Text (text)
   • Button URL (text)
5. Enable Inline Mode in settings
6. Click Save and Publish

Using Inline Schemas

After creating an inline schema, it appears as a field type option:

1. Edit any entity type (e.g., Page)
2. Click Add Field
3. In the field type dropdown, you’ll see your custom types:
   • Hero Banner
   • Testimonial Card
   • Feature Block
4. Select one and configure the field

Now when editing pages, editors will see a structured form for that component.

Common Use Cases

Page Sections

Create reusable page sections that editors can mix and match:

Cards

Create consistent card layouts:

UI Elements

Create standardized UI components:

Nesting Components

Inline schemas can contain other inline schemas. For example:

Feature Grid
├── Heading
└── Features (array of Feature Card)
    ├── Icon
    ├── Title
    └── Description

This lets you build complex layouts from simple building blocks.

Mode Options

When creating entity types, you have options for how they can be used:

Inline Only

Can be embedded in other content, but can’t be created as standalone records.

Best for: Components like buttons, cards, hero banners

Standalone Only

Creates individual records that can be managed separately.

Best for: Pages, blog posts, products

Both Inline and Standalone

Can be embedded OR managed as separate records.

Best for: Reusable sections that you might want to manage centrally and embed elsewhere

Tips

• Keep components focused - Each should do one thing well
• Use clear names - The name appears in the field type selector
• Document with descriptions - Help editors understand when to use each
• Start simple - Add complexity only as needed
• Consider nesting depth - Too many levels can be hard to edit

Next Steps

• Field Types - Available field types for your schemas
• Entities - How inline schemas fit into entities
• Variants - Add targeting to your content