DAM holds everything editorial. Its main screen is Content Studio (/app/content-studio), where you write single posts and multi-page documents — courses, applications, trainings. Around it sit the structures that organize content: categories, tags, navigation, comments, documents and templates.
What it covers
| Area | What it holds |
|---|---|
| Content Studio (posts) | Single posts (articles, news, blog entries, galleries) and multi-page documents — courses, applications, trainings — with pages, chapters, conditions, reviewers and learners. Played on your site by the Content Player |
| Documents | Stored and downloadable files. (Multi-page, chaptered documents are posts — build them in Content Studio.) |
| Navigation | Menus and link trees, built as structures rather than hard-coded |
| Tags | Flat labels, grouped into tag groups |
| Categories | A hierarchical tree |
| View templates | How a type of content is rendered |
| View components | Reusable rendering pieces |
Categories and tags
Categories form a tree; tags are flat. Both are referenced from the publishing block that every record carries, which is why a product, a post and an event can all be categorized and tagged the same way rather than each having its own taxonomy.
Navigation
Menus are records, so they can be edited without touching a template and reused across pages. A change to a menu applies everywhere it is rendered.
View templates
A view template defines how a type of content renders. Define it once and every record of that type presents consistently, rather than each page rebuilding the layout.
Publishing and approval
Content uses the same lifecycle as everything else — draft, review, approve, publish — with versioning and restore. Editorial approval is a permission, so reviewing and publishing can be separated from writing.
Publishing a post copies it into a published version, and the site only ever serves that copy: later edits show as unpublished changes until you publish again, and Unpublish takes the post off the site without deleting it. This is separate from a page's Reviewers in Content Studio, who mark what a learner sends in.
Translation
Content can be localized, with translations managed under Configuration.