KIBO CMS is the content management layer of the KIBO Composable Commerce Platform, built around three pillars: the Website Builder, which is a visual drag-and-drop page editor; the Headless CMS, which handles structured content models; and the File Manager, a dedicated asset library. Before we dive in, it’s worth getting oriented — the CMS has its own dedicated navigation, separate from the rest of the KIBO Admin, and knowing how to navigate the menu will make subsequent videos easier to follow.In this video, we’ll demonstrate how to navigate the KIBO CMS interface and understand what each section does. KIBO CMS is the content management layer of the KIBO Composable Commerce Platform, built around three pillars: the Website Builder, which is a visual drag-and-drop page editor; the Headless CMS, which handles structured content models; and the File Manager, a dedicated asset library. Before we dive in, it’s worth getting oriented — the CMS has its own dedicated navigation, separate from the rest of the KIBO Admin, and knowing how to navigate the menu will make subsequent videos easier to follow. In this video, we’ll demonstrate how to navigate the KIBO CMS interface and understand what each section does. To navigate to KIBO CMS, in the KIBO Admin, on the “MAIN” tab, we’ll click “Content”, then click “Page Builder”. To navigate to KIBO CMS, in the KIBO Admin, on the “MAIN” tab, we’ll click “Content”, then click “Page Builder”. This is the Page Builder configuration menu. Down the left side is the primary navigation, organized into sections, such as “Content Modeling”, “Content”, “Website Builder”, “Dev Tools”, and “Settings”, among others. The center panel changes based on what’s selected in that navigation; currently it’s displaying the “Pages” menu, as that’s where the CMS opens by default. This is the Page Builder configuration menu. Down the left side is the primary navigation, organized into sections, such as “Content Modeling”, “Content”, “Website Builder”, “Dev Tools”, and “Settings”, among others. The center panel changes based on what’s selected in that navigation; currently it’s displaying the “Pages” menu, as that’s where the CMS opens by default. On the top right, we’ll see the Tenant info of the sandbox the Page Builder configuration menu is connected to. There is also a dropdown on the User profile to exit the tenant or logout entirely. On the top right, we’ll see the Tenant info of the sandbox the Page Builder configuration menu is connected to. There is also a dropdown on the User profile to exit the tenant or logout entirely. At the very top of the left navigation is “Home”. This brings us back to this default landing view any time we need to reorient. At the very top of the left navigation is “Home”. This brings us back to this default landing view any time we need to reorient. “File Manager” sits as its own item near the top of the navigation. This is the practitioner-facing asset browser, where uploaded images live, and can be organized into “folders” and “tags”. We’ll cover this in detail in a subsequent video.Important Note: a second “File Manager” appears further down, under “Settings”. That one is a separate admin configuration screen for upload size limits and the file delivery URL — not another way to browse assets. “File Manager” sits as its own item near the top of the navigation. This is the practitioner-facing asset browser, where uploaded images live, and can be organized into “folders” and “tags”. We’ll cover this in detail in a subsequent video. Important Note: a second “File Manager” appears further down, under “Settings”. That one is a separate admin configuration screen for upload size limits and the file delivery URL — not another way to browse assets. Below that, the “Content Modeling” section — “Models”, “Groups”, and “Workflows” — is where structured content types are defined, including their own approval workflows.The “Content” section below “Content Modeling” is where individual entries built from those models live. This is part of the Headless CMS side of KIBO CMS, which is a developer-oriented workflow. Below that, the “Content Modeling” section — “Models”, “Groups”, and “Workflows” — is where structured content types are defined, including their own approval workflows. The “Content” section below “Content Modeling” is where individual entries built from those models live. This is part of the Headless CMS side of KIBO CMS, which is a developer-oriented workflow. The “Website Builder” section is where users will spend most of their time. It includes “Pages”, “Redirects”, “Settings”, “Integrations”, “Workflows”, and “Configure Next.js”.Important Note: “Workflows” appears in both “Content Modeling” and “Website Builder” — each scopes its approval workflow to a different kind of content, “Headless CMS” entries versus “Pages”. “Pages” is what’s currently open; we’ll get hands-on with building and editing pages in a subsequent video. The “Website Builder” section is where users will spend most of their time. It includes “Pages”, “Redirects”, “Settings”, “Integrations”, “Workflows”, and “Configure Next.js”. Important Note: “Workflows” appears in both “Content Modeling” and “Website Builder” — each scopes its approval workflow to a different kind of content, “Headless CMS” entries versus “Pages”. “Pages” is what’s currently open; we’ll get hands-on with building and editing pages in a subsequent video. The center panel shows our page structure two ways: a folder tree on the left for organizing pages, and a table on the right listing every page with its “Author”, “Created” and “Modified” dates, “Status”, and whether it’s “Live”. Right now we can see folders for “Cart Page”, “Category Override Pages”, and “Product Override Pages”, along with several individual pages.The “Category Override Pages”, “Product Override Pages”, and “Cart Page” folders hold pages that override a templated product or category page — for example, a custom splash page for a category instead of its default listing. We’ll cover building these overrides in a subsequent video.At the bottom of the Pages menu, “Trash”, “Content Reviews”, and “Schedule” give us quick access to recently deleted items, pending reviews, and scheduled publishes without digging through the main sections. The center panel shows our page structure two ways: a folder tree on the left for organizing pages, and a table on the right listing every page with its “Author”, “Created” and “Modified” dates, “Status”, and whether it’s “Live”. Right now we can see folders for “Cart Page”, “Category Override Pages”, and “Product Override Pages”, along with several individual pages. The “Category Override Pages”, “Product Override Pages”, and “Cart Page” folders hold pages that override a templated product or category page — for example, a custom splash page for a category instead of its default listing. We’ll cover building these overrides in a subsequent video. At the bottom of the Pages menu, “Trash”, “Content Reviews”, and “Schedule” give us quick access to recently deleted items, pending reviews, and scheduled publishes without digging through the main sections. Important Note: a page’s “Status” and whether it’s “Live” are tracked separately, and they don’t always match. Every time a published page is edited again, the system automatically creates a new revision, keeping the prior published version intact — which is how a page can show a newer draft revision while an older revision stays live.For example, “Homepage” is “Published” at “version 9” and is “Live” at “version 9”, meaning the latest published revision is what shoppers see. “test-page”, by contrast, is a “Draft” at “version 2” but still shows “Live” at “version 1” — a newer draft in progress while an older published revision remains live. Other pages are “Drafts” with no live revision. Important Note: a page’s “Status” and whether it’s “Live” are tracked separately, and they don’t always match. Every time a published page is edited again, the system automatically creates a new revision, keeping the prior published version intact — which is how a page can show a newer draft revision while an older revision stays live. For example, “Homepage” is “Published” at “version 9” and is “Live” at “version 9”, meaning the latest published revision is what shoppers see. “test-page”, by contrast, is a “Draft” at “version 2” but still shows “Live” at “version 1” — a newer draft in progress while an older published revision remains live. Other pages are “Drafts” with no live revision. “Content Reviews” appears further down the navigation. This is where content moves through review before publishing. We’ll cover this in depth in a subsequent video. “Content Reviews” appears further down the navigation. This is where content moves through review before publishing. We’ll cover this in depth in a subsequent video. “Audit Logs” gives us a record of changes made across the CMS — useful for tracking who changed what, and when. “Audit Logs” gives us a record of changes made across the CMS — useful for tracking who changed what, and when. The “Dev Tools” section — “GraphQL Playground”, “SDK Playground”, “Webhooks”, and “Background Tasks” — is developer-facing tooling for working with the CMS programmatically. The “Dev Tools” section — “GraphQL Playground”, “SDK Playground”, “Webhooks”, and “Background Tasks” — is developer-facing tooling for working with the CMS programmatically. The “Settings” section covers two areas: “Access Management”, which includes “Roles”, “Teams”, and “API Keys”; and “System”, which includes the “File Manager” configuration, “AI Power-Ups”, and “Languages”.Important Note: “Roles” define permission bundles, while “Teams” group users so a role can be assigned to everyone on that team at once. “AI Power-Ups” is the CMS’s built-in AI content generation tool — we’ll use it in a subsequent video. We’ll also cover “Roles” and “Teams” in depth in a subsequent video. The “Settings” section covers two areas: “Access Management”, which includes “Roles”, “Teams”, and “API Keys”; and “System”, which includes the “File Manager” configuration, “AI Power-Ups”, and “Languages”. Important Note: “Roles” define permission bundles, while “Teams” group users so a role can be assigned to everyone on that team at once. “AI Power-Ups” is the CMS’s built-in AI content generation tool — we’ll use it in a subsequent video. We’ll also cover “Roles” and “Teams” in depth in a subsequent video.