← Back to home
Comparison · Analytics

forestly vs markdown

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

forestly vs markdown: at a glance

Featureforestlymarkdown
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-safety, adverse-events, data-visualization, r-languagemarkdown-rendering, maintenance-mode, succession, r-package
Last editorial update1h ago3h ago
WebsiteVisit →Visit →

What is forestly?

forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.

forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.

Read the full forestly trajectory →

What is markdown?

A package that finished, declared itself done, and handed its core function to a successor.

The R markdown package spent 2023 adding real capability — fenced code block attributes, HTML widget rendering, compatibility shims for rmarkdown's document functions. Then 1.13 declared the package feature-complete and maintenance-only, naming litedown as where development continues. Version 2.0 completes that handover: mark(), the package's core function, is now a thin wrapper around litedown::mark(), and users are told to call litedown directly.

Read the full markdown trajectory →

forestly vs markdown: editorial side-by-side

F
forestly
ANALYTICS
0.0

forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.

◆ Current state

forestly renders adverse-event forest plots as interactive reactable widgets — filterable by AE category, with sliders for incidence thresholds and a toggle for the risk-difference column. Version 0.1.3 added `rtf_static_forestly()` for static RTF output, and 0.1.4 has been about giving the display owner control over what reviewers see: the CSV download button, the AE filter label, and the diff toggle can each be switched off.

◆ Where it's heading

The arc runs from a fixed interactive widget toward a configurable one with two output modes. Nearly every new argument in the last two releases exists to remove something from the display or relabel it, which suggests the users driving development are producing outputs for others to review under conventions they do not control. The x-axis range, column header, figure header and slider range arguments point the same way — this is a tool being fitted into standardised reporting rather than used ad hoc.

◆ Prediction

Given that the last two releases have consisted almost entirely of display-control arguments, the next is likely more of the same, applied to whichever parts of the interactive layout are still fixed.

M
markdown
ANALYTICS
0.0

A package that finished, declared itself done, and handed its core function to a successor.

◆ Current state

The R markdown package spent 2023 adding real capability — fenced code block attributes, HTML widget rendering, compatibility shims for rmarkdown's document functions. Then 1.13 declared the package feature-complete and maintenance-only, naming litedown as where development continues. Version 2.0 completes that handover: mark(), the package's core function, is now a thin wrapper around litedown::mark(), and users are told to call litedown directly.

◆ Where it's heading

This is a controlled retirement rather than abandonment. The maintainer closed out the outstanding feature work first, announced the succession explicitly, and only then reduced the package to a compatibility surface. What remains is a stable shim for the installed base while new work happens in a package with a different name and scope.

◆ Prediction

Expect only CRAN-driven fixes here from now on, with any genuinely new rendering capability appearing in litedown instead. The entries state this policy directly, so the main open question is how long the wrapper is kept before deprecation warnings appear.

Alternatives to forestly and markdown

Other Analytics 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 forestly or markdown.

See all forestly alternatives → · See all markdown alternatives →

Recent activity from forestly and markdown

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

  1. 5mo agoforestlyDownload button, AE filter label and diff toggle become optional
  2. 11mo agoforestlyStatic RTF forest plots join the interactive output
  3. 1y agomarkdownmark() becomes a thin wrapper around litedown::mark()
  4. 1y agoforestlyreactR 0.6.0 rendering fix and slider label control
  5. 2y agoforestlyTreatment group selection and rough-edge fixes
  6. 2y agomarkdownPackage declared feature-complete; work moves to litedown
  7. 2y agomarkdownAdds compatibility shims for rmarkdown's document functions
  8. 2y agomarkdownFixes verbatim code blocks with language attributes
  9. 2y agomarkdownFixes raw blocks broken by code-block attribute support
  10. 2y agomarkdownFenced code blocks gain attributes; HTML widgets render
  11. 3y agoforestlyFirst release on GitHub and CRAN

Frequently asked questions

What is the difference between forestly and markdown?

They serve adjacent needs but don't currently overlap on shipped themes. forestly and markdown 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.

Is forestly better than markdown?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. forestly and markdown 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 Analytics products to evaluate alongside.

What are the best alternatives to forestly?

Top forestly alternatives in Analytics are ranked by recent ship velocity. Browse the "forestly alternatives" section above for the current picks, or visit /alternatives/forestly for the full list with editorial commentary on each.

What are the best alternatives to markdown?

Top markdown alternatives in Analytics are ranked by recent ship velocity. Browse the "markdown alternatives" section above for the current picks, or visit /alternatives/markdown for the full list with editorial commentary on each.