2.2.1 Content Types — Schema and Structure

The CMS Builder in Praisma Hub allows administrators and authorized users to define content types that model the structure of information managed within a tenant. Content types form the foundation of the CMS and determine how content is created, stored, validated, localized, and presented.

This section describes how content types are defined, how their schema is structured, and how they are used consistently across the platform.

Purpose of Content Types

Content types exist to:

Model real-world information structures (pages, articles, news items, events, etc.)

Enforce consistency across content creation

Enable validation, workflows, and localization

Provide a stable schema for rendering, analytics, and APIs

Rather than allowing free-form content, Praisma Hub uses explicit schemas to ensure predictability, quality, and long-term maintainability.

Content Type Schema

Each content type in Praisma Hub is defined by a structured schema consisting of:

A unique identifier and human-readable name

A stable machine-readable slug

A collection of fields with explicit data types

Metadata describing behavior (publishing, versioning, localization)

Configuration for workflows and visibility

The schema is stored centrally and versioned, ensuring that changes to content structure can be managed in a controlled manner.

Structural Consistency

Once a content type is defined:

All entries of that type follow the same schema

Fields appear in a predictable order within the editor

Validation rules are applied uniformly

APIs and rendering layers can rely on a stable structure

This consistency is critical for accessibility, analytics, integrations, and long-term content reuse.

Relationships and References

Content types may define relationships to:

Other content types

Media assets

Taxonomies or classification structures

These relationships are explicitly modeled rather than inferred, allowing the CMS to enforce integrity and provide clear editorial guidance.

Governance and Change Management

Changes to content types:

Require appropriate permissions

Are tracked and auditable

Can be applied incrementally to avoid breaking existing content

This governance model ensures that schema evolution does not compromise data integrity or editorial workflows.

Summary

Content types define the structural backbone of the Praisma Hub CMS. By using explicit, versioned schemas, the platform ensures consistent content creation, reliable rendering, and safe long-term evolution.