LifeRaft OSTM
← All add-ons

Publishing & Authors

RLX Experience Studio

Compose, validate, preview, publish, export, import, remove, and roll back Visual Packs with per-surface layouts, component families, and managed responsive artwork.

ProductionVersion 1.6.0
Product images coming soonA closer look at RLX Experience Studio.

What it does

Features at a glance

  • Per-surface Visual Composition Designer
  • Expanded Component Skin families
  • Five protected reference profiles

Built for your workflow

Who it’s for

  • Writers and publishers maintaining an owned content hub
  • Editorial teams organizing stories and reader experiences

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

  1. Activate RLX Experience Studio and review its add-on settings
  2. Per-surface Visual Composition Designer
  3. Expanded Component Skin families

Before you choose

Common questions

What does RLX Experience Studio do?

Compose, validate, preview, publish, export, import, remove, and roll back Visual Packs with per-surface layouts, component families, and managed responsive artwork.

What does RLX Experience Studio need to run?

RLX Experience Studio 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 Experience Studio 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 Experience Studio part of your build.

Discuss the fit, requirements, and next steps for your project.

Let’s talk