LifeRaft OSTM

Core Extensions add-on

RLX Blog

Editorial publishing with multiple independent Blogs, per-Blog posts and widget layouts, separate landing and compact archive views, optional sanitized structured HTML, responsive media, historical dates, scheduling, revisions, and SEO.

Core ExtensionsCategory
0.11.3Version
ProductionRelease stage
$64.85 · AdvancedLicense
Back to catalog
Core Extensions add-on

About this add-on

RLX Blog for LifeRaft OS

RLX Blog adds a structured publishing system for announcements, release notes, editorials, tutorials, customer updates, and ecosystem stories. It can stay simple with admin-only posting, or expand into a contributor workflow with assigned editors and author attribution.

Editorial publishing with multiple independent Blogs, per-Blog posts and widget layouts, separate landing and compact archive views, optional sanitized structured HTML, responsive media, historical dates... Use it when the site needs stronger publishing, cleaner self-service information, or a serious web workflow without commissioning a custom build. The practical win: multiple independent Blogs with their own public title, description,.

At a glance
  • Blog categories, public post listings, featured posts, public post detail pages, widgets, and navigation integration
  • Markdown post body editor with drafts, published posts, archived posts, featured images, attachments, revisions, and restore supp
  • SEO fields for title and meta description so posts can become clean public landing content
  • Multiple independent Blogs with their own public title, description,
rlx-blog Version 0.11.3 $64.85 · Advanced Production

Capabilities and outcomes

How RLX Blog 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.

Multiple independent Blogs with their own public title, description,

visibility, posts, and public presentation mode

Turns scattered information into managed, branded, searchable site workflows

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

Each Blog independently chooses **Simple Post Directory** or **Widget

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

Standalone value

What it does by itself

RLX Blog can run as its own Core Extensions workflow. By itself, it focuses on Blog categories, public post listings, featured posts, public post detail pages, widgets, and navigation integration, Markdown post body editor with drafts, published posts, archived posts, featured images, attachments, revisions, and restore supp, and SEO fields for title and meta description so posts can become clean public landing content, 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 Wiki, RLX Pages & CMS, RLX Knowledge Base, RLX FAQ, and RLX Support, RLX Blog 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

  • Multiple independent Blogs with their own public title, description,
  • visibility, posts, and public presentation mode
  • Each Blog independently chooses **Simple Post Directory** or **Widget
  • Core Extensions builds that need RLX Blog without forcing it into every install

Workflow

How it fits into a real build

  1. Activate RLX Blog and review its add-on settings
  2. Multiple independent Blogs with their own public title, description,
  3. visibility, posts, and public presentation mode
  4. Each Blog independently chooses **Simple Post Directory** or **Widget

Works well with

The strongest builds connect the right modules

RLX Blog becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Wiki, RLX Pages & CMS, RLX Knowledge Base, RLX FAQ, RLX Support, 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 Blog

What does RLX Blog do?

Editorial publishing with multiple independent Blogs, per-Blog posts and widget layouts, separate landing and compact archive views, optional sanitized structured HTML, responsive media, historical dates, scheduling, revisions, and SEO.

Who is RLX Blog best for?

Multiple independent Blogs with their own public title, description,. visibility, posts, and public presentation mode. Each Blog independently chooses **Simple Post Directory** or **Widget.

Can RLX Blog run by itself?

RLX Blog can run as its own Core Extensions workflow. By itself, it focuses on Blog categories, public post listings, featured posts, public post detail pages, widgets, and navigation integration, Markdown post body editor with drafts, published posts, archived posts, featured images, attachments, revisions, and restore supp, and SEO fields for title and meta description so posts can become clean public landing content, 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 Blog 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 Wiki, RLX Pages & CMS, RLX Knowledge Base, RLX FAQ, and RLX Support, RLX Blog 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 Blog?

RLX Blog commonly pairs with RLX Wiki, RLX Pages & CMS, RLX Knowledge Base, RLX FAQ, RLX Support. Active pairings depend on the package, customer workflow, and installed add-ons.

What should be decided before launching RLX Blog?

RLX Blog should be launched with its real data model and public routes in mind. Optional integrations: rlx-wiki, rlx-cms, rlx-knowledge-base, rlx-faq, rlx-support, rlx-changelog, rlx-resources, rlx-newsletter, rlx-brands, rlx-teams, rlx-stats, rlx-license, rlx-membership.

How much does RLX Blog cost?

RLX Blog has a $64.85 Advanced 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 Blog?

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 Blog for deployment?

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

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

Activate RLX Blog and review its add-on settings. Multiple independent Blogs with their own public title, description,. visibility, posts, and public presentation mode. Each Blog independently chooses **Simple Post Directory** or **Widget.

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 Blog in your LifeRaft OS build?

RLX Blog 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.