Choosing between Ironmark and desktop XML editors

Editor vs platform.

Oxygen, XMLSpy, MadCap, and other desktop XML editors are strong tools for authoring structured content — that's the editor role. Ironmark is a different category: a platform where the editor is one of nine stages, alongside review, applicability, parts, publishing, delivery, feedback, compliance, and program reporting. Different tool, different job.

Authors keep the editor they know. Programs gain workflow, review, publishing, traceability, and delivery.

At a glance

	Ironmark	Desktop XML editors (Oxygen, XMLSpy, MadCap)
Category	Technical publications platform	XML authoring / editing tool
Deployment	Browser. Server-side install. Airgap-safe.	Desktop application per author, per OS.
Editing surface	Structured + visual editors, schema-aware widgets.	Deep editing controls, mature XPath/XSLT tooling, macros.
Review	In-app peer review, IPRF, BREX validation, review queue.	Track-changes and comments; external tools for structured review.
Publishing	Built-in pipeline: PDF, IETP, IADS.	Transform via XSLT to your own pipeline.
Delivery + feedback	Branded portal + DA-2028 intake ship with every program.	Separate systems.
Program reporting	PM dashboard, per-author health, coverage summaries.	External spreadsheet / BI tools.
Pricing	Per seat, published on the page.	Per seat, published; add-ons and modules vary.

What stays the same

Structured XML source. The source stays schema-conformant XML on disk. No proprietary container, no import step to get your content back out.
Schema and BREX validation. Ironmark validates against the project's own schema and BREX rules on demand, whichever editor produced the XML.
Standard output formats. IADS packages, S1000D-shaped PDFs, IETPs — all industry-standard.

What changes

You gain

One integrated tool instead of an editor plus a chain of separate systems for review, publish, delivery, and reporting.
Browser access — no per-author OS install or license lock-in to a specific machine.
Portal + feedback as a first-class surface, not a custom-built downstream project.
Cross-DM search, applicability wizard, parts browser, PM dashboard — surfaces that live outside the editor by definition.

You give up

The deepest editing controls. Mature desktop editors have decades of refinement in XPath tooling, refactoring, and macro systems. Ironmark's editor covers the common shapes; specialists doing heavy XPath/XSLT work may want a desktop tool alongside.
DITA and non-defense schemas. Ironmark focuses on defense standards.
Custom-pipeline flexibility. If your publish flow is a bespoke XSLT chain, Ironmark's opinion (WeasyPrint or XSL-FO) may not be your opinion.

Desktop XML editors remain excellent tools for standards development, schema design, stylesheet work, and advanced XML engineering. Ironmark is designed for the day-to-day management of technical publications programs where authoring is only one part of the workflow.

Using both

Many teams keep a desktop XML editor for a specialist author or two while running the program on Ironmark for the review, publish, and delivery flow. Since both work on the same XML source, this is straightforward — files edited in Oxygen check in through Ironmark's structured editor without conversion.

The Ironmark Desktop Launcher makes the round-trip a single click. From the Ironmark web editor, Open in Desktop Editor hands the document off to the launcher (a small Windows helper installed to the user profile) which checks it out, opens it in the configured editor, flushes each save to the server as a working-copy update, and performs the final check-in when the editor closes. A companion Continue in Desktop button resumes a checkout that an author left open from a previous session.

System administrators can hide the download entirely or force per-user API-token authentication instead of browser-minted session tokens when program policy calls for it. See How-to: edit in your desktop editor for the install steps and the auth-mode picker.

Ironmark isn't designed to replace every XML tool. It's designed to reduce the number of separate systems required to author, manage, publish, and deliver technical publications.

← Back to migration guides

Choosing between Ironmark and desktop XML editors

At a glance

What stays the same

What changes

You gain

You give up

Using both

Related