LifeRaft OSTM

Core Extensions add-on

RLX Directory

Public resource directory with member submissions, approval queue, profiles, sponsored slots, link imports, click tracking, and related forum widgets.

Core ExtensionsCategory
1.0.0Version
ProductionRelease stage
$44.85 · EverydayLicense
Back to catalog
Core Extensions add-on

About this add-on

RLX Directory for LifeRaft OS

Public resource directory with member submissions, approval queue, profiles, sponsored slots, link imports, click

At a glance
  • Admin-managed content and settings
  • Public pages with clean presentation
  • Designed to run as an optional RLX module
  • Turns scattered information into managed, branded, searchable site workflows
rlx-directory Version 1.0.0 $44.85 · Everyday Production

Capabilities and outcomes

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

Turns scattered information into managed, branded, searchable site workflows

Gives web admins a concrete upgrade path without bloating the base install

Core Extensions builds that need RLX Directory without forcing it into every install

Standalone value

What it does by itself

RLX Directory can run as its own Core Extensions 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 Pages & CMS, RLX Blog, RLX Wiki, RLX FAQ, and RLX Knowledge Base, RLX Directory 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

  • Admin-managed content and settings
  • Public pages with clean presentation
  • Designed to run as an optional RLX module
  • Core Extensions builds that need RLX Directory without forcing it into every install

Workflow

How it fits into a real build

  1. Activate rlx-directory
  2. Review pending member submissions
  3. Mark resources approved, featured, sponsored, or inactive
  4. Use import tools for bulk link creation when needed
  5. approved, featured, sponsored, or inactive

Works well with

The strongest builds connect the right modules

RLX Directory becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Pages & CMS, RLX Blog, RLX Wiki, RLX FAQ, RLX Knowledge Base, 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 Directory

What does RLX Directory do?

Public resource directory with member submissions, approval queue, profiles, sponsored slots, link imports, click tracking, and related forum widgets.

Who is RLX Directory best for?

Admin-managed content and settings. Public pages with clean presentation. Designed to run as an optional RLX module.

Can RLX Directory run by itself?

RLX Directory can run as its own Core Extensions 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 Directory 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 Pages & CMS, RLX Blog, RLX Wiki, RLX FAQ, and RLX Knowledge Base, RLX Directory 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 Directory?

RLX Directory commonly pairs with RLX Pages & CMS, RLX Blog, RLX Wiki, RLX FAQ, RLX Knowledge Base. Active pairings depend on the package, customer workflow, and installed add-ons.

What should be decided before launching RLX Directory?

RLX Directory should be launched with its real data model and public routes in mind. Routes: RLX Directory is exposed through the routes registered by its add-on entry file when the module is active. During, launch, teams should confirm the public page, admin entry point, empty states, permissions, and navigation placement, match the package being sold.

How much does RLX Directory cost?

RLX Directory 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 Directory?

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

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

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

Activate rlx-directory. Review pending member submissions. Mark resources approved, featured, sponsored, or inactive. Use import tools for bulk link creation when needed.

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 Directory in your LifeRaft OS build?

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