Content Overview

A Content item is a concrete instance of a ContentType that follows the structure defined by its associated layout component. Content items maintain status-based versioning (draft/published) and reference specific package versions for stability.

Key Concepts

ContentType Binding

References a specific ContentType version that determines the layout, allowed components, and package version.

Self-Contained

Stores type version reference and maintains derived package and layout references for rendering stability.

Template Support

Content can serve as templates that inherit type structure and can be used as starting points for new content.

Compiled Output

System automatically generates BindJS code from JSON content structure for native rendering.

The Content Object

string

Unique identifier (UUID)

string

Reference to the ContentType

number

Version of the ContentType used

number

Content version number (increments on publish)

number

Last published version number (null if never published)

string

Package version being used (derived from typeVersion, immutable)

string

Display name

string

Structured markdown description for semantic search

string

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

boolean

Indicates if this is a template content

object

JSON structure where layout properties and component arrays are direct properties

string

Auto-generated BindJS code for rendering (system-managed)

string[]

Categories/attributes for filtering

object

Additional content metadata

Show properties

string

Creator of the content

string

Publication timestamp

string

Publisher of the content

string

Content locale

string

Creation timestamp (ISO format)

string

Last update timestamp (ISO format)

Example Content

{
  "id": "cont124",
  "typeId": "ct123",
  "typeVersion": 2,
  "version": 1,
  "lastPublishedVersion": 1,
  "packageVersion": "1.0.0",
  "name": "Getting Started Guide",
  "description": "Getting Started with Metabind. A comprehensive guide...",
  "status": "published",
  "isTemplate": false,
  "content": {
    "title": "Getting Started with Metabind",
    "subtitle": "Your complete guide",
    "heroImage": "asset124",
    "author": "Jane Doe",
    "components": [
      {
        "type": "ArticleParagraph",
        "text": "Welcome to Metabind..."
      },
      {
        "type": "ArticleHeading",
        "text": "Key Features",
        "level": 2
      }
    ]
  },
  "compiled": "const body = () => { ... }",
  "tags": ["Technology", "Tutorial"],
  "metadata": {
    "author": "jane.doe@metabind.ai",
    "publishedAt": "2024-03-21T14:30:00Z",
    "locale": "en-US"
  },
  "createdAt": "2024-03-21T10:00:00Z",
  "updatedAt": "2024-03-21T14:30:00Z"
}

Content Structure

Content is stored as JSON where layout properties and component arrays are direct properties:

Single Section Example (Article)

{
  "title": "Getting Started with Metabind",
  "author": "Jane Doe",
  "publishDate": "2024-03-21",
  "heroImage": "asset456",
  "components": [
    {
      "type": "ArticleParagraph",
      "text": "Welcome to Metabind..."
    },
    {
      "type": "ArticleHeading",
      "text": "Key Features",
      "level": 2
    }
  ]
}

Multi-Section Example (Quiz)

{
  "layout": "split",
  "shortTitle": "Math Quiz 1",
  "questions": [
    {
      "type": "Paragraph",
      "text": "What is the value of pi to 2 decimal places?"
    }
  ],
  "answers": [
    {
      "type": "AnswerMultipleChoice",
      "options": ["3.12", "3.14", "3.16", "3.18"],
      "correct": 1
    }
  ]
}

Key Principles

Direct Properties: Layout properties and component arrays are direct properties of the content object
Layout Properties: Properties defined by the layout component (title, subtitle, etc.)
Component Arrays: Arrays of components, conventionally named “components” but can be any name
Multiple Sections: Layouts can define multiple component arrays (e.g., “questions”, “answers”)
Type Validation: All properties validated against the ContentType’s generated schema

Description Best Practices

Content descriptions follow a structured format for semantic search:

[Title or headline]. [Brief summary of the content].

**Topics:** [Main topics covered]
**Key points:** [Primary takeaways]
**Length:** [Word count or duration]
**Language:** [Content language]

Aim for 250-350 characters. Maximum is 500 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

Key Concepts

ContentType Binding

Self-Contained

Template Support

Compiled Output

The Content Object

Example Content

Content Structure

Single Section Example (Article)

Multi-Section Example (Quiz)

Key Principles

Description Best Practices

​Key Concepts

ContentType Binding

Self-Contained

Template Support

Compiled Output

​The Content Object

​Example Content

​Content Structure

​Single Section Example (Article)

​Multi-Section Example (Quiz)

​Key Principles

​Description Best Practices

Key Concepts

The Content Object

Example Content

Content Structure

Single Section Example (Article)

Multi-Section Example (Quiz)

Key Principles

Description Best Practices