Publishing & Authors add-on
RLX Submissions
Pitches, articles, manuscripts, attachments, reviewer assignment, decisions, revision requests, consent, and contributor communication.
Publishing & AuthorsCategory
0.1.0Version
PreviewRelease stage
$64.85 · AdvancedLicense
Publishing & Authors add-on
About this add-on
RLX Submissions for LifeRaft OS
Pitches, articles, manuscripts, attachments, reviewer assignment, decisions, revision requests, consent, and contributor communication.
At a glance
- Admin-managed content and settings
- Public pages with clean presentation
- Designed to run as an optional RLX module
- Turns drafts, contributors, editorial decisions, and releases into a visible workflow
rlx-submissions
Version 0.1.0 $64.85 · Advanced
Preview
Capabilities and outcomes
How RLX Submissions 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.
Connects living knowledge and forum discussion without duplicating identity, files, or delivery systems
RLX Submissions can be packaged as an optional upgrade, bundle component, or project-specific module
Publishing & Authors builds that need RLX Submissions without forcing it into every install
Add-on-specific scope
What RLX Submissions manages
This module manages submissions as its primary customer-facing records.
Standalone value
What it does by itself
RLX Submissions can run as its own Publishing & Authors workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, 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 Authors, RLX Forms, RLX Manuscripts, RLX Notifications, and RLX Editorial Calendar, RLX Submissions 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
- Publishing & Authors builds that need RLX Submissions without forcing it into every install
Workflow
How it fits into a real build
- pending, screening, review, revision-requested, accepted, declined, withdrawn, archived
Works well with
The strongest builds connect the right modules
RLX Submissions becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Authors, RLX Forms, RLX Manuscripts, RLX Notifications, RLX Editorial Calendar, 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 Submissions
What does RLX Submissions do?
Pitches, articles, manuscripts, attachments, reviewer assignment, decisions, revision requests, consent, and contributor communication.
Who is RLX Submissions best for?
Publishing & Authors builds that need RLX Submissions without forcing it into every install.
Can RLX Submissions run by itself?
RLX Submissions can run as its own Publishing & Authors workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, 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 Submissions 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 Authors, RLX Forms, RLX Manuscripts, RLX Notifications, and RLX Editorial Calendar, RLX Submissions 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 Submissions?
RLX Submissions commonly pairs with RLX Authors, RLX Forms, RLX Manuscripts, RLX Notifications, RLX Editorial Calendar. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX Submissions?
RLX Submissions should be launched with its real data model and public routes in mind. Optional integrations: rlx-authors, rlx-forms, rlx-manuscripts, rlx-notifications, rlx-consent.
How much does RLX Submissions cost?
RLX Submissions 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 Submissions?
Enhanced add-on support indicates a broader or more operationally involved module. Exact response scope and duration are confirmed with the licensed package and core edition. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.
How ready is RLX Submissions for deployment?
Preview module: available for evaluation and scoped deployments while runtime evidence and product polish continue to mature.
How does RLX Submissions fit into a real LifeRaft OS build?
pending, screening, review, revision-requested, accepted, declined, withdrawn, archived.
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.
Related add-ons
Explore the surrounding add-on ecosystem
Coming soon
Want RLX Submissions in your LifeRaft OS build?
RLX Submissions 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.