klytos-page-structure

Define and standardize page data structures for Klytos CMS.

12|2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/joseconti/klytos --skill klytos-page-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: klytos-page-structure
Source: https://github.com/joseconti/klytos/tree/main/.claude/skills/klytos-page-structure
Command: npx skills add https://github.com/joseconti/klytos --skill klytos-page-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and documents the page data model, templates, and hierarchical URL rules in Klytos CMS to ensure consistent page creation and editing workflows.

Core Features & Use Cases

  • Defines required fields (slug, title, content_html, template) and optional metadata (meta_description, lang, status) for pages.
  • Documents templates and hierarchical URLs, enabling predictable routing and rendering across the site.
  • Provides guidance for using PageManager API and Gutenberg blocks when creating and updating pages.

Quick Start

Create a new page by supplying a slug, title, and Gutenberg-compatible content in the PageManager API.

Frequently Asked Questions about klytos-page-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What fields are required to create a page in Klytos CMS?

Creating a Klytos page requires slug, title, content_html, template, and status fields. Optional metadata like language and meta_description can also be applied to ensure compatibility with PageManager and related hooks.

How do I structure hierarchical URLs for pages using the PageManager API?

Hierarchical URLs are structured by defining slug and template fields according to documented routing rules. This standardizes page data models to ensure predictable routing and rendering when queried through the PageManager API.

Can I use Gutenberg blocks to manage content_html in Klytos page templates?

Yes, Gutenberg blocks can be used to supply content_html for Klytos page templates. The page structure provides guidance for integrating Gutenberg-compatible content when creating or updating pages via the PageManager API.

Does Klytos page management support optional language and metadata fields?

Yes, Klytos page management supports optional language and metadata fields such as meta_description and lang. These fields supplement the required slug, title, content_html, template, and status to enrich page data.

Why standardize the page data model in a headless CMS workflow?

Standardizing the page data model ensures consistent page creation and editing workflows. Enforcing required fields like slug, title, and template guarantees predictable hierarchical routing and rendering across the site.

What is the best way to update an existing page without breaking hierarchical URLs?

To update an existing page without breaking hierarchical URLs, maintain the slug and template fields while modifying content_html. Following the standardized page data structure ensures routing remains intact during PageManager API updates.