What is your developer-dependent CMS actually costing you? Calculate your costs and get a full report
Live Commenting & Collaboration in Web Studio
Agility lets editors discuss content exactly where the work happens. From the content/page editing panel, teammates can leave comments to explain a change or ask a question; in Web Studio, Commenting Mode goes further by letting editors drop comment bubbles directly onto elements in the live visual preview. Comments support threaded replies, emoji reactions, @-mentions with notifications, in-place editing, and resolution, so feedback stays attached to the relevant content and is captured alongside its version history rather than scattered across email or chat.
Where comments live
- In the editing panel. Open an item or page in Edit mode; the comments section sits in the right-hand panel, directly below version history (the chat/speech-bubble icon). Editors leave comments here to document changes or ask questions about a specific item.
- In Web Studio (Commenting Mode). Navigate to Web Studio and click the comment bubble in the centre of the top toolbar to enter Commenting Mode. You can then leave interactive comment bubbles on specific elements in the visual preview, see others' bubbles, and click a bubble to jump to the item it references.
What you can do with a comment
- Thread it — reply to keep a discussion together.
- React — acknowledge with an emoji instead of a full reply.
- Mention — tag a teammate; they're notified, and clicking the notification deep-links them to that item and comment.
- Edit — update your own comment after posting.
- Resolve — mark a comment resolved once it's handled.
In-context annotations
Comment bubbles placed in the Web Studio preview act as visual annotations anchored to the on-page element they refer to. This makes feedback unambiguous — a reviewer can point at the actual hero, card, or paragraph in context rather than describing it in words. In Web Studio a bubble opens a full thread panel, where replies, reactions, and @-mentions appear in context with the page.
Filtering and resolution
Comments can be filtered by status — a Show Only Resolved toggle (plus filter controls) lets reviewers focus on open or resolved items. Each comment can be marked resolved or unresolved from its menu, and resolved comments remain accessible via the filter rather than being deleted, so the discussion history is retained.
How it fits editorial workflows
Commenting complements Agility's content workflow and version history:
- Comments are attached to the content item/page, so context travels with the content through staging, approval, and publishing.
- Combined with version history, a team can see what changed, who changed it, when, and read the discussion around the change in one place.
- Combined with presence and live collaboration (see Real-Time Co-Authoring & Conflict Handling), reviewers and authors can work and discuss in real time.
Commenting is separate from the approval workflow. Comments are a collaboration and feedback layer; they are not a formal sign-off gate. Content still moves through Agility's workflow states (staging → approval → publish) independently of whether comments are resolved, so teams can use comments for discussion without blocking or bypassing the approval process.
Shared responsibilities
| Area | Agility | Implementation partner / customer |
|---|---|---|
| Comments, threads, reactions, mentions, resolve | ✅ Built into Content Manager / Web Studio | — |
| In-context comment bubbles in preview | ✅ Web Studio Commenting Mode | ✅ Ensures Web Studio preview is configured for the site |
| Notifications | ✅ In-app (and notification deep-links) | ✅ Manages user accounts so mentions reach the right people |
| Editorial conventions | — | ✅ Defines how the team uses comments (e.g. resolve-before-publish, who reviews what) |