Field Guide
FrameMaker to DITA (or S1000D): Converting the Desktop Era
The Estate
Better Than Word, Messier Than SGML
On the conversion-difficulty spectrum, FrameMaker sits in the instructive middle. Validated SGML converts on rails; Word estates carry twenty years of formatting anarchy; Frame libraries carry discipline without enforcement. Structured Frame — authored against an EDD — converts nearly as predictably as SGML. Unstructured Frame, the wide middle, runs on paragraph tags that carry real signal when the template held: automation gets far, and the traps are at least characteristic — meaning hidden in overrides, anchored frames and text insets, hand-formatted tables, conditional text used creatively. Frame is the template-as-standard era at its best behaved — and its best behaved is still not a content model.
The Method
Audit the Template, Sample the Worst
The playbook is our standard one with a Frame-specific opening move: a template-consistency audit before anything else, because tag discipline is the whole ballgame — the same book count converts at wildly different cost depending on whether “Step” always meant step. Then the representative sample — oldest books, worst tables, inset-heavy chapters — through the real pipeline, yielding the automation rate, the exception catalog, and per-book effort. The cost drivers behave exactly as they do everywhere else; Frame just concentrates them in known places.
Target selection follows the standard logic: contracts choose S1000D; product-family reuse argues DITA (the most common Frame destination); and the convert-or-ingest split still applies — the settled tail of a Frame library can be published as-is through a delivery platform while the living families convert. The consistent good news: teams that chose FrameMaker two decades ago were choosing discipline. That choice is still paying dividends — a conversion project is where it cashes out.
FAQ
Questions We Hear
Why is so much legacy content in FrameMaker?
Because for two decades it was the serious choice. FrameMaker handled thousand-page books when Word crumbled, offered real paragraph-tag discipline and structured (SGML/XML) editions, and became the default for aerospace, industrial, and software manuals through the 1990s and 2000s. Organizations that chose it were choosing structure-adjacent discipline — which is why their libraries now convert better than Word estates, and why so many of them still exist: the tool outlived the era, and the content outlived the tool's centrality.
How well does FrameMaker convert?
It depends entirely on which FrameMaker you have. Structured Frame — authored against an EDD with real element structure — converts nearly as predictably as SGML: the mapping is mechanical and testable. Unstructured Frame is the wide middle: paragraph tags carry real signal (a disciplined template means 'Heading2' and 'Step' actually mean something), so automated conversion gets far — but the traps are characteristic: meaning carried in overrides, anchored frames and text insets, cross-reference formats, conditional text used creatively, and tables formatted by hand. The sample tells you which library you own.
DITA or S1000D as the target?
The same decision logic as everywhere else: the contract chooses S1000D (aerospace and defense deliverables under the specification and its business rules); product-family reuse across overlapping deliverables argues DITA; and a genuinely book-shaped single publication might argue staying simplest. FrameMaker libraries most often move to DITA — industrial and software content with reuse needs — but Frame-to-S1000D is routine on programs whose contracts caught up with their libraries. Pick the target before the pipeline: the mapping decisions differ meaningfully.
What does the sample-first method look like for Frame?
Same discipline as our SGML playbook, tuned to Frame's traps: a representative slice — the oldest books, the worst tables, the inset-heavy chapters, the conditional-text tangles — through the real pipeline before anyone commits. Out come the automation rate, the exception catalog (Frame's cluster in overrides, insets, and tables), and honest per-book effort for the remainder. Plus one Frame-specific pre-step that pays outsized returns: a template-consistency audit, because the conversion cost of a disciplined template and a drifted one differ by multiples.
Get In Touch
A Frame Library With a Future?
Send us a representative slice — worst tables included — and we'll return the template audit and the three numbers that make your conversion budget real.