Content Types Overview

A ContentType defines a specific kind of content (e.g., “Article”, “BlogPost”) and specifies its layout structure through a layout component. ContentTypes follow the same versioning pattern as other resources, with draft and published status, while maintaining references to specific package versions for component stability.

Key Concepts

Content Structure

Define expected content structure through a layout component and specify which components can be used via an allow list.

Status Management

Support draft and published status with iterative development and version history.

Version Control

Independent versioning from packages with complete version history and rollback support.

Package Binding

Reference specific package versions to ensure component stability across content.

The ContentType Object

string

Unique identifier (UUID)

string

Display name of the type (e.g., “Article”)

string

Structured markdown description for semantic search and LLM understanding

string

Current status: draft, modified, published, unpublished, or deleted

number

Current version number (increments on publish)

number

Last published version number (null if never published)

string

Reference to the layout Component that defines the structure

array

Array of component IDs or component groups that can be used within this content type

string

Version of package to use for component resolution

object

JSON Schema auto-generated from layout and allowed components (system-managed)

string[]

Array of pre-built content example IDs

object

Access control settings

Show properties

string[]

Roles that can create content

string[]

Specific users that can create content

object

Publishing permission settings

object

Additional type metadata

Show properties

string

Creator of the type

string[]

Type categories

string[]

Supported locales

string

Last publish timestamp

string

Last publisher

string

Creation timestamp (ISO format)

string

Last update timestamp (ISO format)

Example ContentType

{
  "id": "ct123",
  "name": "Article",
  "description": "Standard article content type for long-form written content...",
  "status": "published",
  "version": 3,
  "lastPublishedVersion": 3,
  "layoutComponentId": "c123",
  "componentIdsAllowList": [
    "c124",
    {
      "id": "questions",
      "name": "Question Components",
      "componentIds": ["c125", "c126"]
    }
  ],
  "packageVersion": "1.0.0",
  "schema": { ... },
  "templateContentIds": ["cont123", "cont124"],
  "permissions": {
    "roles": ["editor", "journalist"],
    "users": ["jane.doe@metabind.ai"],
    "publish": {
      "roles": ["editor"],
      "users": []
    }
  },
  "metadata": {
    "author": "admin@metabind.ai",
    "tags": ["article", "content"],
    "locales": ["en-US", "es-ES", "fr-FR"]
  },
  "createdAt": "2024-03-20T10:00:00Z",
  "updatedAt": "2024-03-20T15:00:00Z"
}

Component Allow List

The componentIdsAllowList field supports two formats:

Simple Component IDs

{
  "componentIdsAllowList": ["c124", "c125", "c126"]
}

Grouped Components

Group related components with optional display names:

{
  "componentIdsAllowList": [
    "c124",
    {
      "id": "questions",
      "name": "Question Components",
      "componentIds": ["c125", "c126"]
    },
    {
      "id": "answers",
      "name": "Answer Components",
      "componentIds": ["c127", "c128"]
    }
  ]
}

Field	Type	Required	Description
`id`	string	Yes	Unique identifier for the group
`name`	string	No	Display name for the group
`componentIds`	string[]	Yes	Component IDs within this group

Group IDs must be unique within the content type. Component IDs can appear in multiple groups. Both formats can be mixed in the same array.

Schema Generation

ContentTypes automatically generate a comprehensive JSON Schema that:

Includes complete component definitions using the oneOf pattern
Provides full property schemas for each allowed component
Enables LLM understanding with complete structural information

When a ContentType is saved, the system:

Fetches the layout component schema
Fetches schemas for all allowed components
Generates a oneOf array for component options
Uses the schema to validate content on creation and update

Description Best Practices

The description field follows a structured markdown format optimized for semantic search:

[Purpose and content structure summary]. [Target audience or use case].

**Content structure:**
- [Main content areas/sections]
- [Supported media types]

**Best for:**
- [Use case 1]
- [Use case 2]

**Typical length:** [Expected content volume]
**Supported platforms:** [Platform list]

Aim for 400-600 characters. Maximum is 800 characters.

Getting Started

API Basics

Organizations

Projects

Saved Searches

Folders

Components

Component Assets

Collections

Packages

Draft Packages

Content Types

Content

Assets

Asset Searching

Tags

Roles

API Keys

Content Types Overview

Key Concepts

Content Structure

Status Management

Version Control

Package Binding

The ContentType Object

Example ContentType

Component Allow List

Simple Component IDs

Grouped Components

Schema Generation

Description Best Practices

​Key Concepts

Content Structure

Status Management

Version Control

Package Binding

​The ContentType Object

​Example ContentType

​Component Allow List

​Simple Component IDs

​Grouped Components

​Schema Generation

​Description Best Practices

Key Concepts

The ContentType Object

Example ContentType

Component Allow List

Simple Component IDs

Grouped Components

Schema Generation

Description Best Practices