Platform add-on
RLX Taxonomy
Shared optional topics, tags, collections, and content-type links for cross-add-on browsing without replacing local add-on categories.
PlatformCategory
0.1.0Version
ProductionRelease stage
$34.85 · FocusedLicense
Platform add-on
About this add-on
RLX Taxonomy for LifeRaft OS
RLX Taxonomy provides shared topics, tags, collections, and content-type links across LifeRaft OS add-ons.
Shared optional topics, tags, collections, and content-type links for cross-add-on browsing without replacing local add-on categories. Use it when a customer package needs a focused capability that should stay optional, sellable, and supportable.
At a glance
- Admin-managed content and settings
- Public pages with clean presentation
- Designed to run as an optional RLX module
- Keeps the core install lean while preserving room for specialized customer requirements
rlx-taxonomy
Version 0.1.0 $34.85 · Focused
Production
Capabilities and outcomes
How RLX Taxonomy improves the build
The overview above identifies the core capability. These supporting outcomes help a project owner judge whether the add-on belongs in the package.
Adds a sellable capability without forcing unrelated workflows into every package
RLX Taxonomy can be packaged as an optional upgrade, bundle component, or project-specific module
Platform builds that need RLX Taxonomy without forcing it into every install
Standalone value
What it does by itself
RLX Taxonomy can run as its own Platform workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.
Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
Connected value
What improves when related add-ons are active
When the customer also owns and activates related modules such as RLX Related, RLX Activity, RLX Featured, RLX Experience Studio, and RLX Decorations, RLX Taxonomy can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Best fit
Who should care about it
- Platform builds that need RLX Taxonomy without forcing it into every install
Workflow
How it fits into a real build
- Activate RLX Taxonomy and review its add-on settings
- Configure the module settings and permissions
- Add the records, content, media, or rules this module manages
- Review public pages and backend empty states before launch
Works well with
The strongest builds connect the right modules
RLX Taxonomy becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Related, RLX Activity, RLX Featured, RLX Experience Studio, RLX Decorations, depending on the customer package and what the site needs to accomplish.
Admin setup
Confirm settings, navigation placement, permissions, and any required starter content before launch.
Public QA
Review the public page, empty states, mobile layout, and activated/deactivated states.
Package QA
Confirm the module fits the selected product package and does not expose unused workflows.
Docs and support
Add customer-facing notes, admin setup instructions, and known limitations for the module.
Customer FAQ
Common questions about RLX Taxonomy
What does RLX Taxonomy do?
Shared optional topics, tags, collections, and content-type links for cross-add-on browsing without replacing local add-on categories.
Who is RLX Taxonomy best for?
Platform builds that need RLX Taxonomy without forcing it into every install.
Can RLX Taxonomy run by itself?
RLX Taxonomy can run as its own Platform workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.
Do I need the other add-ons mentioned on this page?
No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Taxonomy should still explain a useful standalone job before any connected modules are considered. Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
What changes when related add-ons are active?
When the customer also owns and activates related modules such as RLX Related, RLX Activity, RLX Featured, RLX Experience Studio, and RLX Decorations, RLX Taxonomy can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Which add-ons work well with RLX Taxonomy?
RLX Taxonomy commonly pairs with RLX Related, RLX Activity, RLX Featured, RLX Experience Studio, RLX Decorations. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX Taxonomy?
RLX Taxonomy should be launched with its real data model and public routes in mind. Optional integrations: rlx-related, rlx-activity, rlx-featured.
How much does RLX Taxonomy cost?
RLX Taxonomy has a $34.85 Focused add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.
What support is included for RLX Taxonomy?
Standard add-on support covers the licensed module during the active support window of the selected core edition. Exact scope is confirmed with the package. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.
How ready is RLX Taxonomy for deployment?
Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.
How does RLX Taxonomy fit into a real LifeRaft OS build?
Activate RLX Taxonomy and review its add-on settings. Configure the module settings and permissions. Add the records, content, media, or rules this module manages. Review public pages and backend empty states before launch.
Does the public page include implementation details?
No. The public page explains customer value, package fit, related modules, and launch expectations. Setup steps, route details, data structures, hooks, and operator-only notes stay in the licensed add-on documentation.
Related add-ons
Explore the surrounding add-on ecosystem
Coming soon
Want RLX Taxonomy in your LifeRaft OS build?
RLX Taxonomy is part of the modular LifeRaft OS add-on roadmap. Join the waitlist or discuss a package so the right modules can be planned around the way your community, product, studio, or business actually operates.