Back to home
Platform 4.2 · conditional publishing

One source of content, every manual it should produce

The same packaging machine ships with an FDA manual to the US, an EU manual to Europe, an Arabic manual to the Middle East — and different configurations need different wording. With this platform you maintain one source, and publishing automatically produces each correct variant.

Change one parameter and you end up editing a dozen files — and still miss one? We turn content differences into tags, and publishing filters them automatically: one source, N manuals.

86-second overviewWatch once and get it: how conditions are attached, how expressions are built, how output changes

86-second animated walkthrough with Chinese voice-over. Full written details below.

Why Choose Ray Content Technologies

End-to-end enterprise content management, quoted by project scale, with 420 pages of migration included free.

Technical Architecture

  • Front-end/back-end separation: Vue.js + Node.js + microservices
  • AI integration layer: built-in Oxygen AI engine (with DeepSeek)
  • Content isomorphism: cross-platform reuse of DITA XML/Markdown
  • Multi-tenant architecture: data isolation with resource sharing

AI Capability Matrix

Intelligent content recommendationHigh accuracy
Automated PDF/CSS generationHigh accuracy
Content quality detectionHigh accuracy
Enhanced semantic searchHigh accuracy

Oxygen XML Author vs. Ray Content Platform 4.2

Oxygen XML AuthorRay Content Platform 4.2
PositioningFocused on XML/DITA authoring, editing and quality tools.End-to-end solution covering writing, management, publishing and user feedback.
Core functionsXML/DITA authoring; syntax and standards validation; Enterprise adds AI translation, writing, publishing; Git integration (manual setup).Writing: compliance scoring, terminology extraction, steps-to-video (MP4). Management: GitLab, permissions, terminology DB, dashboard. Publishing: dynamic PDF/HTML, PDF watermark, multilingual MS Word styles. Integration: Oxygen Author client, SSO, PLM workflow.
Limitations / specialNo lifecycle management (feedback, permissions); no dynamic publishing or enterprise PDF customization; third-party tools needed for review and feedback."Ray Content DeepSeek Controller" (AI correction); Enterprise Plus supports Oxygen AI plugin and XMLMindServer.
Recommended forSmall to medium teams focused on XML/DITA writing; works with GitLab etc.Medium to large enterprises needing the full lifecycle (writing, publishing, collaboration, feedback); Enterprise Plus recommended.

Ray Platform Value Proposition

Unique Technology

Dual DITA XML and Markdown engines from a single source: one content base outputs both structured and lightweight formats.

Price Advantage

Pricing is quoted by project scale, with 420 pages of migration included free; contact us for a quote.

Localized Service

24/7 Chinese technical support, response under 1 hour.

Business Value

Accelerated Time-to-Market

Content production cycles reduced by up to 40%.

Improved Content ROI

Maximize content use across channels and markets.

Enhanced Brand Value

Culturally appropriate, high-quality content.

Expanded Global Reach

Localized content that keeps your brand voice.

Real case: one manual, two products

Using a roots vacuum pump manual as the example — one source file, with the publishing condition product=roots pump, the system does three things automatically:

Publishing result

✓ 自动保留(罗茨泵专属)
  • 使用须知
  • 注意事项
  • 产品概述
  • 技术参数
  • 安装要求
  • 维护方法
  • 故障分析表
✗ 自动过滤(螺杆泵专属)
  • VSP80 警告
  • VSP80 产品概述
  • VSP80 技术参数
  • VSP80 安装要求
  • VSP80 维护总则
  • VSP80 故障分析

The same logic applies to your equipment: publish the US edition and European regulatory sections disappear; publish the high-end edition and low-end notes disappear.

Five biggest pain points in pharma packaging

Makers of blister, filling, labelling and cartoning machines — and their suppliers of servo, vacuum and sensor systems.

1. Every machine is customised — so is the manual

Sell the same machine to two customers and the interfaces differ, so the installation section changes.

2. Manuals run to thousands of pages, assembled by hand

One Italian manufacturer has 1,500-page manuals, laid out page by page, with translation managed manually.

3. Every new export market means a new document set

The US needs 21 CFR Part 11, Europe needs GMP Annex 11, the Middle East has its own requirements.

4. One parameter change touches a dozen files

Miss one place and the customer receives the wrong manual.

5. Validation documents must ship alongside

Alongside a thousand-page manual comes validation documentation, stretching delivery timelines.

How it solves it

1. One content source

All differences become tags and conditions — no rebuilt copy for each variant.

2. Automatic filtering at publish time

Choose product, market and configuration; the system keeps what belongs and removes the rest.

3. Change once, everywhere consistent

Edit a term or parameter once and every variant stays in sync.

4. Works with XDocs

When stricter structuring and baseline management are needed, add XDocs 5.4 underneath.

Run the ROI estimate Explore XDocs 5.4

Ready to maintain just one source?

30 minutes with one of your own manuals, and we demonstrate conditional publishing live.

Book a free demo