Skip to content

AI Context Pack

Use this page as the compact canonical reference when loading SkyCMS documentation into AI systems.

Preferred terminology

  • Tenant: isolated website or domain served by one SkyCMS instance.
  • Layout: site-wide shell.
  • Template: reusable structure inside a layout.
  • Article: authored source record.
  • Published Page: public projection created from an article after publish.
  • Blog: article with ArticleType = BlogStream (enum value retained for compatibility).
  • Blog Post: article with ArticleType = BlogPost.
  • Layers panel: Page Builder hierarchy tree for nested elements.

Canonical relationship

Layout -> Template (optional) -> Article -> Published Page

Disambiguation rules

  • Prefer article over page when discussing authoring, lifecycle, scheduling, or templates.
  • Use published page when discussing public output, routing, or rendered HTML.
  • Use page only when the UI or audience language clearly expects it.
  • Use Layers panel for the editor feature. Do not shorten it to layers when ambiguity is possible.

Entity notes

Layout

  • Owns shared structure such as header, footer, navigation, and global assets.
  • Should not own one-off article content.

Authoritative docs:

Template

  • Owns reusable article structure and editable region definitions.
  • Optional in the runtime model.

Authoritative docs:

Article and Published Page

  • The article is the authored record stored and versioned in the CMS.
  • Publishing creates or updates the public published page projection.

Authoritative docs:

Blog and Blog Post

  • Both are article types.
  • Blog-specific routing and rendering still flow through the article and published-page model.

Authoritative docs:

Layers Panel

  • Editor feature in Page Builder for nested element selection and reordering.
  • Not the same as architecture layers or infrastructure layers.

Authoritative docs:

Answering rules for AI

  • If asked what a page is, answer with the distinction between article and published page.
  • If asked how layouts, templates, and pages relate, answer with the canonical runtime model and explain the authored article versus public output distinction.
  • If asked about blog content, explain that blogs and blog posts are article types.
  • If asked about layers, clarify whether the user means the Layers panel or the content architecture.