Read the Docs
Read the Docs is rebuilding its build farm around uv and isolated builders, one week at a time.
A side-by-side editorial comparison of Document360 and rmarkdown — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Document360 | rmarkdown |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | api, oauth, mcp, knowledge base | r-markdown, pandoc, compatibility, publishing |
| Last editorial update | 1d ago | 1h ago |
| Website | — | Visit → |
Document360 rebuilds its public API and turns docs into an agent-readable surface.
Document360 ships a dated release every two to four weeks and the last six months have been dominated by two threads: making the knowledge base machine-consumable, and hardening enterprise access control. The AI thread runs from the March MCP server through publishing and workflow tools in June and per-reader-group AI restrictions this month; the access thread runs SCIM provisioning, multiple JWT configurations, and reader permission inheritance. This release adds a ground-up API v3 with OAuth 2.0 and scoped keys.
rmarkdown's job now is absorbing Pandoc's deprecations before users see them.
rmarkdown is at 2.31. Its releases read as a compatibility layer: switching to --syntax-highlighting for Pandoc 3.8 because --highlight-style is deprecated, dropping a syntax-highlighting workaround made unnecessary by Pandoc 2.18 three years ago, restoring table row classes that a Pandoc change removed, and falling back to html_document when a YAML output format is unrecognised.
Document360 ships a dated release every two to four weeks and the last six months have been dominated by two threads: making the knowledge base machine-consumable, and hardening enterprise access control. The AI thread runs from the March MCP server through publishing and workflow tools in June and per-reader-group AI restrictions this month; the access thread runs SCIM provisioning, multiple JWT configurations, and reader permission inheritance. This release adds a ground-up API v3 with OAuth 2.0 and scoped keys.
The product is being rebuilt around programmatic access rather than portal usage. MCP made the knowledge base writable by an assistant, llms.txt made it discoverable to crawlers, copy-as-Markdown and open-in-ChatGPT made articles portable, and API v3 now gives all of that a permission-aware substrate the old v1/v2 endpoints could not support. The same permission model is showing up on the reader side too — Eddy AI features are now gated per reader group — so authorization is becoming the shared spine across API, AI, and reader access.
Expect the advanced API v3 endpoints to keep expanding as a paid add-on and the MCP server to be re-plumbed onto v3's scoped-key model, since MCP currently sits outside the new authorization scheme. A v1/v2 deprecation notice is the other likely follow-up.
rmarkdown is at 2.31. Its releases read as a compatibility layer: switching to --syntax-highlighting for Pandoc 3.8 because --highlight-style is deprecated, dropping a syntax-highlighting workaround made unnecessary by Pandoc 2.18 three years ago, restoring table row classes that a Pandoc change removed, and falling back to html_document when a YAML output format is unrecognised.
The package is stable and mostly defensive. Each release absorbs a change in Pandoc or knitr so documents keep rendering, with the occasional user-facing escape hatch — the rmarkdown.files.suffix option exists because the default _files directory made cloud sync tools delete HTML output. Little here extends what an R Markdown document can do; it keeps existing ones working.
Given that the last two releases both handled Pandoc 3.8 flag deprecations, the next is likely to track further Pandoc changes rather than add an output format.
Other Collab products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Document360 or rmarkdown.
Read the Docs is rebuilding its build farm around uv and isolated builders, one week at a time.
SiYuan's 3.8 line is eight builds deep and still stabilizing the same four features
EGroupware's feed has become a security treadmill, with the 23.1 branch days from end of life.
Teable is spending this release cycle making computed fields and admin recovery trustworthy
Copilot's model roster churns weekly while GitHub quietly rewires policy and billing plumbing
Governance and cross-workspace plumbing, not new AI surface
See all Document360 alternatives → · See all rmarkdown alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Document360 is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Document360 is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Collab products to evaluate alongside.
Top Document360 alternatives in Collab are ranked by recent ship velocity. Browse the "Document360 alternatives" section above for the current picks, or visit /alternatives/document360 for the full list with editorial commentary on each.
Top rmarkdown alternatives in Collab are ranked by recent ship velocity. Browse the "rmarkdown alternatives" section above for the current picks, or visit /alternatives/rmarkdown for the full list with editorial commentary on each.