Content Studio 6 documentation - WIP

Content lives in projects. Each project has a repository with its own content tree, optional applications, and settings. Layers inherit content for reuse or adaptation for other markets or languages.

A content item is a single piece of content — an article, image, page, or site. Every item has an identity (path, display name, id), a type, a set of field values, and a small envelope of metadata (security, schedule, workflow state).

A content type is the schema that defines an item’s fields. Most are defined in application code; a handful ship with XP and have special behaviour:

A page adds a configurable component structure to a content item. A Page component forms the root of the structure, while a page template can provide a starting structure based on the item’s content type. Content Studio manages the components and their data; the front end determines how they are presented. Page building happens in the Page Editor.

Content is always edited in the draft branch. Publishing copies the active draft version into the master branch, from which it becomes available to public consumers of the API.

Workflow state is the signal between editors that a draft is ready to publish — In progress, Ready for publishing, Publish request, Published, Unpublished. See Workflow for the state machine and Publish for the flow.

Every save, publish, unpublish, rename, or permissions change creates a new version. Versions can be compared and reverted from the Version history widget — see Version history.

Content items reference each other — pages embed images, shortcuts target content, text fields link to other items. Dependencies are tracked in both directions (inbound: who uses this; outbound: what does this use). Publishing, archiving, and unpublishing all check dependencies — see Dependencies.

Each content item has its own security settings: a list of principals (users, groups, roles) and the permission flags they have on that item (Read, Create, Modify, Delete, Publish, Read/Write permissions). Permissions are inherited from parent content by default and can be overridden per-item. See Permissions.

Deleting content is destructive. Archiving is the non-destructive alternative — items are moved to a separate archive storage where they can be browsed, restored, or permanently deleted later. See Archive.

An application is an installable unit of XP code that can contribute content types, Page components, Parts, Layouts, translations, and UI widgets. Applications are attached to a site via its Applications field; some (like Juke and Content Studio+) contribute UI across all sites.

Extensions are typically small UI surfaces contributed by an application. The main host is the Context panel; applications can also contribute preview modes and menuitems.

Issues are lightweight work items used to coordinate between editors — either a task (e.g. "spellcheck this article") or a publish request (review-and-publish handoff for users without publish permission, or for an approval flow). See Issues.