What does not change
Your CCMS stays the master. The platform is designed to read from it, not to replace it, and your team keeps approval.
For technical documentation
Your manuals become the source. Nothing extra to write.
Technical documentation delivers the content and the access. IFUto.ai is designed to connect to your CCMS or support portal, read what you already publish, and keep every approved word under your control.
In development The platform is in development. This page describes its design.
01 · Your role
You own the source. Others need the answers.
Your team writes precise, approved content in DITA, iiRDS, XML or PDF. Marketing and support need that same content as answers, pages and video, in every language.
Rewriting it for each channel takes time and creates versions that drift apart. The platform is designed to publish from your source instead.
02 · What it is designed to do
Your content goes further, and stays yours
No new authoring
Starts from what you publish today: DITA maps, iiRDS packages, XML, HTML or PDF.
Connects to your systems
Designed to connect to your CCMS and support portals, so updates flow from the source you already maintain.
You approve
Nothing is published without approval. A re-import updates only the topics that changed, and every change is recorded.
Safety text unchanged
Warnings, cautions, torque values and part numbers stay exactly as approved.
03 · What we need from you
Content and access, not a new project
| You provide | What it is used for |
|---|---|
| Source content | One manual to start, in the format you already use. |
| Access | Read access to your CCMS or portal, or a regular export: your choice. |
| Review | A reviewer who approves the first topic pages and later changes. |
| Terminology | Your term lists and style rules, if you have them. |
Marketing and customer support fund the channels they use. Your team supplies the source and keeps approval.
04 · In your terms
Built on the standards you work with
Structure carried through
Topics, metadata and conditions from DITA and iiRDS are designed to carry through to pages, video and the MCP tools.
Versioned per release and language
Each topic keeps its version, its languages and its approval history, so you can show what was published and when.
The technical overview shows the content model, the import and the review flow in detail.
05 · Who does what
Marketing and support use it. Technical documentation supplies it.
One platform, three teams. Each keeps its own role.
Marketing
Owns visibility: how the brand answers in search and in AI assistants, in every language and on video.
Customer support
Owns self-service: one approved answer in the help centre, in AI assistants and in your own support tools.
Technical documentation
Owns the source: delivers the content and the access, and approves what is published.
What it means for marketing What it means for customer support
06 · Next step
Start with one manual
Send one manual in the format you already use. We map it into topics with you, and you approve the first pages before anything is published.