Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kibocommerce.com/llms.txt

Use this file to discover all available pages before exploring further.

Kibo CMS is the content management layer of the Kibo Composable Commerce Platform. It provides a unified environment for creating and publishing structured content, building storefront pages, managing digital assets, and controlling user access — all within the same platform used to manage your catalog, orders, and fulfillment operations. Content teams work in a visual interface with drag-and-drop page building, rich content modeling, and built-in publishing workflows. Developers access content programmatically through a GraphQL API. Both work within the same tenant-isolated, role-controlled environment that governs the rest of the Kibo platform.

​
Key Capabilities

Content Modeling

Define structured content types with custom fields, validations, and relationships. Content models describe the shape of your data — from editorial articles to product spotlights to promotional banners — and expose each model through a generated GraphQL API. Supported field types include text, rich text, numbers, booleans, date/time, file references, and references to other content entries.

Website Builder

A drag-and-drop visual editor for building and publishing storefront pages without writing code. Content editors compose pages from layout grids and reusable page elements, preview changes before publishing, and manage revisions across Draft, Published, and Unpublished states. Each publish event creates a new revision, preserving the previously published version until the new one is explicitly promoted.

File Manager

Upload, search, organize, and tag digital assets including images and documents. The File Manager supports image width resizing via URL parameter and tagging for structured asset organization. Assets managed here are available for reference throughout the Website Builder and Headless CMS.

Access Management

Access to Kibo CMS is managed through Kibo account roles. Users log in with their existing Kibo credentials, and their Kibo role determines their CMS access level — Full Access, Editor, or Viewer. No separate user provisioning is required within Kibo CMS.

Multi-Tenant Isolation

Each company or brand on the Kibo platform operates within its own isolated CMS tenant. Tenant provisioning is managed through the platform, and each tenant maintains its own content models, pages, assets, users, and locale settings. This allows multiple brands or business units to operate independently on shared infrastructure.

Internationalization

Multi-language support is an upcoming capability. Locales will be configurable at the tenant level, and content entries will support locale-specific field values to enable teams to maintain separate content for each market.

Version Control and Publishing

Content entries and pages maintain a full revision history. Revisions are created on each publish event, making it safe to iterate on content while a stable published version remains live. Unpublishing reverts a page or entry to a non-public state without deleting it.

GraphQL API

Every content model automatically generates a GraphQL API for headless content delivery. Storefronts and integrations query content entries directly via the Read API, the Manage API, or the Preview API, each scoped to the appropriate access level.

​
Kibo Commerce Integration

Kibo CMS is designed to work alongside the rest of the Kibo Composable Commerce Platform. The integration connects CMS page-building workflows directly to live commerce data, and shares identity management with the broader platform.

​
Product and Category Pages

The Kibo CMS Website Builder includes a Kibo Commerce integration that connects page creation to the live product catalog and category tree. When building storefront pages, editors can search for and associate pages with specific products or product categories from the Kibo Commerce catalog. Two page types are available in the Website Builder’s ecommerce integration:
  • Kibo Product Page — Associates a page with a specific product, referenced by product code. The page preview renders at /product/{productCode}.
  • Kibo Category Page — Associates a page with a product category, referenced by category code. The page preview renders at /category/{categoryCode}.
This allows content teams to build product detail page templates and category browsing pages that are linked to real catalog data, and to preview how those pages will render against specific products or categories before publishing.

​
GraphQL API for Headless Content Delivery

All content modeled and published in Kibo CMS is accessible to storefronts and downstream systems through a GraphQL API. The API is automatically generated from your content models and supports three access modes:
  • Read API — For fetching published content entries. Used by storefronts to render live content.
  • Manage API — For reading and writing content entries programmatically. Requires elevated permissions.
  • Preview API — For accessing unpublished draft content, enabling preview environments to render content before it goes live.

​
Who Uses Kibo CMS

Kibo CMS serves several distinct audiences within a commerce organization: Content Editors create and maintain content entries and build storefront pages using the Website Builder. They work within the permissions defined by their assigned role, typically scoped to specific content model groups or page categories. Merchandisers use the Website Builder to build and publish category pages and promotional landing pages. The Kibo Commerce integration lets them associate pages directly with products and categories from the live catalog, making it possible to manage both the commerce data and the editorial experience from a single platform. Tenant Administrators configure tenant-level settings within Kibo CMS. User access is managed through the Kibo platform — users log in with their existing Kibo credentials, and their CMS access level is determined by their Kibo role. Developers define content models, build storefront integrations, and configure the GraphQL API. Developers typically create the initial content model structure that content editors then populate. They also implement the storefront rendering layer that queries the CMS Read API at build time or runtime to deliver content to end users.

​
Getting Started

Glossary

Key terms: content models, content entries, fields, and field types

Website Builder Glossary

Website Builder concepts: grid elements, page elements, revisions, and statuses

Create a Content Model

Define a content type with custom fields and validations

Create a Content Entry

Add a record to an existing content model

Upload a File

Add images and documents to the File Manager

Organize Files

Folder structure and tagging for asset management

Access Management

Understand how Kibo account roles control CMS access