Platform
RLX Changelog
Self-contained changelog and release notes system with Markdown import/update/merge, attachments, revisions, JSON import/export, and optional release/update links.
What it does
Features at a glance
- Public changelog directory and entry detail pages
- Admin CRUD for entries, categories, revisions, and attachments
- Keeps the core install lean while preserving room for specialized customer requirements
- Adds a sellable feature without forcing unrelated workflows into every package
- Markdown editor support with the same drag/drop attachment control used by threads. md import with create, update, and merge modes
Built for your workflow
Who it’s for
- Platform 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.
Optional connections
From setup to everyday use
A straightforward starting point
- Activate RLX Changelog and review its add-on settings
- Public changelog directory and entry detail pages
- Admin CRUD for entries, categories, revisions, and attachments
Before you choose
Common questions
What does RLX Changelog do?
Self-contained changelog and release notes system with Markdown import/update/merge, attachments, revisions, JSON import/export, and optional release/update links.
What does RLX Changelog need to run?
RLX Changelog 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 Changelog 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 Changelog part of your build.
Discuss the fit, requirements, and next steps for your project.