Inside a Scroll: Versions, Comments, and Sharing

How edits, conversation, and visibility work on a single document.

House handbook v12

"Pets allowed in the courtyard but not the kitchen — agreed at Council 23 Feb..."

history 12 versions
chat 4 comments

A Scroll isn't just a doc — it's a doc plus a record of how it changed and a thread to discuss it.

Versions

Every save creates a version. The history panel (clock icon, top-right) shows who edited, when, and a one-line summary if they wrote one. You can roll back to any version with two clicks. Nothing is overwritten. Old versions stay readable.

If your community votes a change to the bylaws, do this:

  1. Edit the Scroll with the new agreed wording.
  2. Add a brief edit summary ("Updated quiet hours per Council 30 Apr 2026").
  3. Save.

Six months later when someone asks "wait, when did we change quiet hours?", the answer is one click in the history panel.

Comments

Threaded at the bottom of every Scroll. Tag with @name to notify. Useful for:

  • Suggesting a change without editing
  • Linking the Scroll to a specific decision ("agreed in Council 30 Apr")
  • Asking "who knows about X in here?"

Don't use comments for chat. They're permanent. Future readers will see them, and irrelevant noise erodes the Scroll's authority.

Sharing publicly

Lock icon > Public > toggle on. The Scroll gets a stable URL, indexable by Google, embeddable on your community's website. Useful for:

  • "About us" or mission statements
  • Workshop signup pages
  • A public version of your bylaws or community agreements

Public Scrolls show only the published content — no comments, no version history, no member names except author attribution.

Linking from a Gathering

You can attach a Scroll to a Gathering — typically the meeting notes. The Gathering page links to the Scroll; the Scroll's metadata names the Gathering. This makes "what did we decide last Tuesday?" trivially answerable.

Editing etiquette

Real-time co-editing isn't on yet (it's on the roadmap). For now, the convention is: if you're going to be in a Scroll for more than five minutes, drop a quick comment first ("editing the lease section now") so a co-author doesn't trample your work. The version history will save you if it happens, but a heads-up is kinder.