Choosing between Ironmark and Adobe FrameMaker (XML)

FrameMaker is a mature page-layout and technical publishing tool with an XML authoring mode. Ironmark is browser-native, defense-standards focused, and covers the whole publications lifecycle inside one tool. Different shapes; the fit depends on whether your source-of-truth is structured XML or the page layout itself.

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

At a glance

	Ironmark	Adobe FrameMaker (XML)
Deployment	Browser (any modern). Server-side install. Airgap-safe.	Desktop application (Windows).
Pricing	Per authoring seat, published on the page ($520–$840/seat/year). Only authoring roles consume seats; QA, program manager, admin, viewer, and customer are unlimited.	Adobe subscription per seat (standalone or via Technical Communication Suite), or perpetual license.
Standards focus	S1000D 4.2/5.0/6.0, MIL-STD-40051, MIL-PRF-63029, GEIA-STD-0007	DITA, XML generally; S1000D via third-party plug-ins
Source-of-truth	Structured XML. Layout is generated from stylesheets at publish time.	FM binary or XML round-trip. Layout is authored alongside content.
Publishing	PDF (WeasyPrint / XSL-FO), IETP, IADS. Publish pipeline in the same tool.	PDF native; other formats via publish plug-ins.
Portal + feedback	Branded portal + DA-2028 intake ship with every program.	Separate product or custom build.
Review workflow	Peer review, IPRF, BREX validation in-app.	Adobe review tools or third-party review products.

What stays the same

Your XML content — Ironmark and FrameMaker's XML mode both round-trip DTD/schema-conformant content. No proprietary intermediate.
Structured authoring discipline — tag awareness, schema validation, controlled vocabularies.
Standard PDF as an output — both produce PDF. The pipelines differ.

What changes

You gain

The lifecycle in one tool. Review, applicability, parts, BREX, publish, portal delivery, feedback triage — all in-app. No FrameMaker + separate CMS + separate portal.
Browser-native. No Windows-only install. Anyone with credentials is an author.
Defense standards support out of the box. S1000D, 40051, 63029 with dedicated widgets, BREX, IADS — not add-on packages.
Published pricing. Per-seat, on the page.

You give up

Page-layout muscle. FrameMaker's whole discipline is print layout. If your source-of-truth is a page (not structured XML), that's a category mismatch — FrameMaker is the right tool.
Adobe ecosystem integration. Illustrator, Photoshop, InDesign, Bridge — Ironmark doesn't slot in alongside those the way FrameMaker does.
DITA-first workflows. Ironmark focuses on defense standards. DITA isn't in the current SDM set.

If your primary need is producing well-structured documents and high-quality publications, FrameMaker remains an excellent choice. If your program also needs repository management, review workflows, controlled distribution, customer delivery, applicability management, and cross-standard traceability, Ironmark was designed to provide those capabilities within a single platform.

Using both

If FrameMaker's XML mode already fits how your authors work, the Ironmark Desktop Launcher lets them keep FrameMaker in front of them while Ironmark handles the CSDB, review, publishing, and delivery around it. From the Ironmark web UI, Open in Desktop Editor checks the document out, opens the XML in FrameMaker (structured application configured to your DTD), flushes each save to the server, and checks in when FrameMaker closes.

Note: the round-trip is XML in / XML out. If your source-of-truth is a FrameMaker binary .fm or you rely on layout authored inside FrameMaker for the final print output, only the XML side survives the round-trip — layout still comes from Ironmark's publish stylesheets. Programs that already treat FrameMaker's XML mode as authoritative see the smoothest fit.

Migrating in

XML content from FrameMaker XML mode imports as-is if it's DTD/schema-conformant. Drag-drop files or import as an IADS package.
Content authored in the binary format needs XML export from FrameMaker first. Adobe documents the round-trip.
Publish stylesheets won't come across — Ironmark's publish pipeline uses WeasyPrint CSS or XSL-FO. Rebuild against the SDM's shipped stylesheets and layer per-project overrides.

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 Adobe FrameMaker (XML)

At a glance

What stays the same

What changes

You gain

You give up

Using both

Migrating in

Related