Untitled Document

The room you're in is a reconstruction of an early WYSIWYG HTML editor shipped December 1997, the first Macromedia release that wasn't a CD-ROM authoring tool, the first one to credibly tell a working web designer: don't write the HTML by hand, but don't suffer FrontPage either. This is not that program. This is a browser in 2026 emulating a 1997 Macintosh emulating a typesetting box, and the chrome you're reading this through is Mac OS 8 platinum, faithfully or not, through forty pixels of stacked nostalgia.

What works in this room. The Objects palette on the left inserts images, tables, horizontal rules, links, anchors, form fields, layers, and rollovers into the visible canvas. The Properties inspector at the bottom is context-sensitive — click an image, the inspector becomes an image inspector; click a table, a table inspector; click a link, a link inspector; and so on. The HTML Source window mirrors the canvas in real time, and edits in either pane propagate to the other — this was the killer feature of Dreamweaver 1.0, the thing that justified the box. Use the Rooms menu at the top right to switch cartridges.

Web design in 1997 was a craft of writing HTML in a text editor. BBEdit, HomeSite, SimpleText, Notepad. You learned the tag list, you learned what nested inside what, you learned the alignment hacks for centering things inside table cells. The browser wars were on — Netscape 4, Internet Explorer 4 — and what worked in one might not work in the other, so you tested twice, you wrote ugly conditional layouts, and you joined a mailing list.

There were WYSIWYG tools, but they were the punchline. Microsoft FrontPage rewrote your handwritten markup into Microsoft markup. Adobe PageMill output bloated tag soup. NetObjects Fusion treated the page as a layered design composition that exported as nested tables. None of them were what a designer who could already write HTML wanted. They were what a designer who couldn't write HTML had to settle for.

Dreamweaver's pitch was a single phrase: Roundtrip HTML. The visual canvas did not own your markup. You could write the HTML by hand in a text editor, open it in Dreamweaver, edit it visually, save it back to disk — and the source would still be your source. Whitespace preserved. Comments preserved. Custom tags untouched. Hand-written JavaScript not mangled.

This was unprecedented. Every other WYSIWYG tool rewrote your markup on open, claiming the canon for itself. Dreamweaver said the source was canonical and the visual view was a projection. The source stayed yours.

In this room, edits on either side of the canvas/source pair propagate to the other automatically. Type in the HTML Source window — the visible page updates. Type in the canvas — the source updates. The synchronization is the demo.

Kevin Lynch joined Macromedia in 1996 from General Magic, having earlier been an architect on the first Mac release of FrameMaker at Frame Technology. At Macromedia he led the team that built Dreamweaver into the product that shipped December 1997. He later led the Flash Player team, went to Adobe in the 2005 acquisition as chief software architect, was promoted to CTO in 2008, then left Adobe in March 2013 to lead a small project at Apple called the Watch. The throughline is software for designers, picked up and put down by the right person at the right inflection.

Macromedia in 1997 was the company that made Director and Flash. Adding a static-HTML editor to that catalog was a strategic bet: web design was about to stop being a programming task and start being a design task. The bet paid off. Within three years Dreamweaver had taken the high end of the market that FrontPage had taken the low end of.

The three palettes that made Dreamweaver Dreamweaver were the Objects palette, the Properties inspector, and the Behaviors panel. The Objects palette inserted HTML elements. The Properties inspector made selected elements editable in a context-sensitive panel — image properties, table properties, link properties, depending on what you'd clicked. The Behaviors panel attached prewritten JavaScript snippets to elements.

The Behaviors panel was the breakthrough. Swap Image, Open Browser Window, Go to URL, Set Status Bar Text, Preload Images. JavaScript a designer hadn't written, attached to elements a designer had drawn. The first generation of rollovers — that thing every navigation bar did from 1998 to 2003 — was overwhelmingly Dreamweaver's Swap Image behavior, attached via the Behaviors panel by people who never read a line of the resulting code.

The other thing Dreamweaver 1.0 shipped with was Layers. Absolutely-positioned div elements that you could drag around the page in the visual canvas. Modify the position, the size, the z-index, the background color — the inspector gave you sliders for all of it. The result, served through Netscape 4 or IE 4 with a sprinkle of positioning via CSS, was the era's idea of Dynamic HTML.

DHTML promised drag-and-drop interactivity in the browser without plugins, in a year when Flash was still finding its audience. The catch: every browser implemented absolute positioning slightly differently. Netscape 4's layers were not Internet Explorer 4's layers, and the cross-browser code Dreamweaver wrote for you was, frankly, what you wanted Dreamweaver writing for you. Hand-rolling it was unthinkable.

Microsoft FrontPage 97 had shipped a year before Dreamweaver. Adobe PageMill had been on the market since 1995. NetObjects Fusion had a cult following among small-shop design firms. The category was crowded and the winners weren't obvious.

Dreamweaver won on three things: it didn't rewrite your markup, it ran on Mac and Windows with parity, and it shipped with extensions. The behaviors panel, the object palette, the inspectors — all of it was driven by JavaScript files that a third party could write. By 1999 there was a thriving ecosystem of Dreamweaver extensions written by people who weren't Macromedia. PageMill never had that. FrontPage didn't believe in it. The web was won by the tool that treated the web as something to extend, not as something to package.

Version 2 in 1998 added Templates and Library items, the first time a web tool let you change a header once and propagate the change to a hundred pages. Version 3, 1999. Version 4, 2000 — and alongside it Dreamweaver UltraDev, a parallel sku that added ColdFusion / ASP / JSP / PHP backends. UltraDev folded back into Dreamweaver proper with the MX release in 2002, by which point the product had eaten the entire mid-market. The 2005 Adobe acquisition merged Macromedia into Adobe, and Dreamweaver became part of the Creative Suite.

The product still ships in 2026, on a different code base, under Adobe Creative Cloud. The category it invented has narrowed — most professional web design moved to React and Figma a decade ago — but Dreamweaver still ships, because the small business owner who built their site in 2001 is still maintaining it, and the tool they built it in is the tool they trust.

The roundtrip HTML promise is the part that stayed. Every WYSIWYG tool that came after — VS Code with extensions, Sublime + a live preview, Adobe Brackets, the marketing-page builders, the no-code platforms — has had to decide what to do about the relationship between the visible page and the source of the page, and Dreamweaver's answer (the source is canonical, the visual view is a projection, edits in either go to the other) is the answer that most of them landed on.

What didn't stay was the unified product. Modern web design is six tools — Figma for design, VS Code for source, GitHub for versions, Netlify for hosting, Webflow for handoff, Chrome devtools for debug — and the assumption that one application could be all of them in one window is gone. Dreamweaver tried to be the only window. For one brief stretch between 1997 and 2003 it almost was.

The roundtrip itself wasn't new. Seven years earlier in WorldWideWeb (CART 014, 1990) the browser already was the editor — that NeXTSTEP application was built in Interface Builder (CART 015, 1988), the room next door, where the window-and-edit pattern itself was first archivable. The web came with editing already attached. Mosaic dropped it. Dreamweaver tried to put it back.

From THE LITERATURE · CANON / 001B · the theory wing of CLASSICERY. Hear Vannevar Bush on As We May Think read aloud — the 1945 essay that imagined the desk that browsed and edited a linked corpus, decades before any of this. → track 02 →