In my time as a technical writer, it seems that the authoring of technical information has gone full circle:
- 1985: Authored my first-ever deliverable in the vi editor with nroff markups.
- 1987-1990: IBM’s Bookmaster, which grew from ISIL, again a markup language.
- 1990-1992: FrameMaker on Sun! And some Microsoft Word (!) for shorter documents.
- 1993-1995: Interleaf. I’ve tried to forget Interleaf.
- 1995-2000: Microsoft Word and RoboHelp (WinHelp, no less). And FrameMaker, now on Windows.
- 2000-2005: RoboHelp (HTMLHelp) and, alas, Microsoft Word.
- 2005-2009: RoboHelp, Microsoft Word.
- Today: DITA markup with the oXygen editor. I like oXygen; I still miss the vi editor. Even so many years later, I find myself trying to use vi commands in word processors and other editors.
All that said, I love working in markup languages. WYSIWYG is good for many things, but I think it gets in the way of much quality technical writing. With markup languages, we are encouraged to focus on the meaning of the content and leave the appearance of that content to style files, .css, and other technology.