FrameMaker is a long-document processor. Where PageMaker (Cart 003) was built to lay out a magazine page, FrameMaker was built to assemble a two-thousand-page Boeing 777 maintenance manual. PageMaker came up on the Macintosh; FrameMaker came up on the Sun Microsystems demoware circuit. The philosophy was opposite from the start.

PageMaker imagined the page. FrameMaker imagined the structure. In FrameMaker every paragraph carries a tag (Heading1, Body, Caption, BlockQuote, Code) and the tag carries the formatting. Edit a tag's definition once and a thousand paragraphs re-format. Insert a heading and the TOC updates. Move a chapter and every cross-reference to it stays correct. This is structured documents, the line every word processor since has tried to walk and mostly missed.

Frame Technology was founded in 1986 by four people. David Murray designed the UI and shipped a great deal of the code. Charles Corfield, a Cambridge mathematician detoured into a Columbia astrophysics PhD, had written the original prototype on a Sun-2 because no WYSIWYG document editor existed for Unix. Steve Kirsch had the money, having founded Mouse Systems. Vickie Blakeslee ran operations.

The four came together because Sun Microsystems salesmen had been carrying Corfield's prototype around as demoware for the Sun workstation — Sun needed commercial software to show, FrameMaker happened to exist. Kirsch saw the demo and the rest is corporate genealogy: FrameMaker became one of the most ported programs of the late 1980s — thirteen Unix platforms at its peak — and Adobe bought the company in October 1995 for $566 million.

FROM MURRAY stamps the cartridge because the chrome you see here is his.

NeXTSTEP 0.9 was a pre-release build of Steve Jobs' new operating system, shipping on the Cube and the Slab. The Cube cost $6,500. The OS came on a 256 MB magneto-optical disk that took fifteen seconds to spin up. The display was a MegaPixel monitor — 1120 by 832, two-bit grayscale, ninety-two dots per inch, antialiased Display PostScript fonts. It looked, in 1989, like the future, because it was.

NeXTSTEP 0.9 shipped with a pre-alpha demo of FrameMaker 2.0 included on the system disk. This is the version this cartridge honors. There was no shipping FrameMaker 2.0 yet — the demo predated the released Mac version by a year — but it was the version that proved structured documents could be done on a workstation with the chrome we still imagine when we imagine 1989.

The NeXT and AIX builds of FrameMaker used Adobe's Display PostScript, an extension of the PostScript printing language that rendered fonts and graphics on the screen using the same drawing model the LaserWriter used on paper. WYSIWYG, finally, meant actually what-you-see-is-what-you-get — the screen rendered Helvetica and Times using the same outline data the printer would.

Every other Unix port of FrameMaker — Sun OpenWindows, IBM AIX X/Motif, HP-UX — used X11 with Motif, which meant bitmap fonts at low resolutions. The NeXT version was the version where the document on screen looked like the document that would print. This is why the cartridge honors NeXT specifically.

The foundational mechanic. Every paragraph in a FrameMaker document belongs to a paragraph tag. The tag carries the formatting — font, size, weight, indent, spacing above and below, the works. The paragraph carries only the text and a pointer to the tag.

Edit the tag once and every paragraph carrying it re-styles. This is the inverse of every word processor since: where Microsoft Word stores formatting on the paragraph and offers tags as an afterthought, FrameMaker stores formatting on the tag and treats the paragraph as a pointer to it. The implications are profound. Restyle a thousand-page book in five seconds. Translate a tag's definition into French and the formatting flips locales without touching content. Re-target a manual from print to web by swapping the catalog.

CSS would arrive eight years later, in 1996, and reach the same insight from the other direction.

A FrameMaker cross-reference is a live pointer. Click Insert → Cross-Reference, choose a target paragraph (typically a heading), and a token is placed at the cursor. The token renders as "See [target's title] on page [target's page]." Edit the target's text; the cross-reference re-renders. Move the target to a different page; the page number updates.

This is the same insight as a relational database foreign key. The document is no longer a flat sequence of words. It is a graph. Cross-references are edges. Headings are addressable nodes. Edit the node; the edges follow.

The room implements this for real. Click any paragraph, hit Cross-Ref in the main menu, pick a target heading. A live token appears in the paragraph. Re-tag the target — say, demote a Heading1 to a Body — and the cross-reference now points to a body paragraph rather than a heading. Re-name the target by clicking its text and editing; the cross-reference renames everywhere.

Generate TOC walks the paragraph array, collects every Heading1 and Heading2 paragraph, and writes a new document — TOC.fm — containing entries with leader dots and page numbers. Generate again after editing; the TOC re-builds.

FrameMaker supported many generated lists: List of Figures, List of Tables, Index, Glossary. All worked by the same trick — pick a tag or set of tags, walk the document, emit a parallel document of entries. The catalog of tags drove every generated artifact.

Modern static-site generators (Hugo, Jekyll, Eleventy) re-invent this pattern thirty-five years later, with markdown headings as the catalog and YAML front-matter as the metadata schema.

FrameMaker's native binary format was inscrutable. The Maker Interchange Format (MIF) was the parallel ASCII serialization — every FrameMaker feature representable, human-readable, parseable by scripts. The format had three purposes: round-trip between versions, automation by external tools, and integration with type-setting pipelines.

MIF is the granddaddy of every text-based document format that followed: SGML 1986, HTML 1991, DocBook 1992, XML 1998, Markdown 2004, MDX. The recognition that the document should be readable by both humans and machines came from FrameMaker before the web existed.

Adobe bought Frame Technology in October 1995 for $500 million. FrameMaker 5.1 shipped in 1996 with SGML support; later it ate XML; the structured editor became its own product, FrameMaker+SGML. It stayed the documentation tool of choice for aerospace, pharma, telecom, defense — every industry where a manual was a regulated artifact and a typo could ground a plane.

Adobe killed the Mac version in 2004. Windows remained. As of 2026, FrameMaker is on version 2025, still shipping, still niche, still the right tool if you have a Boeing manual to write.

The cleaner descendant is structured editing in DITA, which carried FrameMaker's tag philosophy into XML, and the long-form Markdown stack (Pandoc, MDBook, Asciidoc), which carried the human-readable interchange principle into the open-source era. The pattern survives. The program that started it does too.

Frame Technology, founded 1986. NeXTSTEP 0.9 ships with FrameMaker 2.0 pre-alpha, April 1989. Adobe acquires October 1995. As of this writing FrameMaker (Adobe FrameMaker 2025, version 17.0) is still in active development.

From THE LITERATURE · CANON / 001B · the theory wing of CLASSICERY. Hear Vannevar Bush on As We May Think read aloud — → track 02 →