← Back to home
Comparison · Collab

EGroupware vs pagedown

A side-by-side editorial comparison of EGroupware and pagedown — release velocity, themes, recent moves, and the top alternatives to consider.

EGroupware vs pagedown: at a glance

FeatureEGroupwarepagedown
SectorCollabCollab
Velocity score5.00.0
Sparks · 30d00
Top themessecurity, self-hosting, groupware, end-of-lifer-markdown, paged-media, pdf-output, browser-rendering
Last editorial update1d ago1h ago
WebsiteVisit →Visit →

What is EGroupware?

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.

Read the full EGroupware trajectory →

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`.

Read the full pagedown trajectory →

EGroupware vs pagedown: editorial side-by-side

E5.0

EGroupware's feed has become a security treadmill, with the 23.1 branch days from end of life.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

P
pagedown
COLLAB
0.0

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 EGroupware 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 EGroupware or pagedown.

See all EGroupware alternatives → · See all pagedown alternatives →

Recent activity from EGroupware and pagedown

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoEGroupwareSecurity release fixes passkey regression and OAuth token errors
  2. 9d agoEGroupware23.1 security release; branch support ends August 15
  3. 9d agoEGroupwareWebAuthN two-factor moves into core, plus security fixes
  4. 20d agoEGroupwareSecurity release repairs merge-print and ImportExport regressions
  5. 20d agoEGroupware23.1 security backport with end-of-support warning
  6. 1mo agoEGroupwareTwo more security fixes for the 23.1 branch
  7. 4mo agopagedownpagedown 0.24 fixes header rules in poster_jacobs
  8. 11mo agopagedownpagedown 0.23 fixes non-ASCII headers in TOC processing
  9. 1y agopagedownpagedown 0.22 drops deprecated xfun::attr()
  10. 1y agopagedownpagedown 0.21 signals paged.js context to knitr
  11. 3y agopagedownpagedown 0.20 requires R >= 3.5.0
  12. 3y agopagedownpagedown 0.19 fixes paged.js rendering in modern browsers

Frequently asked questions

What is the difference between EGroupware and pagedown?

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.

Is EGroupware better than pagedown?

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.

What are the best alternatives to EGroupware?

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.

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.