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 EGroupware and rmarkdown — release velocity, themes, recent moves, and the top alternatives to consider.
EGroupware's feed has become a security treadmill, with the 23.1 branch days from end of life.
Almost every release in this window is a security release, and most ship as a pair — one build for 26.x, an identical-scope backport for 23.1. Feature work exists but arrives as single lines inside those security notes: WebAuthN two-factor moving out of the former EPL add-on, OpenID bumped to current upstream libraries, invoice XML gaining reverse-charge exemption codes. The recurring theme in the fixes themselves is authentication — OAuth bearer tokens, OpenID regressions, an inverted email_verified check, passkeys broken by a missing proxy config.
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.
Almost every release in this window is a security release, and most ship as a pair — one build for 26.x, an identical-scope backport for 23.1. Feature work exists but arrives as single lines inside those security notes: WebAuthN two-factor moving out of the former EPL add-on, OpenID bumped to current upstream libraries, invoice XML gaining reverse-charge exemption codes. The recurring theme in the fixes themselves is authentication — OAuth bearer tokens, OpenID regressions, an inverted email_verified check, passkeys broken by a missing proxy config.
The project is consolidating everyone onto 26.x and has put a date on it: security coverage for 23.1 ends August 15, 2026, repeated as a warning in every 23.1 build since July. After that the twin-release pattern should stop and the cadence should halve. The authentication stack is the least settled part of the codebase right now — the July and August releases keep re-fixing OpenID and WebAuthN regressions introduced by their own predecessors.
Expect 23.1 builds to cease after August 15 and the feed to become single-track 26.x. On the evidence of the last six releases, expect at least one more OpenID or WebAuthN regression fix to follow the recent upstream library bump.
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 EGroupware 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
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
A nightly canary train where the AI platform work hides between dependency bumps
See all EGroupware 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. EGroupware is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. EGroupware is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 EGroupware alternatives in Collab are ranked by recent ship velocity. Browse the "EGroupware alternatives" section above for the current picks, or visit /alternatives/egroupware 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.