Casdoor
casdoor ships several times a day, mostly tightening organization boundaries.
A side-by-side editorial comparison of pkgdown and Tailscale — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | pkgdown | Tailscale |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | documentation, llm-readable, quarto, dark-mode | networking, kubernetes, identity-federation, programmable-infra |
| Last editorial update | 1h ago | 1d ago |
| Website | Visit → | — |
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.
Tailscale is turning the tailnet into something you provision by API, not configure by hand.
Tailscale ships on three parallel tracks: the client (now on the v1.102.x line), the Kubernetes Operator, and control-plane features that land as standalone admin notes. July was consumed by security work — advisories TS-2026-004 through TS-2026-009 across Tailscale SSH, Serve and Funnel, backported into the 1.98.x line. August has turned back to capability: a Services CLI surface, constant-time node churn on large tailnets, and an operator release adding in-cluster PeerRelays.
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.
Tailscale ships on three parallel tracks: the client (now on the v1.102.x line), the Kubernetes Operator, and control-plane features that land as standalone admin notes. July was consumed by security work — advisories TS-2026-004 through TS-2026-009 across Tailscale SSH, Serve and Funnel, backported into the 1.98.x line. August has turned back to capability: a Services CLI surface, constant-time node churn on large tailnets, and an operator release adding in-cluster PeerRelays.
Two threads run through the recent releases. One is making large tailnets cheaper to operate — node additions and removals now process in constant time, certificate issuance runs in parallel, MTU is clamped on both interfaces, and the operator's reconciliation loops have been stabilized. The other is making Tailscale programmable rather than configured: an alpha API for creating and deleting tailnets, workload identity federation on the Tailnet custom resource, self-serve identity provider switching, and OAuth-based device provisioning. The Kubernetes operator is where those two threads meet.
The tailnet creation API is still alpha and workload identity federation has only just reached the operator's Tailnet resource; the pattern across these entries points to the API graduating and identity federation spreading to more of the operator surface. What the entries do not indicate is whether API-only tailnets are aimed at customer-per-tailnet isolation or internal test fleets.
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 Tailscale.
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 Tailscale alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Tailscale 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. Tailscale 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 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 Tailscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tailscale alternatives" section above for the current picks, or visit /alternatives/tailscale for the full list with editorial commentary on each.