WPML
WPML made machine translation the default, and its point releases keep chasing WordPress and page builders.
Comparison · Infra & APIs
legendry vs traits.build
A side-by-side editorial comparison of legendry and traits.build — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
legendry vs traits.build: at a glance
What is legendry?
A ggplot2 extension quietly turning axes and legends into a place where other plots can live.
legendry extends ggplot2's guide system, letting axes and legends be composed from primitives and keys rather than accepted as given. The most recent release added guides for user-defined keys, upset matrices, arbitrary symbol placement, freeform annotations, and side-plots attached to an axis, plus a run-length-encoded range key and subtitles on custom axes. Between feature releases the package ships small patches, several of them tracking ggplot2's own changes.
What is traits.build?
The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.
traits.build is the harmonisation workflow extracted from AusTraits and generalised so other groups can assemble trait databases from heterogeneous sources. Its schema and ontology reached 1.0.0 in late 2024, and the package now leans on austraits itself for the functions that belong to database consumption rather than construction. The 2025 release extends the data model with identifiers and methods tables.
legendry vs traits.build: editorial side-by-side
legendry
0.0INFRA · APIS
A ggplot2 extension quietly turning axes and legends into a place where other plots can live.
◆ Current state
legendry extends ggplot2's guide system, letting axes and legends be composed from primitives and keys rather than accepted as given. The most recent release added guides for user-defined keys, upset matrices, arbitrary symbol placement, freeform annotations, and side-plots attached to an axis, plus a run-length-encoded range key and subtitles on custom axes. Between feature releases the package ships small patches, several of them tracking ggplot2's own changes.
◆ Where it's heading
The direction is toward treating a guide as a rendering slot rather than a label strip. Dendrogram scales arrived in 0.2.0 with a matching axis guide; the newest release adds side-plots and upset symbol matrices to the same position. Each of these puts real graphical content where an axis used to be, and each one ships with a key function so the composition stays user-controllable. Note that this feed's order is unreliable: 0.2.1 was published eight months after 0.2.4 and minutes before 0.3.0, so neither version numbers nor timestamps indicate release order here.
◆ Prediction
The pattern of pairing each new guide with a matching key function is consistent enough that the next feature release will likely follow it again; the recurring forwards-compatibility patches also suggest another ggplot2-tracking release whenever upstream moves.
traits.build
0.0INFRA · APIS
The AusTraits engine, generalised for anyone's trait database, now links measurements to real specimens.
◆ Current state
traits.build is the harmonisation workflow extracted from AusTraits and generalised so other groups can assemble trait databases from heterogeneous sources. Its schema and ontology reached 1.0.0 in late 2024, and the package now leans on austraits itself for the functions that belong to database consumption rather than construction. The 2025 release extends the data model with identifiers and methods tables.
◆ Where it's heading
The project's direction is toward provenance and interoperability rather than throughput. Value types grew to carry standard error and standard deviation, the methods table now records what kind of source each dataset came from, and the identifiers table lets a trait value point at a herbarium sheet, a museum accession or a GenBank record. Alongside that, responsibilities have been split with the sibling austraits package, with shared functions moved out under deprecation shims. A published paper and a versioned ontology mark it as infrastructure meant for outside adoption, not just for AusTraits.
◆ Prediction
Expect further schema extensions in the same provenance direction, since the last two releases both added structure for describing where a measurement came from rather than new processing capability.
Alternatives to legendry and traits.build
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 legendry or traits.build.
forestploter
A forest plot package that keeps handing users control of one more graphical detail.
ggInterval
Interval-valued data plotting, spending 2026 making its function names and examples survive CRAN.
rgm
A microbiome network model that got itself un-archived by deleting the dependency that killed it.
contagionchannels
Three releases in ten days, every one of them a CRAN reviewer's correction rather than a code change.
tidyaudit
Pipeline provenance for tidyverse workflows, recording what changed at each step without keeping the data.
See all legendry alternatives → · See all traits.build alternatives →
Recent activity from legendry and traits.build
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agolegendryFive new guides, including side-plots and upset matrices on axes
- 3mo agolegendryPatch release: guide placement, sizing and gizmo key fixes
- 11mo agolegendryCRAN fix for undeclared S7 imports
- 11mo agolegendryColourbar sizing fix; sandwich guides gain label suppression
- 1y agotraits.buildTrait values gain specimen and GenBank identifiers ⚡
- 1y agolegendryForwards-compatibility patch for an upcoming ggplot2 release
- 1y agotraits.buildFunctions move to austraits as the ontology reaches 1.0.0
- 1y agolegendryDendrogram scales and axis guide, plus a circle size guide
- 2y agotraits.buildFixes to dataset testing, reports and name standardisation
- 2y agotraits.buildAusTraits workflow generalised into a reusable package
Frequently asked questions
What is the difference between legendry and traits.build?
Both compete on the same themes — r-package — within Infra & APIs. legendry and traits.build 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 legendry better than traits.build?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. legendry and traits.build 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.
What are the best alternatives to legendry?
Top legendry alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "legendry alternatives" section above for the current picks, or visit /alternatives/legendry for the full list with editorial commentary on each.
What are the best alternatives to traits.build?
Top traits.build alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "traits.build alternatives" section above for the current picks, or visit /alternatives/traits-build for the full list with editorial commentary on each.