Community
RLX Timeline
Chronological milestone, release, event, story, and project-history timelines for LifeRaft OS.
What it does
Features at a glance
- Public timeline route with grouped chronological cards
- Detail pages for individual milestones with optional source links and CTAs
- Admin CRUD for milestones, dates, type, status, badges, body copy, links, and visibility
- Navigation and add-on settings
- Optional integration metadata for Roadmap, Calendar, Changelog, Blog, Gallery, Video, Analytics, Stats, Forms, Support, CMS, and Newsletter
- RLX Timeline stores public or private timeline items and renders them in date order. Each item can represent a milestone, release, event, story, campaign, incident, update, announcement, or historical note
Built for your workflow
Who it’s for
- Community owners organizing member participation
- Creators and teams adding focused social workflows
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-timeline and review its add-on settings
- Add milestones from Admin > RLX Timeline with date, type, status, summary, body, links, and visibility
- Use optional related add-on fields to cross-link roadmap, calendar, changelog, blog, gallery, video, support, or form routes when those modules are active
Before you choose
Common questions
What does RLX Timeline do?
Chronological milestone, release, event, story, and project-history timelines for LifeRaft OS.
What does RLX Timeline need to run?
RLX Timeline 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 Timeline 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 Timeline part of your build.
Discuss the fit, requirements, and next steps for your project.