b3doc
A small B-Cubed utility for turning R Markdown into publishable docs
A side-by-side editorial comparison of accessr and logger — release velocity, themes, recent moves, and the top alternatives to consider.
One R Markdown source, four accessible formats — and a fortnight spent patching around someone else's bug.
accessr turns a single R Markdown file into HTML slides, HTML, Word and PDF output, with an emphasis on producing documents a screen reader can navigate. Accessible PDFs come via OfficeToPDF and are Windows-only, which is the package's main structural constraint. Recent releases have been spent absorbing and then unwinding a fault in the officedown dependency.
R's logging package handed to new maintainers and rebuilt from the inside out
logger structures R logging around four composable pieces — a level threshold, a formatter, a layout and an appender — a design fixed at the 2018 CRAN release and unchanged since. The recent work is all underneath it. 0.4.0 made metadata computation lazy so expensive fields cost nothing unless a layout uses them, swapped the custom background-process appender for mirai, and added native GitHub Actions output. 0.4.1 followed with elapsed-time logging, call site location exposed to layouts, a cli-based formatter, and knitr chunk timing. 0.4.2 is a small maintenance release adding an ntfy appender.
accessr turns a single R Markdown file into HTML slides, HTML, Word and PDF output, with an emphasis on producing documents a screen reader can navigate. Accessible PDFs come via OfficeToPDF and are Windows-only, which is the package's main structural constraint. Recent releases have been spent absorbing and then unwinding a fault in the officedown dependency.
The package's own development is focused on the details that make output genuinely accessible rather than merely produced — PDF bookmarks generated from Word headings, image dimension handling, header behaviour in slide output. That work is intermittent, and the more visible pattern in 2025 is dependency fragility: a CRAN check failure traced to a strsplit() call inside officedown forced a temporary patch, which was reverted two weeks later once upstream fixed it. Depending on a chain of document-conversion tools means the package inherits their breakages.
The next release will likely be another response to an upstream document-tooling change, though the pdf_args work suggests further OfficeToPDF options could be exposed if accessibility gaps surface.
logger structures R logging around four composable pieces — a level threshold, a formatter, a layout and an appender — a design fixed at the 2018 CRAN release and unchanged since. The recent work is all underneath it. 0.4.0 made metadata computation lazy so expensive fields cost nothing unless a layout uses them, swapped the custom background-process appender for mirai, and added native GitHub Actions output. 0.4.1 followed with elapsed-time logging, call site location exposed to layouts, a cli-based formatter, and knitr chunk timing. 0.4.2 is a small maintenance release adding an ntfy appender.
Two things stand out. The original four-part architecture has absorbed six years of additions without being renegotiated — every new capability arrives as another formatter, layout or appender rather than a change to the contract. And the contributor pattern has shifted: 0.3.0 collected two years of scattered community patches, while 0.4.0 and 0.4.1 are concentrated work from a small number of prolific R-infrastructure maintainers, which reads as a handover of stewardship rather than a maintenance lull ending.
The pluggable design means new destinations and formatters are the path of least resistance, so expect further appenders in the mold of ntfy and Slack rather than changes to the core logging contract.
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 accessr or logger.
A small B-Cubed utility for turning R Markdown into publishable docs
An R interface to GeoPackage that keeps sanding down its own API
Four dormant years end with a test fix, not a feature
Four years of releases land in four minutes as the changelog gets backfilled to GitHub
A comorbidity-coding package relicenses to BSD and grows past the American coding systems
Dragonfly spends its releases on correctness in the parts of Redis compatibility nobody tests.
See all accessr alternatives → · See all logger alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. accessr and logger 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. accessr and logger 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 accessr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "accessr alternatives" section above for the current picks, or visit /alternatives/accessr for the full list with editorial commentary on each.
Top logger alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "logger alternatives" section above for the current picks, or visit /alternatives/logger for the full list with editorial commentary on each.