Core Extensions
RLX CMS
Advanced landing and editorial pages with thread bridges, public widget regions, presets, homepage routing, revisions, SEO, and visibility controls. RLX Pages is a separate lightweight add-on.
What it does
Features 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
- CMS homepage routing for communities that want a landing-style page instead of the forum index
- Shell placement controls for each page: top nav left, center, right, or no nav; footer left, center, right, or no footer
- Link label and link order fields for clean navigation
Built for your workflow
Who it’s for
- Core Extensions projects that need this focused capability
- Owners who want to activate only the workflows their site needs
Setup and fit
Compatibility
Requires a valid LifeRaft OS core license and a supported installation.
No additional add-on is listed as a required dependency.
From setup to everyday use
A straightforward starting point
- Activate RLX 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
Before you choose
Common questions
What does RLX CMS do?
Advanced landing and editorial pages with thread bridges, public widget regions, presets, homepage routing, revisions, SEO, and visibility controls. RLX Pages is a separate lightweight add-on.
What does RLX CMS need to run?
RLX CMS runs on the LifeRaft OS core without another add-on listed as a required dependency. Optional integrations can be added for a broader workflow.
How ready is RLX CMS for deployment?
Production is this add-on’s declared release stage. The V5 platform is a development build; review the workflows, hosting, and integrations you plan to use.
Review the launch checklist
- 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.
Make RLX CMS part of your build.
Discuss the fit, requirements, and next steps for your project.