A comment thread at the bottom of a long document is where feedback goes to lose its context. "This paragraph needs a source" forces the reader to hunt for which paragraph, on which page, in which version. The alternative is anchoring the discussion to the thing it discusses.
The idea: anchor conversations to content
Most writing tools treat comments as a single stream attached to the document as a whole. Anchored annotation works differently: a discussion thread attaches to a specific section, sentence, or element. The context travels with the comment.
This changes a few things in practice:
- Feedback becomes actionable. The reader sees exactly what the comment refers to, and the writer can resolve threads one by one without archaeology.
- Navigation and discussion reinforce each other. If your document has a real section structure, anchored tags double as a map: jump to a section, see its open threads.
- Documents become reference material. Attachments and related documents can live next to the work itself, at workspace or document level, instead of in a separate folder system people forget to check.
There are design costs. Anchors break when the anchored text is deleted or heavily rewritten, so the system has to decide: orphan the thread, re-anchor it, or mark it stale. Fine-grained anchoring also raises the permission question: if you can hide a document from specific people, do its threads inherit that? (They should.)
How we approached it at Andika
Andika is a knowledge workspace built around Markdown documents, and several recent additions came directly from user requests:
- A tagging system on top of documents. You can tag a specific section and start a focused discussion thread on it, rather than collecting all feedback in one stream.
- Document attachments at both workspace and document level, with the option to hide specific documents from specific people.
- Section navigation in the Markdown editor and preview, plus copy buttons on code blocks in the preview, so reference documents are easier to move through and reuse.
- Reader summaries on the same page, and the option to send a document to a large language model for summarization when you want a machine-generated first pass.
None of these is a headline feature on its own. Together they move a document from "a page of text" toward "a place where reading, discussing, and referencing happen in one spot."
Adapted from posts on the Andika blog.
