Publishing add-ons ship at different levels of maturity, and treating everything on the roadmap as equally production-ready is how teams end up depending on a feature still meant to be used with more caution than its polish suggests, or overlooking one that’s actually stable and ready for heavier reliance.
Why This Distinction Matters for How You Use Each Add-On
A fully live, mature add-on can reasonably be trusted with less oversight and integrated more deeply into a regular workflow. A beta or manual-stage feature warrants closer monitoring and a willingness to fall back to a manual process if it behaves unexpectedly — using both the same way risks either under-trusting something reliable or over-trusting something still being refined.
What "Live" Actually Means Here
A live add-on has moved past active refinement into stable, dependable operation — the kind of maturity that supports building regular workflows around it without needing to double-check its output every time out of caution.
What "Beta" Signals About How to Use It
Beta status means the feature is functional and useful but still being actively refined, with a higher chance of rough edges, unexpected behavior, or changes to how it works between now and its eventual stable release. Beta features are worth using, just with a closer eye and a lower initial trust threshold than a fully live feature warrants.
What "Manual" Status Means for Planning
Some capabilities remain manual by design or by current development stage — worth knowing which parts of a workflow still require hands-on effort so that planning (staffing, time estimates, expectations) accounts for the manual step rather than assuming everything is automated.
Why Roadmap Awareness Matters Beyond Current Status
Knowing what’s coming, not just what’s currently live, helps with planning — a manual process you’re building extensive workarounds for might be scheduled for automation soon, in which case investing heavily in the workaround is less valuable than it would be for a capability with no automation on the near-term roadmap.
Checking the Roadmap Periodically, Not Just at Initial Setup
Add-on maturity changes over time — a beta feature from months ago may now be fully live, and a manual process may have since gained automation. Revisiting the roadmap periodically, rather than operating on an initial understanding that’s since become outdated, keeps workflow decisions aligned with current reality.
Where to Go Next
For the complete publishing add-ons picture, see the complete guide to publishing, distribution, and site health.
