Skip to content

Comments ​

Select some words, comment on them. The thread appears in the Comments tab and the words stay highlighted in the text.

Anchored to words, not to offsets ​

A comment records which block it is on and the words it quoted — never a character offset. The highlight is found again on every render.

That is what makes a comment survive ordinary editing. Add a paragraph above it, indent the block, reorder the page: the anchor still matches, because none of those changed the words.

And when the quoted words are rewritten, the comment comes loose — visibly. It stays in the thread list, attached to the block, and says it no longer matches. The alternative is an offset-anchored comment silently sliding onto a sentence nobody wrote it about, which is worse than an obviously detached one.

Comments are not content ​

They are not blocks, and they are not ops. They do not appear in the timeline, they are not in the export, and they have no fidelity tier.

That is a decision rather than an omission. A comment is a conversation about the writing; putting it in the log would put it in the record of what was written.

Who may comment ​

comment is a level of its own, between read and write. Somebody with it can leave a comment and propose a change — and cannot edit the page. See roles and permissions.

Known limits ​

  • A comment anchors to one block. A selection spanning two blocks cannot be commented on, because no single block can carry that anchor.
  • Replies are one level deep. There are threads, not trees.
  • Anchoring matches the first occurrence of the quoted words in the block. Two identical phrases in one block share a highlight.

Blocks and the op log are canonical. Markdown is a projection. Git is a target.