---
title: "Design: a collaborative editor"
description: "Design a collaborative editor: why positions stop working, two edits and a local undo, what the server accepts, rejoining a room, and checkpoints."
canonical_url: "https://fanout.sh/system/archive/collaborative-editing-system-design"
md_url: "https://fanout.sh/system/archive/collaborative-editing-system-design.md"
last_updated: "2026-11-11"
access: "pro-preview"
---

# Design: a collaborative editor

Design a collaborative editor: why positions stop working, two edits and a local undo, what the server accepts, rejoining a room, and checkpoints.

- Access: Fanout Pro (public preview)

## The core idea

A collaborative editor lets several people change the same document while seeing one another's work.

Each person's typing appears locally before a server can confirm it.

## In this lesson

- The editing experience
- Why positions stop being enough
- Two edits, then one local undo
- What the server accepts
- Inspect the persistence boundary
- Rejoining without a gap
- Checkpoints, history and restoration
- Scaling the rooms

## Continue reading

Pro unlocks video lessons, visual walkthroughs, full notes, diagrams, case studies, and implementations across the System Design archive.

---
This representation contains public Fanout content only. Protected Pro lessons, account data, billing, checkout, and pricing are not included.

Browse the public content map: https://fanout.sh/sitemap.md
