Content & Publishing

Content is everything a site publishes: your own structured collections, the blog, pages built from sections, and the header, footer and settings shared by every page. The same content serves the Kanorio-hosted site and any front end you build.

Core objects

• Collections and items. You define a collection's fields, such as text, rich text, numbers, dates, media and references to other collections, and its items hold the data. Collections can restrict fields to members or buyers.
• Posts. The blog is a set of built-in collections: posts, categories, tags and authors. Posts support review before publishing and scheduled publishing.
• Pages and sections. Each page is an ordered list of typed sections. The hosted site renders them; a headless front end reads the same data.
• Globals. The header, footer and site settings, such as call-to-action buttons and social links.
• Redirects and revisions. Renaming a page creates a redirect automatically, and earlier versions of content can be restored.
• Imports. Move posts from another platform, with images, categories and original dates kept.

How the APIs fit

• Write with the Management API. Writes to pages, globals and posts are drafts until a publish operation runs. Collection items publish immediately unless you ask for a draft.
• Read published content with the Content Delivery API. It is anonymous, edge-cached and safe for the browser, and every response resolves media in one assets map.
• Listen for collections.item.*, content.page.* and content.translation.* webhooks, whose cacheTags let you refresh exactly the pages that changed, in exactly the locales that changed.