RSuite Features and Capabilities

RSuite CCMS manages the full lifecycle of structured content: authoring, reuse, versioning, review, workflow automation, and multi-format publishing, in one platform built on MarkLogic. This document details what RSuite does, grouped by capability area.
See RSuite in Action

1. Structured authoring

Authors work in a familiar editor while RSuite enforces valid structure underneath.

  • Browser-based authoring through oXygen Web Author with WYSIWYM editing and a toggle to native XML.
  • Desktop authoring through oXygen XML Editor, XMetaL, and Arbortext with check-in and check-out.
  • Real-time schema enforcement against DITA, custom XML schemas, DTDs, and Schematron rules.
  • Rich text tools mapped to the underlying schema so formatting always produces valid markup.
  • Content-aware search to find and reuse existing components from inside the editor.
  • Multi-language spell check with extensible custom dictionaries.

2. Content reuse and modularity

Every piece of content is a Managed Object stored once and referenced everywhere it is used.

  • Centralized repository where each object carries a unique RSuite ID and full metadata.
  • Create once, reuse everywhere through references rather than copies, so a source edit propagates to every assembly.
  • Granular reuse at the element, paragraph, and section level via DITA conref, conkeyref, and keyref.
  • Conditional reuse through DITAVAL profiling on attributes such as audience, product, or platform.
  • Where-used visibility through a Referenced By view and snapshot dependency maps.

3. Version control and history

RSuite tracks every change at the object level with a complete, auditable history.

  • Explicit check-in and check-out locking so only one author edits a component at a time.
  • Full version history with major and minor revisions, author, timestamp, and change comments.
  • Schema-aware XML compare and merge that highlights structural and textual differences.
  • Branching through snapshots that freeze a complete set of component versions for a release.
  • Rollback of individual components or entire documents to any prior version.
  • Restore of deleted content from the orphan and trash views before permanent purge.

4. Content assembly

Modular components are assembled into deliverables through a structured map view.

  • Map Editor for building and managing DITA maps and bookmaps.
  • Drag-and-drop assembly of topics, files, and references from the repository.
  • Snapshots that pin the exact component versions used in a given build for repeatable output.

5. Review and collaboration

Internal and external stakeholders review content without needing an authoring license.

  • BPMN-based review and approval workflows, both parallel and sequential, with a full audit trail.
  • RSuite Review, a browser app for external reviewers with SSO access, in-context annotation, and threaded comments.
  • Read-only review snapshots so reviewers annotate without altering the source content.
  • Version-specific approval statuses such as approved or approved with reservations.

6. Workflow automation

Content moves through authoring, review, and publishing on configurable, automated paths.

  • Activiti BPMN 2.0 workflow engine with decision logic, timers, and automated service tasks.
  • Multiple initiation methods: UI actions, scheduled jobs, hot folders, and REST API calls.
  • Automated email and in-app notifications on assignment, status change, and completion.
  • Triage and status dashboards for assigning, prioritizing, and tracking work.
  • Scheduled, on-demand, and workflow-triggered publishing with detailed job logs.

7. Multi-format publishing

A single source produces every output format the audience needs.

  • Single-source multi-output publishing through DITA-OT, TopLeaf, and Congility.
  • Conditional publishing that includes or excludes content by audience, product, or version via DITAVAL.
  • Stylesheet and branding management, with different brands driven by different TopLeaf stylesheets stored as Managed Objects.
  • Accessible PDF output for WCAG, Section 508, and European Accessibility Act requirements.

9. Security and access

Access is enforced at the component level and inherited from enterprise identity.

  • Role-based access control at the folder and individual component level on a least-privilege model.
  • SAML 2.0 single sign-on, LDAPS, ADFS, and Microsoft Entra ID, with MFA through the SSO provider.
  • Exportable audit logs capturing check-in, check-out, metadata changes, deletes, and uploads.
  • Single-tenant isolation on dedicated infrastructure.

10. AI and machine learning

AI runs over your content inside your boundary, never outside it.

  • Semantic search powered by a machine learning data service.
  • RSuiteAI, a generative AI plug-in that creates structured content from your own RSuite repository.
  • PoolParty integration for AI-driven taxonomy and ontology management, including semantic repository and vector database support for agentic AI workflows.
  • Natural language processing, semantic search, and generative AI tool integrations.
  • oXygen AI plug-ins for authoring teams.
  • All models are trained only on your content, and nothing is pushed outside your firewall.

11. Integration and extensibility

RSuite connects to the systems around it through standard APIs.

  • REST APIs in XML and JSON to move content in and out and to trigger workflows from external systems.
  • Integration with PLMs, ERPs, and other enterprise systems through APIs and workflow handlers.
  • Plug-in architecture where client-specific configuration is captured as a plug-in, so upgrades do not disturb it.
  • Translation connectors (XTM Cloud, WordBee) and ingest via SFTP, HTTPS, and API.

12. Deployment and operations

RSuite runs where the organization needs it, with production and non-production environments.

  • SaaS on AWS or Azure (single-tenant) or on-premises deployment.
  • Separate Production and Non-Production environments.
  • Monitoring through Zabbix and AWS CloudWatch.
  • 99.5% availability SLA with automated AWS failover and encrypted backups.

13. Where RSuite differs

Two capability differences matter most when comparing RSuite to other CCMS platforms.

  • Multi-schema, non-DITA management. RSuite manages DITA and non-DITA content (JATS, NISO-STS, BITS, S1000D, custom XML) in one repository, rather than requiring all content to be DITA.
  • Client data ownership. All source and transformed content is the client's property and is exportable at any time, with no extraction barrier on exit.

Walk through these capabilities against your
own content operation.

Book a technical assessment
Request a demo