# Document View — Web app

A rich content view for reading, editing, and collaborating on structured documents.

Source: https://www.checklist.design/web-app/document-view

## Items

### Document title and metadata
The document's name, owner, and last-modified details visible at the top.

_Tip: An editable inline title is the expected pattern — requiring a separate settings screen to rename a document is a common frustration._

### Table of contents
A navigable outline generated from the document's headings.

_Tip: A table of contents that requires scrolling back to the top to access defeats its own purpose — sticky or floating placement is what makes it useful._

### Rich text with inline media
Support for formatted text, images, embeds, and other content types within the body.

_Tip: Most users bring content from Word or Google Docs — how gracefully paste handles those imports determines how much cleanup work they face._

### View and edit mode distinction
A clear difference between reading a document and actively editing it.

_Tip: Accidental edits are a major frustration in collaborative documents — a clear mode switch prevents content being changed unintentionally._

### Version history or change tracking
A log of previous versions and the ability to restore or compare them.

_Tip: Even basic 'last 10 versions' history is enormously valuable — it is one of the most-cited reasons users trust a platform with important documents._

### Auto-save and last-saved indicator
Changes save automatically, with a visible timestamp of when the last save occurred.

_Tip: 'Saving...' → 'Saved 3 seconds ago' is the gold standard — it reassures users without interrupting them._

### Inline comments or annotations
The ability to add comments to specific sections or selections of text.

_Tip: Flat unthreaded comments pile up quickly in a collaborative document — threading keeps conversations self-contained and the document readable._

### Share and permission controls
A way to share the document and control whether recipients can view or edit.

_Tip: A document shared with an entire organisation looks identical to a private one without a persistent sharing state indicator — that ambiguity causes accidental data exposure._

## License for the Checklist Design collection

Checklist Design collection: https://github.com/Checklist-Design/skills
Snapshot: bfae71e507b1b7c03c12e0756402b60eb80f5d14 · Imported: 2026-11-12
Republished under the MIT License. Original checklist text belongs to Checklist Design.

MIT License

Copyright (c) 2026 Checklist Design

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.