Leave Inline Comments on a Draft Without Leaving the Editor
A short walkthrough of the content editor's inline commenting — threads anchored to the exact passage they're about, visible to everyone editing the draft.
Review feedback on a draft is more useful when it's attached to the sentence it's about, not sitting in a separate document or a Slack thread that's already scrolled past the relevant paragraph. The content editor's commenting feature is built for exactly that: select a passage, leave a comment, and it stays anchored to that quote for as long as the thread is open.
How to leave a comment
Highlight the text you want to comment on, open the comment panel, and write your note. That creates a thread — a quoted passage plus one comment — which shows up alongside the draft, not in a separate tab. Anyone else with access to the draft can reply into the same thread, so a comment thread reads as a conversation about one specific piece of text rather than a flat list of unrelated notes.
What happens when someone deletes a comment
Deleting doesn't erase it outright — the comment is replaced with a visible "[Deleted Comment]" marker rather than disappearing from the thread. That matters when a thread has a reply chain: removing the middle of a conversation without a trace would make the remaining comments confusing. The marker keeps the shape of the discussion intact even after content is pulled.
Why it stays in sync
Comments are synced the same way the rest of the draft is — through the real-time collaboration layer under the editor (Yjs), not a separate save/reload cycle. If two people have the draft open, a comment added by one shows up for the other without a refresh, the same way a text edit would. It's part of the document, not a bolt-on review tool with its own state to keep in sync.
When to use it
Inline comments are the right tool for "this claim needs a source" or "can we soften this line" — feedback about a specific passage. If you're deciding whether a whole draft is ready to publish, that's a different, higher-stakes decision with its own approval step (see the companion piece on requiring sign-off before anything reaches your CMS). Comments are for getting a draft to that point, not for the publish decision itself.