Framemaker – Page 3 – TechCommGeekMom

A New Year–A New Adobe Technical Communication Suite – PREVIEW

Posted on January 14, 2014January 14, 2014 by TechCommGeekMom

TCS5-Ball-Drop — The Times Square New Year’s ball drop has landed…it’s a new Adobe Technical Communication Suite!

As of TODAY, Adobe is releasing five new tools for technical communication professionals everywhere! Technical Communication Suite 5.0 (TCS5), FrameMaker 12 (FM12), FrameMaker XML Author 12 (FMXA 12) and RoboHelp 11 (RH11), and FrameMaker Publishing Server 12 (FMPS12) are now available. It’s been about eighteen months or so since the last big Adobe tech comm release, so you can imagine there are some new and enhanced features included.

I was privileged to be among a group of tech comm professionals who were invited to get a preview of the products before their release, and I have to say, there were so many new and improved features that it was difficult to squeeze all the information into one press conference! But I’m going to give you the highlights, and I’m sure you’re going to find that there’s something new for you.

In the last release of TCS, namely TCS4, there were several big overhauls of the product, namely that the Technical Communications Suite concentrated on providing tools that supported structured authoring, integrated interactive content, and could support the creation of content for mobile devices while providing searchable, personalized, socially enabled content in a way that would yield bigger results with less resources. It was a major step to enhance these tools, especially in regards to adding mobile and interactive abilities to content. Adobe has continued to build on those major changes with the new features in version 5.0.

The foundation of the Tech Comm Suite has always been FrameMaker and RoboHelp. With the release of TCS5, FrameMaker 12 and RoboHelp 11 have been released with big enhancements that appear to concentrate on making these tools more user-friendly and efficient for the technical writers using them.

FM12_boxshot_2014 — Image courtesy of Adobe.

For FM12, the first obvious enhancement is the interface. Adobe has improved the user interface to include colored icons and larger icons that look cleaner and sharper in HD. If you like things “old school” in the original smaller, monochromatic colors, that choice is still available as well. There is also more flexibility in customizing your interface. A new “pod” allows the user to access all the currently opened files in one place, from which you can save and close multiple files at one time, while still viewing the unsaved files. There are also enhanced abilities to drag-and-drop to empty areas of the interface, close pods or panels more easily, double-click on empty areas to minimize or expand pods, and searching capabilities have been expanded. These seem like minor details, but when using a product as often as many technical writers use FrameMaker, these finer details can make a big difference! FM12 includes three samples of unstructured content and one DITA-based content sample with the product.

FM12 is not all about a new façade. Adobe has enriched the authoring process with new capabilities. The first thing that caught my attention is that FM12 can generate QR codes now! They can be created for URLs, SMS texts, emails, or to initiate phone calls. QR codes are taking over these days, so it’s great that these can be both created and integrated into FM documentation. Background color enhancements allow uniform height background color and options to specify paragraph boxes. The addition of a new customer-requested feature is the support regular expression coding.

Single-sourcing has been a hot topic in the last few years, and this has been addressed with new enhancements. FM12 gives users a new way to work with conditional text, by using a new conditional tag pod which provides check-box mechanisms with multiple conditions to allow the user to do more complex filtering with conditional text enhancements. It truly simplifies the entire process, that even a newbie should be able to figure it out easily.

Productivity enhancements have also been included in FM12. A searchable smart catalog function allows the user to filter choices based on the valid choices available and phrase typed by the user, while the user can continue to use the keyboard shortcuts as before. There is also a new capability to open all files from the user’s last session in one click, including the last documents and pages in focus, workspaces such as pods, panels and palettes, among others.

Adobe has also taken care to add great collaboration enhancements in FrameMaker. Native connections to any webdev content management system (CMS), such as Documentum, SharePoint, and Adobe CQ are available. Users can now view entire CMS tree layouts, and can access several key CMS functions, such as checking out documents, editing documents, and searching within document, all from FM12. PDF review commenting has been made more flexible. The most proactive steps towards subject matter expert (SME) reviews is that reviews can be done on PDF reader apps on mobile devices, and can also be used on those same devices using cloud technology such as Dropbox for both internal and external reviewers. As mobile devices become more commonplace replacing desktops and laptops, this is a great step forward!

Publishing abilities have gotten a boost on FrameMaker as well. It used to be that if you wanted to create certain types of digital output, such a ePUBs, for FrameMaker content, you would have to export it to RoboHelp, and have RoboHelp publish the document. Now, that step is no longer needed for PDFs, Webhelp, ePUBs, Kindle docs, Microsoft HTML Help, responsive HTML5, or Web help! That’s a big deal, as it allows FM12 to be more efficient by skipping that step of exporting and publishing in RoboHelp. Publishing can also be done through the Web now, too, for multiple users using a FrameMaker server, allowing multiple users to publish simultaneously and automatically to multiple channels and devices. That’s a practical efficiency improvement right there!

FMXA12_boxshot_2014 — Image courtesy of Adobe

With this release, Adobe is introducing a new FrameMaker product for those who don’t need the full version of FM12, but are mostly concerned in having a tool to do structured XML authoring. FrameMaker XML Author is a tool that has been created especially for the structured XML market. Those wanting to use unstructured content will still need to use the full FM12 version. The XML Author is fully standards-compliant for content creation, and supports the most popular XML technology for single-sourcing. It is not FM12 “lite”, but it is a streamlined, easy-to-use version that supports structured authoring without the bulk of the FM12 features that aren’t needed for structured content, yet still integrate-able with the full version of FM12 and available at a lower price. I’m sure that having this tool will be highly beneficial to many companies who are looking for a way to cut costs (it is priced at 40% the price of FM12 “full”) while still reaping the benefits of having a powerful XML authoring tool.

Another customer request that has been granted by Adobe is the integration of MathML, to allow MathML equations to be imported, created, edited, and published with FrameMaker. Adobe is even including 30-day trials of MathFlow (MathML editor from Design Science) with the shipment of FM12 for those who are interested in trying it out. There are several other features that are also included, along with 55 bug fixes, improved performance and launch time for FrameMaker, but I’d end up writing a book at this point!

Of course, with all these big changes to FrameMaker, we can’t forget RoboHelp 11, which also has had a big overhaul.

RH11, like FM12, has a new UI look as well. Based on customer feedback, RH11 has a new color scheme and a more modern interface that looks more pleasing to the eye. It’s a step in the right direction. Adobe has said that further UI improvements are in the works, but this current new UI is the first step in a long overdue makeover for the interface.

The more important feature enhancements with this new release of RoboHelp include advances with HTML5 publishing, printed document enhancements, and collaboration and single-sourcing enhancements.

The HTML5 publishing enhancements are from the perspective that mobile publishing is central, so new single responsive layouts for all devices are available “right out of the box” when downloading RH11. This new single layout feature will work seamlessly across all devices, can be easily customized, will allow for real-time previewing based on the browser size, and can be published with one click. There is a new wizard-based layout editor available to help with this process that shows the added responsive HTML5 output options. You can also preview layouts, and the customization is great because no coding in CSS needs to be done, as you can use the editor instead. To me, this is true single-sourcing creation at its best while simplifying the process! This is a big deal!

Printed documents have not been ignored. Users can now customize headers and footers of printed documents by defining them in the master pages. Headers and footers can also be imported from Word. There is also the ability to specify different headers and footers for the cover, and even and odd pages for different sections of a document. This is great for consistency within branded documentation.

In terms of collaboration and single-source improvements, cloud integration and topic sharing for SMEs has now been included. RH11 now includes a Resource Manager tool that synchronizes folders using Dropbox, Google Drive, or Microsoft SkyDrive as shared locations, and includes filtering for specific folders. This allows the user to manage linked resources within files used in real time across projects and geography.

The Technical Communication Suite 5.0 includes FrameMaker 12 and RoboHelp 11, but it also includes the updated products of Acrobat Pro XI, Captivate 7, and Presenter 9 to complete the Suite. You will notice that Illustrator, which was included in the TCS4 version, is not included. This was a step, Adobe said, to help lower the price. Additionally, from the way I see it, it makes sense, because both Illustrator and Photoshop–another product that used to be included in prior TCS versions–are now affordably available as part of the Adobe Creative Cloud subscription. I know that I personally have a CC subscription, and I’m guessing that many active technical communicators do too, so this saves us from spending twice for the same product, which makes a lot of sense. TCS5, FM12, RH11, FM XML Author, and the FMPS12 will also be available both as a subscription and through perpetual license as well. There is separate pricing for the FM XML Author and FM Publishing Server software.

The updates made to FrameMaker and RoboHelp are extensive, as there are many more features, but I think you get the idea. Adobe is taking steps to try to stay on top of technological changes that have taken root in the past couple of years, such as mobile and cloud technology, and is working to continue to make a more robust and user-friendly products for technical communicators.

My recommendation is that if you are looking to try TCS5 or any of the TC products out, or are interested in upgrading your current TCS package or individual products, click on the Adobe advertisement in the upper right corner of this page, or visit Adobe’s TCS product page for more information.

I hope you find this helpful!

Uncategorized

2013 in review, Part 2

Posted on December 31, 2013 by TechCommGeekMom

The WordPress.com stats helper monkeys prepared a 2013 annual report for this blog.

Here’s an excerpt:

The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 9,600 times in 2013. If it were a concert at Sydney Opera House, it would take about 4 sold-out performances for that many people to see it.

Click here to see the complete report.

Uncategorized

Book Review: 8 Steps to Amazing Webinars by Sharon Burton

Posted on December 5, 2013 by TechCommGeekMom

In less than a week from this writing, I will be doing a new webinar that I was asked to do by one of the STC Special Interest Groups (SIGs). I was really honored to have been asked, and it’s about a topic that I think I know a little something about–blogging. After all, this little webspot has been going strong for about 21 months now.

But in putting this latest webinar together, I realized that while I felt that I could whip something decent together, it’s been a while since I had to craft a webinar presentation. This, in turn, reminded me that I had a promise to fulfull, as I sought out a reference in my personal library written by one of my tech comm knitting buddies. Pulling this reference out reminded me that I’ve been meaning to write this review since last spring, but had been side-tracked several times until now–when I really needed it most.

Sharon Burton’s book, 8 Steps to Amazing Webinars, is a slim volume of only 81 pages (and that’s the end of Appendix B), but it’s loaded with very concise information. 81 pages is all you need! Considering that this is a short and concise how-to book, it shouldn’t have taken me this long to write this! I truly try to read any books that I’m asked to review cover to cover, and this was a quick but highly informative read!

There are several things I like about Sharon’s book. It’s short and to the point, as already mentioned. For busy presenters who have many things to do other than solely doing webinars, this is great resource because she gets straight to the heart of what needs to be done. Additionally, one of the things that I’ve found that Sharon and I have in common with our tech comm perspective is that our views are highly customer service-oriented. Before my life in an IT/tech comm world, I came from a customer service/client services background, so much of her advice on the how and why webinars can be great marketing tools geared towards customers made a lot of sense to me.

Sharon’s eight steps take the reader from the point of understanding what a webinar is, through every step of the process of creating and following-up with the webinar, including choosing presenters, topics, technology needed, advertisting the webinar, and all the other preparation steps to creating the webinar. She even includes pointers on how to set up the presentation slides that are most likely going to be used in the presentation.

As I read the book, I was quickly reminded of the first webinar that I did back in 2012 for Adobe’s Technical Communications group (you can find the link on the right-hand column of this blog). I remember not knowing the first thing about how to put together a webinar. At the time, Maxwell Hoffman, who is one of the evangelists for Adobe TCS, guided and coached me through the process, and it ended up being a great success. Looking back, I would not be surprised if Maxwell was already well-versed in the steps that Sharon outlines in her book, because I’m fairly sure that we followed every single step. When I also look back to the first in-person presentation I did, which lead to a recent webinar on the same topic, I realized that I had followed much of the same steps again, and got a great response as a result. These steps are practically foolproof, so I can assure you that if you follow Sharon’s advice in the book–and much of it is really common sense, you should have success in presenting a webinar.

Sharon’s viewpoint in this book is from a marketing perspective, in that webinars are used to drive people to a brand, increase leads, and provide resources to your customers. And for 99.9% of time, this is a main focus for most people who would read this book. But even for people who are academics, for example, who are not necessarily trying to create a brand, but rather disseminate valuable information, this book is still helpful because it put the reader in the right mind-set to create a virtual presentation that is meaningful for his or her audience. For example, while I am promoting my “brand” of TechCommGeekMom, I’m not really selling a product or service the same way that a software company or communications service consultancy would be. (At least I’m not at that stage yet!) Even so, I know that when I present the webinars that I’ve done, there is some sort of value based on the type of information that I’m providing. By referring back to 8 Steps to Amazing Webinars as I prepared for this upcoming webinar, I knew that I was on the right track to maximize the information that I will be delivering. It also made me reflect, based on these steps, what made for a bad webinar, and I’m sad to say that I’ve attended a few of those in my time. I think I even remember one that Sharon and I attended at the same time, and I remember us talking about how disappointed we were with that one webinar, and we had the same sticking points about it.

I highly endorse this book for its strong content and its easy-to-read, straightforward language. Anyone who is doing a webinar–or even an in-person presentation–can gain some great pointers and advice following Sharon’s advice. Hey, it’s such good advice that the book is endorsed by the STC itself, and I know that many of their best webinars follow Sharon’s methods. So that says something right there!

You can find the book on Amazon.com, Barnes & Noble, and XML Press websites. And be sure to follow Sharon on Twitter too– she’s @sharonburton, or on her blog found at sharonburton.com. She always has good information to pass along that goes beyond just how to do webinars!

Uncategorized

Adobe Day @ Lavacon 2013: Scott Abel’s 5 Technologies Tech Comm Can’t Ignore

Posted on November 18, 2013 by TechCommGeekMom

I realized as I was writing this post that this would be my 500th post on TechCommGeekMom. Who knew that so much information and thought could accumulate through original posts and curated content? I’m also very close to my all-time 15,000 hits mark (only a few hits away at this writing). I wouldn’t have believed you if you told me that I’d hit these benchmarks when I started this blog, but of course, I’m going to keep going! I debated about what I should write for my 500th post–whether to finish my Adobe Day coverage or do something else, and in the end, it seems fitting to finish my Adobe Day coverage, because in many respects, knowing and writing about the presentation of Scott Abel, aka “The Content Wrangler”, shows how far I’ve come already in my tech comm journey from beginner to covering internationally known presenters.

Scott is one of the most prolific and vocal speakers out there on the conference circuit speaking about content–whether it be content management or other technical communication topics. It also seems like he has written the forewords of many of the best tech comm books out there. He’s everywhere! To boot, he’s an accomplished DJ, and I found myself “bonding” with him over dance remixes and mash-ups while at Lavacon, because I always enjoy when he posts either his mash-ups or his favorite mash-ups on Facebook. (I’ll be writing a post about the relationship between tech comm and dance mash-ups in the near future.) He is a person who is full of so much kinetic energy that you wonder when he’s going to explode, but he doesn’t. Even the time I saw him at the STC Summit last spring with a bad cold, he was still more on top of his game than a lot of people would be on a good day. Much like Val Swisher, my love for all things Scott Abel also knows no bounds. He knows how to stir things up at times, but there is no denying that in his frenetic pace of delivering a presentation, you learn SO much. I’m lucky that he’s so kind to be one of my cheerleaders!

ScottAbel — Scott Abel checking his files before his presentation

So when it came to thinking of a garden in Portland to use as an analogy to Scott, I had to deviate. In my mind, he’s the Voodoo Doughnuts shop located about four or five blocks away from the Chinese Garden. Scott’s talks always have lines going out the door, and like many of the Voodoo Doughnuts themselves, the unique flavors dispensed open your mind up to new and delicious possibilities and ideas, and you come back wanting more (hence, more long lines!). They are both crazy and sweet at the same time. You can’t beat that combination.

Scott was the keynote speaker for Adobe Day as well as the moderator of the discussion panel later in the event. Scott’s topic for his talk was called, “Five Revolutionary Technologies Technical Communicators Can’t Afford To Ignore.” If Joe Gollner went fast during his presentation, then Scott went at lightning speed, so my notes below are the highlights.

Scott started by telling us that translation is going to be an important part of automated content going forward. It’s important to understand that for the web, the World Wide Web (WWW) is equal to the “land of opportunity.” The WWW can reach a global market reaching new consumers. As American users, we forget that 96% of web users are not in the US. We don’t all speak English globally. In fact, less than 6% of the global population speaks English well, but don’t necessarily read or write it well.

Scott’s list of the five technologies the Tech Comm can’t ignore were as follows:

1) Automated Translation
Why would be need automated translation? We write for the *worldwide* web. There are over 6000 languages in the world, so translation is a big deal for a global reach and global connection. We need to recognize that content is written for both machines and humans. Even though we write for both machines and humans, we need to write for machines first, as they are the “gatekeepers” of content, such as for searches. Everything goes through the machine first. We need to recognize that writing rules learned in elementary school are no longer sufficient for a world in which language science is needed. We need to examine our content from the vantage point of a rules-processing engine and ensure it’s optimized for machine translation.

2) Automated Transcription
Automated transcription involves software that translates speech to text for machine use. Without transcription, content is locked and hidden from view. Transcription allows for better searchability of content. Scott recommended Koemei as a good transcription software tool for video and general transcription, as it can help transform editable content into other languages.

3) Terminology Management
Terminology management controls words in a central place, namely the words used the most and used consistently for branding, products, etc. Terminology management is important for consistency as well as for regulatory reasons. This is an instance where seeking a global content strategist is needed to help standardize processes. It’s best to adopt a terminology management system, such as Adobe partner and Scott’s suggestion, Acrolinx.

4) Adaptive content
Adaptive content is content that is structured and designed to adapt to the needs of your customer; it’s about substance of the content. Adaptive content adapts to the devices, e.g. laptops, GPS, and smartphones. Customers are demanding exceptional experiences, so we need to meet their expectations, so it’s up to responsive designers to meet that challenge. Adaptive content makes it possible to publish to multiple platforms and devices. It is content separated from formatting information. By allowing authors to focus on what they do best, adaptive content makes content findable and reuseable by others who need it. We need to rethink content, as the move to adaptive content involves work, but the ROI (return on investment) can be realized in months instead of years.

5) Component Content Management
Component content management systems are needed. They focus on the storing of content components that are used to assemble documents. Components can be in all sizes, and can be photos, video, and text. It’s about managing CONTENT not FILES.

Scott provided these slides as his example to show this:

Structured content, combined with a component content management system, supports personalized content and targeted marketing, which in turn increases response rates. In this end, this process can save money! The key is to remember that all customers are not the same! Reusing content without the “copy and paste” methods produce the best results. You can ensure that content is consistent by seeking a content strategist who understands content and is a technologist. Implement a component management system. Scott suggested checking out Astoria Software for a good component content management system.

At this point, Scott’s talk had pretty much finished, but in answering audience questions, he pointed out that there’s a lot more than just these five technologies to watch. He suggested that we should look out for wireless electricity, flexible surfaces, more wireless devices, wearable computing, and augmented reality as well. He also said that in order to mature as a discipline, we need to be content craftspeople, content designers and content engineers. We need to leverage using content and code. We need to think more like engineers, and less like writers and editors. Even websites that are very localized still need to be written for global purposes to improve the English used for the native speakers as well. Controlled vocabulary helps all end users!

Scott covered a LOT of information in a short amount of time, and he set the tone for the rest of the session, as the presentations that followed repeated much of the same information. (This is a good thing, because then we know that the information is valid, coming from several experienced technical communicators!)

Scott posted on Twitter than his presentation was available on SlideShare, but I have it below.

And as always–Scott, if I misinterpreted or misquoted any of the information I summarized above, please let us know in the comments!

Uncategorized

Adobe Day @Lavacon 2013 – Val Swisher Says It Starts With The Source

Posted on November 8, 2013 by TechCommGeekMom

Ladds_1 — Ladd’s Addition Rose Garden
Photo from http://www.rosegardenstore.org

Val Swisher was the next to last individual to speak at the Adobe Day at Lavacon 2013 event. For those who are regular readers of this blog, you know that my love for all things Val Swisher has no bounds. I’ve always been able to take her easy-to-digest information, and absorb it quickly into my brain, as well as relay her knowledge to others. When I looked at Portland Gardens to compare her to, I chose Ladd’s Addition Rose Garden. While it’s not as well-known (unlike Val, who is very well-known), this particular park, according to The Rose Garden Store, was one of four rose gardens especially built from the Ladd estate, in which the design included these gardens coming together to form the points of a compass. I often think of Val as my compass, as she has never steered me wrong with her information or with the wisdom and fun that she’s shared with me one-on-one.

Val’s Adobe Day presentation centered on talking about source English terminology in a multi-channelled, global world, and how terminology affects structured authoring, translation and global mobile content. She started the talk by reminding us that historically, we’ve always created content, whether it’s been on cave walls, through stenography, through typewriters or eventually on word processors. In every instance, consistent terminology has been essential for structured authoring and content. Managing terminology is also essential for translation and for reuse. She stated that prior attitudes used to be that the more complicated the writing was, the more “fancy” the product was. Today, that’s definitely not true. She used the example that I’ve heard her use before, but it’s so simple itself that it’s a classic. Her example involves writing for a pet website. If multiple words meaning dog are used, there can be problem with reuse, because you can’t reuse content if you use different words.

Val_example_dog — Here’s the example Val showed.

Val pointed out that it would be an even worse situation if technological or medical terminology was used instead.

Val continued by saying that when it comes to XML, reuse , and terminology, you cannot realize the gains of structured authoring if you’re not efficient with your words. Terminology is critically important to gain more opportunities.

ValSwisher — Val Swisher explaining how to approach content from a translation perspective.

Translation comes down to three elements– we’re trying to get better, cheaper, and faster translation output. We MUST use technology to push terminology and style/usage rules to content developers. In order to make it cheaper, we need fewer words, reused words, and reused sentences. It’s impossible for writers to know or even know to look up all term and usage rules. We MUST automate with technology. For example, “Hitting the button” is not translatable, but “Select OK” is fine! She said, “Say the same thing the same way every time you say it.”

For better translation, translation quality needs to improve and meanings need to match in order for better machine translation to be a possibility. Bad translation comes from the source itself. If the source information is problematic, then the translation will be problematic. The best way to save money and time is to say the same thing, every time, using the same words, and use shorter sentences. For machine translation, don’t go over 24 words in a sentence.

Faster translation is seen as content that takes less time to translate, needs fewer in-country reviews, and gets to market more quickly. The key to delivering global mobile content is responsive design, global mobile apps, text selection is key, and terminology is the most important element. Val showed this example of how translation in responsive design isn’t working, where the Bosch websites are not exactly in synchronization:

The mobile website on the left looks nothing like the English language version on the right.

The simpler the design is for the website–especially in mobile, the less you have to tweak it. This is especially true where consistent terminology is important, because consistency is needed for structured authoring. Creating truly faster, cheaper, and better translation enables a true global responsive design. This is not a simple task, as there is no such thing as simple, even when writing about complex concepts. Even if you think you’re not translating, your customers are, so the content needs to be very clear. The scary part of this is that some companies use Google Translate as their translation strategy, which is risky at best. To use something like Google Translate as the translation software, the content had better be tight, clear, and consistent.

One of the things I enjoy with Val Swisher’s presentations is that it all comes down to common sense, and she breaks it down into easy manageable parts for those of us–like me–who might not have thought about the context of language for structured authoring, and the consequences for not strategizing content to include translation considerations.

I highly recommend checking out Val’s blog for other great insights.

(As always, Val–if you’d like to add or correct anything here, please do in the comments below!)