Team chose BookStack over Outline because of thin documentation → BookStack
“the documentation was indeed lacking. It seemed to me that they're more intent on pushing their paid plans”
Friction holds 17 sourced reports about Outline (getoutline.com) from 71 public source threads (as of 2026-10-15); only 1 of them says the author left. This page shows that report, what its users say pushes them away, and the problem profile of Nextcloud, Notion.
Get started free with your email Open Outline on Friction
Switching reports that name a destination. A count is the number of reports naming it, not a market share: Friction only holds what people say in public.
| Named alternative | Reports naming it | Newest report |
|---|---|---|
| BookStack | 2 | 2020 (over 5 years old) |
| Slite | 1 | 2023 |
| Outline | 1 | 2020 (over 5 years old) |
| Microsoft Teams | 1 | 2018 (over 5 years old) |
Team chose BookStack over Outline because of thin documentation → BookStack
“the documentation was indeed lacking. It seemed to me that they're more intent on pushing their paid plans”
The most-reported open problems, worst severity first. Each links to the item with its source.
Recently viewed omits directly shared documents and uncategorized drafts · Reporting & analytics · Blocks work
“does not return some documents that the user can read and has viewed”
Malformed editor content makes documents and revision APIs unusable · Reliability & bugs · Blocks work
“A document becomes unopenable after invalid editor content is saved”
MCP initialization notification is rejected, preventing sessions · Integrations · Blocks work
“Outline sends a 400 response”
Markdown ZIP import creates broken attachment records · Data export & migration · Blocks work
“a subset of the created `Attachment` records end up broken”
macOS app activation errors after the original window closes · Reliability & bugs · Blocks work
“every subsequent activation of the app (Dock icon click, Spotlight, Raycast, `open -a Outline`) shows Electron's uncaught-exception dialog”
Switching trades one set of problems for another. The same evidence, for each tool Friction covers in this category:
38 reports · 92 source threads · most-discussed area: Reliability & bugs
14 reports · 25 source threads · most-discussed area: UI & usability
Counts and reports reflect people who post in public (developers and technical buyers are over-represented). A tool with fewer reports is not a better tool; it may only be discussed less. How the data is built.