Content Studio is where every post is written: a single article, a photo gallery, or a multi-page document such as a course, a staff training, a study guide with coursework, or a multi-step application. It lives in the admin at DAM › Content Studio (/app/content-studio). On your site, posts are played by the Content Player.
The dashboard
The first screen, Content Manager, lists every post.
| Control | What it does |
|---|---|
| New post | A single post — pick a type (Post, Blog Post, …) |
| Multi-page document | A post made of pages — pick a type. Use it for courses, applications, trainings, ebooks and documentation |
| All / Draft / Published / Archived | Tabs with counts |
| Search, Sort, Type, Category, Tag | Narrow the list |
| Published / Not published | The card's state, with Publish or Unpublish beside it |
| Preview · Clone · View JSON · Delete | Card actions |
Writing pages
A multi-page document opens with Contents on the left — its pages, in order — and + Page to add one. Each page has a title, a short summary and its content.
The content editor has four modes: Visual, HTML, Split and Preview. The + button inserts ready-made blocks:
| Group | Blocks |
|---|---|
| Layouts | Columns, sidebar layouts, hero, card grid, callout, quote, banner |
| Text | Heading, paragraph, bulleted list, quote, divider |
| Media | Video (a YouTube or Vimeo link, or an upload), Audio, PDF (with an I've read it button), Image / gallery |
| Questions & forms | Question (a written answer), Multiple choice (with the right answer, if there is one), Form from a collection |
| Other | Button / link, Start this page as… (Article, Video lesson, Video + quiz, Audio, PDF reading, Quiz, Feedback) |
A page's questions form one answer form, sent in together. For multiple choice, the right answers are kept on the page record, never in the page itself, so a reader cannot find them; the answers are marked 0–100 when sent in.
Blocks also say how a page is finished. A video or audio reports how much was watched and finishes the page at the end (unless the page also asks questions); a PDF finishes with I've read it; a page with questions finishes when they are sent in; anything else has Mark complete.
Access & review — per page
Open Access & review above a page's content.
- Reviewers — emails or groups. When someone sends this page in, it waits for one of them to mark it instead of finishing on its own. Leave it empty if no one needs to.
- Conditions — the page opens only when every condition holds. Each points at an earlier page or chapter:
| Condition | Holds when |
|---|---|
| is done | that page (or every page in that chapter) is finished |
| is approved | a reviewer approved it |
| score at least | its answers scored at least the number (0–100) |
| watched at least % | at least that much of its video or audio was watched |
| complete at least % | at least that much of the chapter is finished |
Until a page opens, readers see it locked, with the reason (Complete "Welcome" first).
Settings
The Settings tab holds the post itself.
- Title, slug, summary, cover image — the slug is the post's address on the site.
- Access — the same rules as a CRM form:
- Access mode: open (anyone), code (anyone holding the access code), or participants (only the people listed, each with their own code).
- Authentication: none, magic-link, code, password or email — how a person proves who they are before it opens.
- Start date / End date, an Invitation template, and Participants.
- Course — Due in days sets a due date for each person from the day they start. A post can also say how the Content Player lays it out: layout (sidebar for courses and trainings, steps for applications and forms) and navigation (sidebar, a numbered stepper at the top, or none).
- Outline & conditions — group pages into chapters (sections). Conditions on a chapter apply to every page in it. Pages not placed in the outline are listed so none is forgotten.
Learners
At the bottom of Settings, Learners follows the people taking the post.
- Enroll people by email. Someone without an account is matched when they sign in with that address.
- Waiting for review lists every page sent in to a reviewer, oldest first, with the person, the page and what they sent — each answer, and uploaded files by name. Approve it, or Request changes with a note; the person sees the note on that page and can send it in again.
- The roster shows each person's status, % complete, the next page and the due date.
Reviewers named on a page, and admins, can mark it.
Preview
Preview (on the card or in the editor) opens the post on your active site at /__preview/post/<slug or id> — every page open, nothing recorded, and each locked page says when a learner would get it. The link carries a key for that post that lasts an hour — no one's sign-in goes in it — so open Preview again for a fresh link. It works whether or not the Content Player is switched on. Build Studio's page preview works the same way at /__preview/page/<site>/<page>.
Publishing
Publishing copies the post into a published version, and your site only ever serves that version. Edits after publishing show as unpublished changes until you publish again, so work in progress never reaches readers. Unpublish takes the post off the site without deleting it. People's progress and answers are kept either way.