RLX Wiki

Knowledge base and wiki pages with categories, revisions, Markdown or optional sanitized structured HTML editing, contributor editors, author attribution, and public documentation views.

Public or permission-gated wiki pages with Markdown content, categories, projects, templates, parent pages, related. Revision history, restore support, attachments, author attribution presets, and optional contributor editors. Admin controls for visibility, editor access, author defaults, page widgets, metadata panels, related pages, child.

RLX Wiki can run as its own Core Extensions workflow. By itself, it focuses on Public or permission-gated wiki pages with Markdown content, categories, projects, templates, parent pages, related pages, child, Revision history, restore support, attachments, author attribution presets, and optional contributor editors, and Admin controls for visibility, editor access, author defaults, page widgets, metadata panels, related pages, child pages, attachm, so a customer can use the module without buying every related add-on first.

No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Wiki 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.

When the customer also owns and activates related modules such as RLX Blog, RLX Pages & CMS, RLX Knowledge Base, RLX FAQ, and RLX Support, RLX Wiki 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.

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

RLX Wiki should be launched with its real data model and public routes in mind. Optional integrations: rlx-blog, rlx-cms, rlx-knowledge-base, rlx-faq, rlx-support, rlx-changelog, rlx-resources, rlx-brands, rlx-teams, rlx-license, rlx-membership.

RLX Wiki has a $44.85 Everyday add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.

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.

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

Activate RLX Wiki and review its add-on settings. Public or permission-gated wiki pages with Markdown content, categories, projects, templates, parent pages, related pages, child pages. Revision history, restore support, attachments, author attribution presets, and optional contributor editors. Admin controls for visibility, editor access, author defaults, page widgets, metadata panels, related pages, child pages, attachments.

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.