Core Extensions
RLX Blog
Publish one or several Blogs with independent layouts, editorial roles, drafts, scheduled posts, revisions, and Gallery artwork. Feature selected public posts on a brand page.
What it does
Features at a glance
- Run multiple Blogs with separate names, descriptions, posts, and presentation settings
- Choose a simple post directory or a widget-based portal for each Blog
- Write drafts, schedule publication, and keep revisions during editorial work
- Use configurable featured media, Gallery artwork, and visual links within posts
- Organize publishing through author, editor, and reviewer workflows
- Feature selected published public posts on brand pages while retaining Blog visibility and publication checks
Built for your workflow
Who it’s for
- Independent writers and creators publishing regular updates
- Studios and products maintaining a news or release journal
- Teams managing several editorial sections or authors
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
- Set up a Blog and choose its directory or portal layout
- Prepare posts with artwork, summaries, categories, and an editorial review
- Publish or schedule the posts, then feature eligible stories on the relevant brand
Before you choose
Common questions
What does RLX Blog do?
Publish one or several Blogs with independent layouts, editorial roles, drafts, scheduled posts, revisions, and Gallery artwork. Feature selected public posts on a brand page.
What does RLX Blog need to run?
RLX Blog 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 Blog 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 Blog part of your build.
Discuss the fit, requirements, and next steps for your project.