Tag: Adobe RoboHelp

Dr. Corfield pointed out that the first content management problems started to occur as a result, and those issues included the need for internal references, such as footnotes, indexes, cross references,  and markers. The power of Framemaker’s ability to create indices to update long documentation was–and still is–more powerful than Microsoft Word even today. He also added the ability to refer to external factors like external references and hypertext.

Framemaker created the ability to manage variants of a single document, leading to what we now think of as single source publishing. Variants would be such objects as variables, conditional text, frozen pagination and change-pages. This yielded a new dilemma. As Corfield posed it, do you send out fully changed documentation or only the pages that were changed, especially with super large documents? The problem would be that with big documents, people would say, “Well, what changed?” Corfield pointed out the Boeing 777 project in 1990s needed IMMENSE documentation, so they needed to use retrievable databases. The Boeing 777 project solution was to use SGML (the predecessor of HTML and XML). This project made it the first “web” delivery of documentation. The Boeing 777 project used Framemaker with SGML, using HTML, XML, DITA as well as “structure.” Framemaker provided a server-based generation of documentation.

Shifting his talk a bit, Dr. Corfield started to talk about Framemaker’s impact today.  He pointed out that the original retina display was actually paper! Sophisticated layouts had to be used to maximize the user-experience. The computer came along later to expand on that concept. Displays started out with 72 dpi (dots per inch) displays, which led to crude layouts. Now, retina display is available at 300 dpi, but we need to re-learn what we did on paper yet also include dynamic content from high resolution video and images.  Corfield pointed out that there has been a proliferation of platforms. We have desktop, laptops, smartphones, and tablets that use different platforms such as Unix, DOS, and MacOS (for PC and Mac products respectively) that need different outputs. Technical writing, therefore, is directly impacted by all the different displays and platforms in relation to  document authoring. It is a requirement to produce structure and rich layouts for the output. Documentation needs to be able to support dynamic content (video, animation, etc.) and it needs to manage content for consumption on multiple platforms. The good news is that Framemaker can do all that! While there are other tools out there that can also deliver different kinds of output, many still struggle to manage and deliver to these needs the same way that Framemaker can now. Dr. Corfield is not part of Adobe anymore, nor is he part of today’s Framemaker product, but he seems happy with where the product has gone since he left it in Adobe’s hands.

(I should note, that while this was a talk sponsored by Adobe, this really wasn’t intended to be a big info-mercial for Framemaker, but rather something that puts the concept of tech comm software into perspective, and it happens to be the product of the sponsor.)

So, where does this tech comm legend think technology is going next? Corfield thinks that going forward, voice is going to have the biggest impact. He felt that screen real estate is full, and that much of the visual is about adding a new widget, then removing a widget. Voice, he continued, eliminates how keyboard shortcuts are remembered. How many keyboard shortcuts does the average user know? Touch screens are a slow way to perform data entry. The impact of voice will be the ability to use visual tips, and have voice act as a virtual keyboard. Voice will be impacting product documentation, allowing it to understand how existing workflows can be modified. Corfield’s prediction is that Framemaker, along with other software out on the market, will “assimilate” voice, just like everything else.

Since leaving Framemaker, Corfield has been working with a product called SayIt, using voice as part of workflow optimization, and emphasized that voice truly is the next big thing (you heard it here, folks!). When asked about the use of voice technology in practical office use, Corfield responded that push-to-talk technology helps prevent cross-talk in an office environment. He also pointed out that with voice, there are no ergonomic issues as there are with carpel tunnel syndrome using a mouse and keyboard. If anything, voice will be more helpful!

On that note, the presentation was over. The long and winding road had ended, but has lead to new doors to be opened. 😉

I really enjoyed listening to the history and the thought process behind Framemaker that Dr. Corfield presented. Everything he mentioned made total sense, and it’s to his credit that he had the foresight to think about the next steps in word processing to create a useful tool like Framemaker to help technical writers meet the needs of documentation in the digital age.

There is a certain aura around creative, imaginative and smart people who make huge differences in our lives, whether it’s in music like McCartney, or tech comm software like Corfield. You can’t help but be awed in their presence, and yet understand that they are generally humble people.  When you have a chance to meet an individual like that, you want the opportunity to capture the moment–like have a picture of yourself and that person to prove that it happened. I was much too shy to ask Dr. Corfield for a photo with me to be honest. I felt awkward asking, so I didn’t. Heck, I felt awkward asking about his potential Twitter name! Even so, I’m glad I had the opportunity to meet him and hear him speak.  He’s got my vote as a candidate for the Tech Comm Hall of Fame someday.

(And, Dr. Corfield, if you do ever read this, please feel free to correct anything written here or add any clarification or other commentary below!)