Skip to content

Content Type Builder

The Content Type Builder allows you to create and customize the structure of your content by defining content types and their fields.

Overview

Content types define the structure of your content. Each type has specific fields that determine what information can be stored.

Page Layout

  • Create Content Type button - Add new type
  • Content Types List - All existing types
  • Field Editor - Configure fields for selected type

What is a Content Type?

A content type is a template that defines:

  • What fields content has
  • What kind of data each field stores
  • Validation rules
  • Display settings

Examples:

  • Blog Post: title, author, content, featured image
  • Product: name, price, description, images
  • Team Member: name, role, bio, photo

Common Tasks

Creating a Content Type

  1. Click + Create Content Type
  2. Enter type details:
    • Display Name - Human-readable name
    • API ID - Technical identifier
  3. Click Create
  4. Add fields to the type

Adding Fields

  1. Select content type
  2. Click + Add Field
  3. Choose field type:
    • Text
    • Rich Text
    • Number
    • Date
    • Media
    • Boolean
    • Relation
    • etc.
  4. Configure field settings
  5. Save

Field Configuration

For each field, configure:

  • Name - Field identifier
  • Label - Display name
  • Required - Must be filled
  • Default - Default value
  • Validation - Rules (min/max, pattern)
  • Hint - Help text

Editing Fields

  1. Select content type
  2. Click on field
  3. Modify settings
  4. Save changes

Deleting Fields

  1. Select content type
  2. Click delete on field
  3. Confirm deletion

Warning: Deleting fields removes data from existing content.

Reordering Fields

  1. Select content type
  2. Drag fields to reorder
  3. Save new order

Field Types

TypeUse For
TextShort text, titles
Rich TextFormatted content, articles
NumberPrices, quantities
DateDates and times
MediaImages, files
BooleanYes/No options
EnumerationDropdown options
JSONComplex data
RelationLinks to other content
ComponentReusable field groups

Best Practices

Naming

  • Use clear, descriptive names
  • Follow consistent naming convention
  • API IDs should be lowercase, no spaces

Structure

  • Group related fields
  • Keep types focused
  • Don't overload with too many fields
  • Use components for repeated structures

Planning

  • Plan types before creating
  • Consider how types relate
  • Think about API usage

Tips

  • Start Simple - Begin with basic fields
  • Test Early - Create sample content to test
  • Document - Note what each field is for
  • Version Control - Track changes to types
  • Consider Relations - Plan how types connect

💡 Note: Plan your content types carefully - changes can affect existing content.

Released under the MIT License.