LifeRaft OSTM

Core Extensions add-on

RLX Timeline

Chronological milestone, release, event, story, and project-history timelines for LifeRaft OS.

Core ExtensionsCategory
1.0.0Version
ProductionRelease stage
$44.85 · EverydayLicense
Back to catalog
Core Extensions add-on

About this add-on

RLX Timeline for LifeRaft OS

Chronological milestone, release, event, story, and project-history timelines for LifeRaft OS.

At a glance
  • Public chronological timeline for milestones, releases, events, campaigns, incidents, and project history
  • Standalone mode for simple installs plus optional cross-links to planning, publishing, media, support, and reporting modules
  • Admin-managed dates, statuses, badges, media URLs, source links, CTA links, visibility, and sort order
  • Public timeline route with grouped chronological cards
rlx-timeline Version 1.0.0 $44.85 · Everyday Production

Capabilities and outcomes

How RLX Timeline improves the build

The overview above identifies the core capability. These supporting outcomes help a project owner judge whether the add-on belongs in the package.

Public timeline route with grouped chronological cards

Detail pages for individual milestones with optional source links and CTAs

Turns scattered information into managed, branded, searchable site workflows

Gives web admins a concrete upgrade path without bloating the base install

Admin CRUD for milestones, dates, type, status, badges, body copy, links, and visibility

Core Extensions builds that need RLX Timeline without forcing it into every install

Standalone value

What it does by itself

RLX Timeline can run as its own Core Extensions workflow. By itself, it focuses on Public chronological timeline for milestones, releases, events, campaigns, incidents, and project history, Standalone mode for simple installs plus optional cross-links to planning, publishing, media, support, and reporting modules, and Admin-managed dates, statuses, badges, media URLs, source links, CTA links, visibility, and sort order, so a customer can use the module without buying every related add-on first.

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.

Connected value

What improves when related add-ons are active

When the customer also owns and activates related modules such as RLX Roadmap, RLX Calendar, RLX Changelog, RLX Blog, and RLX Gallery, RLX Timeline 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.

Best fit

Who should care about it

  • 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
  • Core Extensions builds that need RLX Timeline without forcing it into every install

Workflow

How it fits into a real build

  1. Activate rlx-timeline and review its add-on settings
  2. Add milestones from Admin > RLX Timeline with date, type, status, summary, body, links, and visibility
  3. Use optional related add-on fields to cross-link roadmap, calendar, changelog, blog, gallery, video, support, or form
  4. routes when those modules are active
  5. Publish the public timeline as a standalone history page or package it beside other LifeRaft OS modules

Works well with

The strongest builds connect the right modules

RLX Timeline becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Roadmap, RLX Calendar, RLX Changelog, RLX Blog, RLX Gallery, depending on the customer package and what the site needs to accomplish.

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.

Customer FAQ

Common questions about RLX Timeline

What does RLX Timeline do?

Chronological milestone, release, event, story, and project-history timelines for LifeRaft OS.

Who is RLX Timeline best for?

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.

Can RLX Timeline run by itself?

RLX Timeline can run as its own Core Extensions workflow. By itself, it focuses on Public chronological timeline for milestones, releases, events, campaigns, incidents, and project history, Standalone mode for simple installs plus optional cross-links to planning, publishing, media, support, and reporting modules, and Admin-managed dates, statuses, badges, media URLs, source links, CTA links, visibility, and sort order, so a customer can use the module without buying every related add-on first.

Do I need the other add-ons mentioned on this page?

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

What changes when related add-ons are active?

When the customer also owns and activates related modules such as RLX Roadmap, RLX Calendar, RLX Changelog, RLX Blog, and RLX Gallery, RLX Timeline 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.

Which add-ons work well with RLX Timeline?

RLX Timeline commonly pairs with RLX Roadmap, RLX Calendar, RLX Changelog, RLX Blog, RLX Gallery. Active pairings depend on the package, customer workflow, and installed add-ons.

What should be decided before launching RLX Timeline?

RLX Timeline should be launched with its real data model and public routes in mind. Routes: These are the URLs buyers, members, or admins should expect to test. Video, CMS, Blog, or uploaded asset workflows without owning heavy storage Optional integrations: rlx-roadmap, rlx-calendar, rlx-changelog, rlx-blog, rlx-gallery, rlx-video, rlx-analytics, rlx-stats, rlx-forms, rlx-support, rlx-cms, rlx-newsletter.

How much does RLX Timeline cost?

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

What support is included for RLX Timeline?

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.

How ready is RLX Timeline for deployment?

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

How does RLX Timeline fit into a real LifeRaft OS build?

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.

Does the public page include implementation details?

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.

Coming soon

Want RLX Timeline in your LifeRaft OS build?

RLX Timeline is part of the modular LifeRaft OS add-on roadmap. Join the waitlist or discuss a package so the right modules can be planned around the way your community, product, studio, or business actually operates.