Casdoor
casdoor ships several times a day, mostly tightening organization boundaries.
A side-by-side editorial comparison of pkgdown and Trunk — release velocity, themes, recent moves, and the top alternatives to consider.
pkgdown now generates llms.txt and a markdown copy of every documentation page
pkgdown builds the documentation sites for most R packages. The 2.1 line was about format and appearance - Quarto vignettes, a light and dark switch, self-hosted assets instead of CDN fetches. The 2.2 line changed audience: build_llm_docs() emits an llms.txt at the site root and a markdown version of every page, on by default.
Trunk is methodically maturing Merge Queue and Flaky Tests into enterprise-grade CI infrastructure.
Trunk's recent work is almost entirely incremental hardening of its two core products: Merge Queue and Flaky Tests. The cadence shows a clear enterprise-readiness pattern — a Terraform provider, public API endpoints, Prometheus-compatible metrics, multiple queues per repo, and deeper Slack and Jira integration. Nothing here redefines the product; it's the steady filling-in of operational and integration gaps larger teams require.
pkgdown builds the documentation sites for most R packages. The 2.1 line was about format and appearance - Quarto vignettes, a light and dark switch, self-hosted assets instead of CDN fetches. The 2.2 line changed audience: build_llm_docs() emits an llms.txt at the site root and a markdown version of every page, on by default.
Two audiences are now being served from one build. Human-facing work continues in small increments - dark-mode plot filtering, new translations, a local http server so search works in preview - while the new machine-facing output is opt-out rather than opt-in. The default matters more than the feature: thousands of package sites will start emitting llms.txt without their maintainers choosing to.
Expect the markdown output to gain the same configuration surface the HTML has, and the llms.txt contents to get more selective as maintainers discover what ends up in it; a way to exclude individual pages is the obvious next request.
Trunk's recent work is almost entirely incremental hardening of its two core products: Merge Queue and Flaky Tests. The cadence shows a clear enterprise-readiness pattern — a Terraform provider, public API endpoints, Prometheus-compatible metrics, multiple queues per repo, and deeper Slack and Jira integration. Nothing here redefines the product; it's the steady filling-in of operational and integration gaps larger teams require.
Trunk is making Merge Queue programmable and observable: APIs, IaC, metrics endpoints, and richer dashboards point at customers who manage CI at scale and want it wired into their existing tooling. Flaky Tests is gaining automation hooks (Jira issue creation, configurable threshold monitors) that move it from detection toward workflow.
Expect continued API, metrics, and integration depth on Merge Queue, and more automated remediation paths for Flaky Tests, as Trunk leans into programmability for larger engineering orgs.
Other Infra & APIs 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 pkgdown or Trunk.
casdoor ships several times a day, mostly tightening organization boundaries.
downlit's HTML contract was set in 0.4.0; every release since tracks R itself.
dittodb has spent four years on CRAN link fixes and one DBI bump.
connectapi is becoming the scripted administration surface for Posit Connect.
chromote turned the browser itself into a pinned, downloadable dependency.
lifecycle gave the tidyverse the word superseded, then spent years tuning who gets warned
See all pkgdown alternatives → · See all Trunk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. pkgdown and Trunk are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. pkgdown and Trunk are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top pkgdown alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "pkgdown alternatives" section above for the current picks, or visit /alternatives/pkgdown for the full list with editorial commentary on each.
Top Trunk alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Trunk alternatives" section above for the current picks, or visit /alternatives/trunk for the full list with editorial commentary on each.