LifeRaft OSTM

Commerce add-on

RLX Projects

Project container layer for grouping roadmap, kanban, changelog, docs, media, support, updates, and bridge records without hard dependencies.

CommerceCategory
0.1.0Version
ProductionRelease stage
$44.85 · EverydayLicense
Back to catalog
Commerce add-on

About this add-on

RLX Projects for LifeRaft OS

RLX Projects adds optional project containers for grouping typed records from other LifeRaft OS systems. It does not replace roadmap, kanban, changelog, docs, media, support, updates, or bridge add-ons.

Project container layer for grouping roadmap, kanban, changelog, docs, media, support, updates, and bridge records without hard dependencies. Use it when the community needs a revenue layer for paid access, checkout support, entitlements, offers, or product operations while keeping the core lean. The practical win: future activity, search, bookmarks, notifications, and recommendations through the shared typed entity key.

At a glance
  • Admin-managed content and settings
  • Public pages with clean presentation
  • Designed to run as an optional RLX module
  • Future activity, search, bookmarks, notifications, and recommendations through the shared typed entity key
rlx-projects Version 0.1.0 $44.85 · Everyday Production

Capabilities and outcomes

How RLX Projects 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.

Future activity, search, bookmarks, notifications, and recommendations through the shared typed entity key

Creates monetization surface area that can be sold above a core community build

Keeps paid workflows modular so customers activate only the revenue tools they need

RLX Projects can be packaged as an optional upgrade, bundle component, or project-specific module

Commerce builds that need RLX Projects without forcing it into every install

Standalone value

What it does by itself

RLX Projects can run as its own Commerce 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 Taxonomy, RLX Search, and RLX Bookmarks, RLX Projects 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

  • Future activity, search, bookmarks, notifications, and recommendations through the shared typed entity key
  • Commerce builds that need RLX Projects without forcing it into every install

Workflow

How it fits into a real build

  1. Activate RLX Projects and review its add-on settings
  2. Future activity, search, bookmarks, notifications, and recommendations through the shared typed entity key
  3. Add the records, content, media, or rules this module manages
  4. Review public pages and backend empty states before launch

Works well with

The strongest builds connect the right modules

RLX Projects becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Related, RLX Activity, RLX Taxonomy, RLX Search, RLX Bookmarks, 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.

Payment QA

Test provider setup, order states, entitlements, refunds, and failed-payment recovery.

Docs and support

Add customer-facing notes, admin setup instructions, and known limitations for the module.

Customer FAQ

Common questions about RLX Projects

What does RLX Projects do?

Project container layer for grouping roadmap, kanban, changelog, docs, media, support, updates, and bridge records without hard dependencies.

Who is RLX Projects best for?

Future activity, search, bookmarks, notifications, and recommendations through the shared typed entity key. Commerce builds that need RLX Projects without forcing it into every install.

Can RLX Projects run by itself?

RLX Projects can run as its own Commerce 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 Projects 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 Taxonomy, RLX Search, and RLX Bookmarks, RLX Projects 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 Projects?

RLX Projects commonly pairs with RLX Related, RLX Activity, RLX Taxonomy, RLX Search, RLX Bookmarks. Active pairings depend on the package, customer workflow, and installed add-ons.

What should be decided before launching RLX Projects?

RLX Projects should be launched with its real data model and public routes in mind. Optional integrations: rlx-related, rlx-activity, rlx-taxonomy, rlx-search, rlx-bookmarks, rlx-notifications, rlx-roadmap, rlx-kanban, rlx-changelog, rlx-support, rlx-resources.

How much does RLX Projects cost?

RLX Projects has a $44.85 Everyday 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 Projects?

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 Projects for deployment?

Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.

How does RLX Projects fit into a real LifeRaft OS build?

Activate RLX Projects and review its add-on settings. Future activity, search, bookmarks, notifications, and recommendations through the shared typed entity key. 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.

Coming soon

Want RLX Projects in your LifeRaft OS build?

RLX Projects 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.