AFFiNE
A nightly canary train where the AI platform work hides between dependency bumps
Comparison · Collab
Document360 vs pagedown
A side-by-side editorial comparison of Document360 and pagedown — release velocity, themes, recent moves, and the top alternatives to consider.
Document360 vs pagedown: at a glance
| Feature | Document360 | pagedown |
|---|---|---|
| Sector | Collab | Collab |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | api, oauth, mcp, knowledge base | r-markdown, paged-media, pdf-output, browser-rendering |
| Last editorial update | 3d ago | 1h ago |
| Website | — | Visit → |
What is Document360?
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.
What is pagedown?
pagedown is down to one small fix a year, mostly absorbing changes from elsewhere.
The last six releases contain no new capability. 0.24 fixes missing horizontal rules under unnumbered h1 headers in the poster_jacobs format; 0.23 stops non-ASCII header text erroring during TOC processing; 0.22 drops a call to `xfun::attr()` before it disappears upstream; 0.21 sets an `is.paged.js` knit option so knitr knows paged.js loads its own JS and CSS; 0.20 raises the R floor; 0.19 patches a browser rendering regression with `overflow-x: clip`.
Document360 vs pagedown: editorial side-by-side
Document360
6.3COLLAB
Document360 rebuilds its public API and turns docs into an agent-readable surface.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
pagedown
0.0COLLAB
pagedown is down to one small fix a year, mostly absorbing changes from elsewhere.
◆ Current state
The last six releases contain no new capability. 0.24 fixes missing horizontal rules under unnumbered h1 headers in the poster_jacobs format; 0.23 stops non-ASCII header text erroring during TOC processing; 0.22 drops a call to `xfun::attr()` before it disappears upstream; 0.21 sets an `is.paged.js` knit option so knitr knows paged.js loads its own JS and CSS; 0.20 raises the R floor; 0.19 patches a browser rendering regression with `overflow-x: clip`.
◆ Where it's heading
pagedown sits between three things it does not control — paged.js, headless Chrome, and Pandoc — and its release history is a record of each of them moving. The one release in the window with anything resembling design intent is 0.21, which lets other packages detect a paged.js context rather than guess it. Cadence has thinned to roughly one release a year, and the last genuinely new features (long-table headers, Sass support, streamed PDF transfer) are outside this window.
◆ Prediction
Expect another single-fix release triggered by a paged.js, Chrome or Pandoc change. Nothing here suggests new output formats are coming.
Alternatives to Document360 and pagedown
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 pagedown.
tufte
After three quiet years, tufte 0.15 finally lets Tufte-style documents cross-reference.
xaringan
xaringan has settled into theme upkeep and Pandoc-era compatibility patches.
Double
Double is turning its accounting assistant into the way the work gets done
litedown
litedown grows from a lean renderer into a book and site generator
bookdown
bookdown's output is mature; its free hosting destination is being switched off.
See all Document360 alternatives → · See all pagedown alternatives →
Recent activity from Document360 and pagedown
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoDocument360API v3 rebuild adds OAuth 2.0 and scoped API keys ⚡
- 10d agoDocument360Interactive API reference with a rebuilt Try It! console
- 1mo agoDocument360Find and replace spans variables, snippets, and links
- 1mo agoDocument360Native Mermaid diagrams and automatic llms.txt generation
- 1mo agoDocument360MCP server gains publishing and workflow controls
- 2mo agoDocument360Multiple JWT configs and an MCP analytics dashboard
- 4mo agopagedownpagedown 0.24 fixes header rules in poster_jacobs
- 11mo agopagedownpagedown 0.23 fixes non-ASCII headers in TOC processing
- 1y agopagedownpagedown 0.22 drops deprecated xfun::attr()
- 1y agopagedownpagedown 0.21 signals paged.js context to knitr
- 3y agopagedownpagedown 0.20 requires R >= 3.5.0
- 3y agopagedownpagedown 0.19 fixes paged.js rendering in modern browsers
Frequently asked questions
What is the difference between Document360 and pagedown?
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.
Is Document360 better than pagedown?
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.
What are the best alternatives to Document360?
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.
What are the best alternatives to pagedown?
Top pagedown alternatives in Collab are ranked by recent ship velocity. Browse the "pagedown alternatives" section above for the current picks, or visit /alternatives/pagedown for the full list with editorial commentary on each.