Core Extensions
RLX FAQ
Flexible public FAQ categories and answer cards with admin management, visibility controls, search-friendly output, and support/KB handoff links.
What it does
Features at a glance
- Turns scattered community information into managed pages and repeatable content flows
- Gives owners a stronger reason to keep members inside the RLX site
- RLX FAQ can be packaged as an optional upgrade, bundle component, or project-specific module
- RLX FAQ provides a focused Community capability for LifeRaft OS based on its manifest and documentation
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 FAQ and review its add-on settings
- Configure the module settings and permissions
- Add the records, content, media, or rules this module manages
Before you choose
Common questions
What does RLX FAQ do?
Flexible public FAQ categories and answer cards with admin management, visibility controls, search-friendly output, and support/KB handoff links.
What does RLX FAQ need to run?
RLX FAQ 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 FAQ 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 FAQ part of your build.
Discuss the fit, requirements, and next steps for your project.