LifeRaft OSTM

Core Extensions add-on

RLX Pages & CMS

Custom and structured landing pages with editorial thread bridges, public extension regions and widgets, presets, homepage routing, revisions, SEO, and visibility controls.

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

About this add-on

RLX Pages & CMS for LifeRaft OS

RLX Pages & CMS is the maintained custom-page and landing-page provider for LifeRaft OS. It implements the `rlx-pages` alias without creating a second page database or competing homepage router.

Custom and structured landing pages with editorial thread bridges, public extension regions and widgets, presets, homepage routing, revisions, SEO, and visibility controls. Use it when the site needs stronger publishing, cleaner self-service information, or a serious web workflow without commissioning a custom build. The practical win: admin-managed custom pages for public, member-only, private staff, and owner-only content.

At a glance
  • Admin-managed custom pages for public, member-only, private staff, and owner-only content
  • Markdown page body editor with the shared RLX editor toolbar
  • Live editor preview/upload behavior through the shared composer hooks
  • Turns scattered information into managed, branded, searchable site workflows
rlx-cms Version 1.3.0 $44.85 · Everyday Production

Capabilities and outcomes

How RLX Pages & CMS 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 Pages & CMS without forcing it into every install

Add-on-specific scope

What RLX Pages & CMS manages

Explain the outcome before listing implementation details.

Standalone value

What it does by itself

RLX Pages & CMS can run as its own Core Extensions workflow. By itself, it focuses on Admin-managed custom pages for public, member-only, private staff, and owner-only content, Markdown page body editor with the shared RLX editor toolbar, and Live editor preview/upload behavior through the shared composer hooks, 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 Legal, RLX Blog, RLX Wiki, RLX Knowledge Base, and RLX FAQ, RLX Pages & CMS 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 custom pages for public, member-only, private staff, and owner-only content
  • Markdown page body editor with the shared RLX editor toolbar
  • Live editor preview/upload behavior through the shared composer hooks
  • Core Extensions builds that need RLX Pages & CMS without forcing it into every install

Workflow

How it fits into a real build

  1. Activate RLX Pages & CMS and review its add-on settings
  2. Admin-managed custom pages for public, member-only, private staff, and owner-only content
  3. Markdown page body editor with the shared RLX editor toolbar
  4. Live editor preview/upload behavior through the shared composer hooks

Works well with

The strongest builds connect the right modules

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

What does RLX Pages & CMS do?

Custom and structured landing pages with editorial thread bridges, public extension regions and widgets, presets, homepage routing, revisions, SEO, and visibility controls.

Who is RLX Pages & CMS best for?

Admin-managed custom pages for public, member-only, private staff, and owner-only content. Markdown page body editor with the shared RLX editor toolbar. Live editor preview/upload behavior through the shared composer hooks.

Can RLX Pages & CMS run by itself?

RLX Pages & CMS can run as its own Core Extensions workflow. By itself, it focuses on Admin-managed custom pages for public, member-only, private staff, and owner-only content, Markdown page body editor with the shared RLX editor toolbar, and Live editor preview/upload behavior through the shared composer hooks, 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 Pages & CMS 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 Legal, RLX Blog, RLX Wiki, RLX Knowledge Base, and RLX FAQ, RLX Pages & CMS 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 Pages & CMS?

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

What should be decided before launching RLX Pages & CMS?

RLX Pages & CMS should be launched with its real data model and public routes in mind. Optional integrations: rlx-legal, rlx-blog, rlx-wiki, rlx-knowledge-base, rlx-faq, rlx-support, rlx-forms, rlx-contact, rlx-waitlist, rlx-landing-intake, rlx-newsletter, rlx-stats.

How much does RLX Pages & CMS cost?

RLX Pages & CMS 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 Pages & CMS?

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 Pages & CMS for deployment?

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

How does RLX Pages & CMS fit into a real LifeRaft OS build?

Activate RLX Pages & CMS and review its add-on settings. Admin-managed custom pages for public, member-only, private staff, and owner-only content. Markdown page body editor with the shared RLX editor toolbar. Live editor preview/upload behavior through the shared composer hooks.

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 Pages & CMS in your LifeRaft OS build?

RLX Pages & CMS 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.