Adobe Technical Communications Suite

Adobe Tech Comm Suite 2017 is better than ever!

Posted on February 14, 2017 by TechCommGeekMom

Recently, Adobe held a virtual press conference for the 2017 Release of the Adobe Technical Communications Suite, which launched on 31 January 2017. While the Suite continues to include the latest versions of Captivate, Acrobat, and Presenter, it’s RoboHelp (RH), the XML documentation add-on for Adobe Experience Manager (AEM), and its flagship product in the suite, FrameMaker (FM) and its related FrameMaker Server that have all received updates with this newest release.

FrameMaker itself has been around for thirty years now, but it’s been especially in the last few years that significant changes has been made to accommodate DITA support, multi-channel and mobile publishing, and support from right-to-left (RTL) languages.

With the 2017 Release, Adobe’s main objective was to provide new features while simplifying current features that would help with productivity and keep the end users in mind.

I found that now that I have a better understanding of the structured authoring views from my recent DITA course, I could see these products with a fresher perspective while I attended this virtual press conference, and better appreciate the upgrades.

The main attraction for the virtual press conference was FrameMaker, as the product has had some major overhauls, including new features centered around the authoring experience. I won’t go into all of the features, as there’s too much to review, but several of them made a big impression on me. FM has been a complicated tool to use for many years, but it seems to me that with each new release, the tool becomes more user-friendly for those who aren’t as deeply entrenched with all the bells and whistles. The new interface is more modern and usable, and there’s easier access to recent items through the Browse Computer or repository feature. This gives you access to all resources like tutorials, guides, and online help. It also allows you to access structured and unstructured items in one page. Even within the Search function, there is better auto-complete functionality which shows predictive results based on user typing through responsive HTML5 output.

An important upgrade in this 2017 release is that menus have been optimized and reorganized, with more commands to improve discover-ability. My favorite new feature within these new menu changes is that the “Special” menu is gone, and the much more logical “Insert” menu has been added. This is something that has sorely been needed for a long time to be more user-friendly interface! Why, just today I was in a different Adobe tool, and I looked to insert an image, and that particular app (a Creative Cloud app) didn’t have an “Insert” menu at all! Insert menus are commonly used in apps almost universally now, that this was a long time coming. It makes inserting objects more intuitive for an app that’s not always that intuitive. It’s one of those “DUH!” things that I’m glad Adobe has fixed for FrameMaker. The Insert menu provides one stop for inserting images, files, variables, elements, equations…you name it! For example, all that needs to be done to insert an image into a document is to go to Insert-> Image and it’s done! You don’t need DPI settings change, as the DPI settings are retained, but they can be changed. You can also do a “drag and drop” of an image into a document easily. All you do is add to your project, then drag the image into the page, and it adapts to the page. You can still adjust the size in object properties if needed. The object properties dialog is improved, as there is an option to maintain aspect ration, DPI can be set inline, and apply a check inline. The “Element” menu is also enhanced. New options have been added to insert, wrap, and change. The Insert drop down is great! It has everything you need, and will likely be heavily used.

Shortcuts for productivity got a boost, as there is a new Command Search feature that is accessed through the <F7> button and very easy to use. All shortcuts are also now listed next to menu commands so that power users can learn them more easily. <CTRL-1> provides a list of where you are within the structure of your structured authoring, which is rather convenient. Commands that are applicable globally, such as borders, text symbols, rulers, grid lines, and hotspot indicators that impact all open docs both structured and unstructured are viewable now, although there are some limitations with structured views.

PODS have also has some upgrades as well. A new paragraph designer table allows you to create new styles easily in the pod. Styling icons in table and paragraph designers have been replaced with labeled buttons, configurable options have been reorganized and relabeled, and redundant command operations have been removed. Additionally, adding or editing a conditional tag now happens thru a dialog. The former “Select” drop down list has been replaced by Filter icon. Color and background columns have been removed. Conditional takes are listed with their close to final formatting, with tooltips displayed for conditional tags listed in the pod. Several catalog PODS are also redesigned, with old buttons replaced with icons. Deletion has been made intuitive by removing extra options.

These changes have allowed the project management of a given project much easier, as now it’s easier to organize content such as a DITA map, book, topic, image, TOC, or index files related to a project in a single place whereby you can drag and drop files from Windows Explorer.

Structured Authoring gets some boosts as well. The Status bar now provides information about the exact path of the current element in your structured document. You can show or hide content from the structure view for a cleaner view as you work. Some of the new Insert menu options have been added for structured authoring, such as the Insert>Cross-Reference function, which should be very handy. There is also an improved DITA Keyspace Manager, whereby if any DITA map is opened, it gets populated automatically in drop down. The ability to search for a keyspace by entering the 1st few characters.

To keep up with the rapid changes in technology, high resolutions displays are supported now! Support for 4K resolution is now available, and allows the application to scale automatically. No separate setting is required to adjust resolution, so icons are now more sharp and size will scale automatically with the screen resolution.

Publishing features have not been forgotten, as they include brand new responsive HTML5 layouts that are modern, frameless layouts with a redefined browsing experience, are fully customizable, and can easily match the look and feel of your corporate website template. The navigation is search driven, and you also have the ability to add favorites while still being fully accessible (508 compliant).

New publishing features include the introduction of basic HTML5 formatting without any JavaScript or layout, with the look and feel controlled by CSS. This makes publishing lightweight and easy to share. Text searches within searchable vector graphics (SVG) can now be done, and supported in HTML5, as the information in the SVG files can be read and displayed as part of search results. Multimedia files are managed in assets folder in published output. Inline styles have been cleaned up, including the introduction of a setting for Excel inline styles from published output. You can publish topics to a single folder–an important organization feature. Content personalization has been improved with DITA attribute support in dynamic content filters in the indexes, and a new dialog has been introduced to select conditional attributes.

Wow, that’s a lot right there!

All these changes are great for the FrameMaker app, but what about the FrameMaker Publishing Server? No worries! The 2017 release of the FrameMaker manage remote publishing, and can publish bi-directional content across formats and devices, so it can integrate with any CMS.

RoboHelp has brand-new, responsive HTML5 layouts as well, also incorporating modern, frame-less layouts with a redefined browsing experience that’s fully customizable. The Search autocomplete is also functional here in RoboHelp as well, allowing for search in responsive HTML5 output that shows predictive results based on user typing by segment first–which is a unique feature, gives contextual results, can indicate the number of occurrences of an entered word or phrase which helps in narrowing down the matching results, and can even correct spelling mistakes as you type in the search. The new authoring features include thumbnail support for images, folder imports for baggage files, and variable view toggling.

The Adobe Technical Communications Suite 2017 Release (TCS 2017) includes these latest versions of FrameMaker and RoboHelp, as well as the latest versions of Acrobat Pro, Captivate, and Presenter, which went bought together in the Suite, provide a 58% savings over buying the tools separately.

While not formally part of the Technical Communications Suite, it’s also important to mention that the Adobe Experience Manager (AEM) XML Documentation Add-On 2.0 version has been released. If you are using AEM as your CMS or CCMS, you can host your tech and marketing content that’s written up in FrameMaker more easily through the integration of this add-on. This add-on allows for content sharing and reuse which lends itself to consistent user experience and reduced total cost of ownership. Higher content velocity helps to drive enterprise publishing features, such as batch publishing, baseline publishing, and post-publishing workflows. Enhanced review and collaboration capabilities include web-based inline review, web editor enhancements that help with content management capabilities and document life-cycle management.

If you want more information about TCS 2017, you can click on the Adobe advertisement in the right column, or email the Adobe TCS team directly at techcomm@adobe.com.

Additionally, there is a 2017 Release Launch Webinar on 15 February 2017. It’s free! Learn more and register for the event on the Adobe Event website.

Uncategorized

Confessions of a Failed Technical Communicator

Posted on December 10, 2016 by TechCommGeekMom

homer_confession — Really, Father, my only sins are beer, donuts, beer, donuts, not knowing DITA, beer, donuts…

“Bless me, Father, for I have sinned! I am a failure in technical communications.”

OK, perhaps in many eyes, I haven’t been a failure in technical communications. It will be five years this spring since I graduated with my Masters degree in Professional and Technical Communication from NJIT. In many ways, that feels like it was just yesterday, and I’m still a “new graduate”. But with the change this year in my STC Membership that’s moved from “Student” to “New Professional” to “Classic”, I supposed I’m not anymore.

While graduate school gave me a good foundation to move forward, I learned very quickly that I needed to continue to educate myself. As I attended conferences and presentations, and paid attention to discussions in social media, I found out that graduate school lessons barely cut the surface. I’ve tried my best to continue my studies by attending as many webinars, conferences, and presentations that I can. I even took another university graduate certificate course on digital marketing, hoping to get some insight that might help me going forward.

However, in the end, I failed to do one thing that might actually boost what I’m doing as a fledgling content strategist, and thus, my confession: I needed to learn DITA.

For those of you who don’t know what DITA is, it’s the acronym for Darwin Information Typing Architecture, and it’s a commonly used method for creating structured authoring using XML coding. The idea is that documentation done using DITA methods will allow for single-sourcing for content elements, and equally make it easier to integrate that content into print or digital outputs in a super-organized, modular way. It’s a standard that helps because it’s generic to almost any system out there. Any system that can read XML can read a DITA document, for the most part. When moving from one system to another, the content can stay intact if done using DITA/XML methods.

I don’t remember learning much about DITA in grad school, other than understanding what it was in general as I explained it above. I never learned the details. In my work life so far, I haven’t needed it. It’s always been unstructured authoring. I try to take some small steps to create some single-sourcing content when possible in content management systems, but that was hard to do sometimes. One of my recent jobs made me realize that we needed some sort of structured authoring done, but I didn’t know how to go about it. We created our own coding tags to describe things going on in copy decks. It wasn’t the best, but it was better than nothing.

In the past year, I’ve tried to figure out ways to continue to improve my skills, and make myself more marketable as a content strategist/content manager. I talked to the leading experts in the field. (It’s one of the benefits of getting involved with the STC and attending STC events–you get to know these people personally.) And the one thing that seemed to come back to me again and again was that I had a good resume, and I have some great skills under my belt, and they knew that I was a good writer from this blog. The biggest sore spot in my skill set was that I lacked an important skill–knowing DITA and using it. And while I looked for jobs in my area that included DITA practices (I think I’ve only seen one listing in three years), I’ve been assured that if I could learn DITA, the remote/telecommuting possibilities could be much better for me. And since remote opportunities are my best bet right now, I have to do what I need to do to make that happen.

So, as the saying goes, I bit the bullet. Fortunately, the STC was promoting a course about DITA Essentials taught by Bernard Aschwanden, the Immediate Past-President of the STC, and the proprietor of Publishing Smarter. Bernard’s a great instructor, and he’s taking it nice and slow. One of the best parts of the course is hands-on experience, even if it’s in the simplest ways. That’s the way I tend to learn best–learn the logistics of how something is done, then I need to learn to do the work through trial and error. Last week’s assignment was particularly challenging for me. While I understood what I had to do conceptually, since I was also trying to familiarize myself with a few XML editors at the same time while applying what I wanted to do with my assignment, I got very frustrated. I sent in my assignment, along with notes about where I was getting frustrated and needing some guidance. Bernard assured me that all would be well, and asked me if he could use what I had turned in for my assignment for the most recent class. He also warned me to have a glass of wine ready while taking class, because I’d be needing it. Yikes!

I was told to prepare for the onslaught of big corrections to my DITA homework with a glass of wine. I took the suggestion seriously, thankfully.

The glass of wine was done by the end of the class, and yes, he ripped my assignment apart, but it was okay in the end. I knew there were problems with it, and he showed me where my original thought process was correct, but I didn’t know how to execute it properly. One of the mistakes I was making was my use of XML tags, particularly using the correct ones. While the XML editing apps all have guidance features to help you with using correct tags in certain situations, I still wasn’t using the best choices. Most of that was because I’m not familiar with what these XML tags mean, so I was using them at face value. For example, I was using a step example tag in part of my content, and Bernard understood why I used it, but felt that the way I used it was incorrect, and didn’t allow for cleaner coding. Okay, I can deal with that, especially when he demonstrated the correction.

So, as much as I’m struggling with DITA, I do understand the essential concepts behind it now. My biggest problem is learning how to use it beyond the most elementary tasks. I haven’t had any “real world” scenarios to date when I could implement and learn how to use the XML editors and use DITA practices in writing or rewriting content. I need to figure out how to find content and start having a way to truly play with something so that I can get the full experience of that trial and error to master DITA.

After the STC course that Bernard is teaching, I plan to follow-up with Scriptorium’s DITA tutorials as well, and see if I can learn some more about XML coding. I have a lot to do to figure this out, but I know that in the end, this will be a big skill that will make a lot of difference in how I approach content. The content strategist skills I already have acquired have helped me frame DITA much more easily than if I learned this with no prior knowledge. But, I can tell that I still have a long way to go before I feel that I’ve mastered this.

So, this ends my confession. I have needed to learn DITA. If it’s not taught in university classes in technical writing, it should be. I think it would have saved me a lot of frustration, and provided more opportunities for me sooner. If I can get a better handle on this, I’m hoping that I can start exploring how XML Editors can integrate with CMSs, like Adobe CQ. I’m not an Adobe AEM developer (I’m not a developer at all!), but I know how to create websites and pages with AEM, and hopefully I can start figuring out how to integrate those skills with DITA skills. I was told by one mentor, that would make me a very desirable job candidate, and I think she’s onto something. Of course, I need to brush up on my AEM skills, since it’s been a couple of years since I’ve used them regularly, but with all things, once you master them, it’s like riding a bicycle. You might be a little unstable at first, but you never quite forget how to do it once you get started back into it again.

Here’s hoping that in 2017, DITA will become a “bicycle” skill for me. I’ll go say a few rounds of the Rosary in the meantime for my penance.

(What do you think? How important is DITA in technical writing? I’ve heard some say it’s a passing trend, and others say that its usage continues to grow. Include your comments below.)

Uncategorized

Will Tablets Replace PCs? Part 2

Posted on October 25, 2016October 25, 2016 by TechCommGeekMom

"Nope. Even I can't see much improvement over the last few years," says Geordi LaForge. — “Nope. Even I can’t see much improvement over the last few years,” says Geordi LaForge.

Four years ago, I wrote a post that was in response to RJ Jacquez’s post on his blog about the advent of the Microsoft Surface’s release.

My response to RJ Jacquez’s question: Will Tablets replace PCs?

RJ’s argument was that while mobile was the wave of the future, he felt that the Surface was not a mobile product. Since the Surface still ran full programs rather than streamlined apps, it really didn’t qualify as a mobile device, despite its tablet-like form. His argument was that the industry needs to learn to streamline code to make lighter programs for heavy duty use so that mobile can become more prolific.

My argument at the time, more or less, was that while I agreed with his thinking and supported more use of mobile, I didn’t think it was going to happen anytime soon because PCs enabled people to use more powerful programs that tablets just couldn’t handle. I supported the idea of cloud technology, which was just barely emerging at the time, but I knew it wasn’t there yet. Only when cloud technology could catch up, I contended, then we could start making a bigger move to mobile devices as our primary work tools.

Well, here we are, four years later. Have we made huge strides in moving more to mobile? Yes and no.

More tablet-like devices have been created in these four years, and the main leaders in this arena, Surface and iPad, have made improvements over the years. Surface has its standard version of the device, as well as a “Surface Pro” and “Surface Book”. iPad has developed its competition creating iPad Pro, but the various MacBooks continue to be the competition for the Surface Book.

Surface’s OS is still the same thing that runs on laptops, namely full versions of Windows 10. Windows 10 runs regular, full version programs, but it also runs on apps that can be bought through the Microsoft Store, including many cloud-based apps such as Microsoft Office 365. But, it’s still a really flat PC in a tablet format. People still use it like their PC, running more powerful programs in it, and use it as a laptop, just smaller. It’s certainly more portable than a standard laptop, but as laptop design gets thinner and thinner, it doesn’t make much of a difference. Additionally, the price tag on the Surface is still pretty high. To get a powerful enough machine that can create and edit video, you’d pay somewhere around US$3000.00+ for a Surface, when you could get something just as powerful in another brand of laptop for less than half that price (like I did for my current laptop).

iPads, in the meantime, have become more robust, and while still more dependent on cloud-based apps such as its own Work suite and it does run the cloud-based Office 365, other apps like Adobe’s Creative Cloud aren’t the same. There are Creative Cloud apps available for iPad, but they are still the watered down versions of them, and not the full versions that can be used on a laptop. Even though Adobe claims that Creative Cloud is cloud-based, it’s only cloud based insofar as it will save your work in iPad to your storage within Creative Cloud, but that’s about it. iPads have definitely been a frontrunner in promoting cloud-based storage, but running robust apps that are memory-intensive isn’t part of its anatomy.

Still, with these minimal advances, they are still steps forward in the right direction. For example, I do used Office 365 or iWork on my iPad when I help my son write up his homework assignments, and I can store them on my OneDrive or my iCloud. If he’s working on a bigger project, he can use PowerPoint or Keynote on my iPad, save it to OneDrive or iCloud, and then continue working on the project using my laptop or his desktop. Cloud-based storage, and some other cloud-based apps have definitely gotten better, for sure. I like this ability to switch from my laptop to my iPad to work on low-impact project, like doing my son’s homework.

There are some apps that won’t ever happen on iPad. For example, I’ve been working heavily in Dreamweaver this past week or two. This is not to say there aren’t other HTML/JavaScript editing tools that are probably iPad apps out there, but this is the most popular one and a standard one to use. Is there an iPad version to access? No. I need to use my laptop for this. This might be where Surface would be the better choice, but again, it’s still really a laptop in a different device shell, as mentioned before. I doubt that Flare or Adobe TechComm Suite tools are ready for the iPad treatment either. They can probably run on a Surface, but would you really want that?

Even a StarFleet Captain like Benjamin Sisko can find this sort of thing daunting, and needs to seek Kira's help in straightening this out! — Even a StarFleet Captain like Benjamin Sisko can find this sort of thing daunting, and needs to seek Kira’s help in straightening this out!

It looks like the PC versus tablet/mobile wars will continue to rage on for a while. I don’t think they’ve gotten that far in four years, but the few improvements made have certainly been in the right direction. We’re not quite there yet. I think RJ’s original thought that all apps need to be streamlined for mobile use was a great observation then, and it’s still one that needs to apply now. If we are truly going to move towards the mobile age, bigger steps have to be made. These are steps forward, for sure. I think more has been concentrated on mobile phones, to be honest, since more people own them. And that seems appropriate. I don’t bring my iPad or my laptop with me everywhere, but I bring my phone everywhere. Then again, I’m not working on HTML code on my phone, so there has to be some sort of balance at some point.

Mobile devices are becoming more powerful all the time, but it looks like we’ll have to be a little more patient before we see another big leap with technology. I know there are some “big” announcements from Microsoft and Apple about these tablet products sometime this week, but I’m not holding out for any big advances, even though they are certainly overdue.

What do you think? How will this lack of technology development–or the future of mobile technology–help or hurt tech comm? Include your comments below.

Uncategorized

Saddle up for a FREE workshop event from Adobe at #STC2016!

Posted on April 27, 2016 by TechCommGeekMom

While I was unable to go to the STC Summit last year, I am looking forward to going to Anaheim this year to not only being a presenter at the STC Summit, but also to learn and connect with other technical communicators again!

I realized that one of the events I’ve always liked attending is the Adobe pre-conference event. They always have great information to share. However–what’s this? No Adobe Day this year? Nope. But wait…there’s something better.

Register for the FREE Adobe Tech Comm Tools Workshop at the 2015 STC Summit! — (Click on the wanted poster for more information)

That’s right! Saddle up, and gain some skills through this FREE Adobe Tech Comm Tools Workshop! This looks like a great event, cowboys and cowgirls! There are industry leaders leading the workshop, you earn a certificate for participating (which you can include on your resume, it’s that good), and lunch and snacks are included in the afternoon. And did I mention it’s free? Who says you can’t get a free lunch AND a free certificate? Evidently not Adobe!

Oh, did I also mention that even if you can’t attend to earn the certificate, you can still follow along on my Twitter feed found at @techcommgeekmom that day, as I’ll be tweeting highlights of the event for all who come to the Twitter corral!

If you don't comply, you can't register. But these are easy terms to deal with, Sheriff. — If you don’t comply, you can’t register. But these are easy terms to deal with, Sheriff.

Now, there are some caveats in registering, namely that you have to bring your laptop, and download the Adobe Tech Comm Suite Release 2015 Trial Version (if you don’t already have the full version). Other than that, it should be like riding into the sunset.

This is a great opportunity for those who would like to either get to know the Tech Comm Suite better, or brush up on some skills. Space is limited so you should register as soon as possible to get your seat on this great event!

Information and Registration for the Adobe Tech Comm Tools Workshop at the 2015 STC Summit

(My apologies to those who are more sci-fi savvy for mixing my space westerns together. Firefly and Cowboys and Aliens were the first things I thought of!)

Uncategorized

RoboHelp 2015 Release is a big step forward!

Posted on September 8, 2015 by TechCommGeekMom

Adobe RoboHelp -- 2015 release — Adobe RoboHelp — 2015 release

The last few weeks–in fact, the last couple of months–have been so busy for me that I can’t always finish what I need to get done. One of the things on my long to-do list has been writing up a review of the new RoboHelp 2015 release. I shouldn’t have waited, because let me tell you–there are some great things happening with this updated product! Additionally, Adobe has already released an update, which I will include details from that as well in this review.

Back in May, Adobe held a preview press conference to let us know what’s new in Robohelp (2015 release). It was hosted by Maxwell Hoffmann, one of the Technical Communications Suite (TCS) product evangelists for Adobe. I know Maxwell fairly well, as I first had a chance to work with him on the webinar I did for Adobe three years ago, and I know he knows and understands the TCS products very well, especially since he worked for some of these products before they were originally acquired by Adobe! He’s also a master storyteller and pays a lot of attention to what technical communicators have to say, so he’s excellent at explaining the benefits of features to users.

The first thing that Maxwell noted was that like the newest release of Framemaker, the naming convention for current and forthcoming releases from now on will be reflected in year instead of version 12, 13, etc. This allows for some consistency, and it’ll be easier to know if you have the latest version based on the year it was released.

Going forward from that, Maxwell explained that RoboHelp (RH) now offers a new degree of usability to both help authors and their users. There are several new features going on in the 2015 release that I have to tell you, truly impressed me, and I think you will find to be great upgrades as well. The highlights of these new features include:

A brand new user interface
Best in class multi device publishing capabilities
Dynamic Content Filters that enable end users to quickly find relevant content
Single-click mobile app creation workflow
Miscellaneous productivity enhancements

Let me go into more detail about each of these highlights.

Brand New User Interface

Even though RH was already able to have its configuration customized by the user, many of the icons were rather small and hard to see–the interface had a lot going on in one screen. Even so, one of the advantages of RH has always been that you didn’t have to work with code in RH. The new interface, when demonstrated, was significantly cleaner and more concise. Not nearly as busy looking as its predecessor! The interface has a much simpler look that resembles modern MS Office interfaces with the task ribbon, project manager window/frame, and the main designing frame. The icons are larger and much clearer to figure out what they are. You also have a choice over the user interface being light or dark, and with or without color. It’s totally customizable to your preferences. Nice! Maxwell noted that it’s also helpful if you have two instances of RH running to keep different projects straight.

The commands are clustered in the tab ribbons. As the different tab ribbons were demonstrated, I could see this was so much easier to decipher! There is also an icon in the first two tabs called “Pods” which can help you manage the pods you are working on. The ribbons allow you to see all the commands readily available to you in a consistent manner. All the tab ribbons seem consistent with MS Office-style ribbons, so new users should be able to adapt easily to these command choices.

The new Output tab ribbon, which contains one of the most frequently used clusters of tools, replaces the single-source layout pod that was in previous versions of RH. The Primary Output tool icon within the Output tab is customizable so that you can choose what outputs you want to use if you have a certain set of outputs that you standardly use. You can still do output of individual things as well, and the generation of output is faster now. There is also a great “Primary Output View” which allow you to prototype and see what your output will look like before you actually publish.

The area circled in red shows the customizable Primary Output tool, which provides a one-touch customizable option to publish to your primary outputs.

There are several other interface features that are great enhancements. The Quick Access Toolbar used to display your favorite, most commonly used commands can be easily and quickly customized. The tabs will reformat with window resize, and the ribbon can also autohide.

Within the workspace, table creation is similar to MS Word. Tables can be created in color, and have greater flexibility. When creating a table, just like Word, RH creates a specific tab for formatting and layout tables when needed. When creating content, commands that don’t make sense will gray out. Keyboard tips and shortcuts can be customized. The opening window is much more graphical and easier interface to use to start projects. When opening up a file, it will remember what documents you had open. Of course, if you are used to the old interface, this is an option as well.

With the update released in late August, the layouts have been optimized

Boy, Adobe has really gone all the way with making RH an easier, more user-friendly tool to use! If nothing else, this was the one improvement that in my eyes that impressed me the most, because I think this new, user-friendly layout is much less intimidating than the old one, which will help those who are new to the product or not as proficient on the product more willing to use it.

Best in Class Multi-Device Capabilities

RH now has new dynamic content filters that empower users by allowing them to find revelvant content faster. Adobe created brand new HTML5 layout enhancements which include:

The ability to easily show or hide widgets such as the Table of Contents (TOC), Glossary, Index, or Filter panes
Configure media query boundaries for different screens
Support native social media widgets
Flip to Right-to-Left (RTL) layout by changing language in single-source language
Show or hide branding band for mobile output

The HTML5 responsive layout has easy off/on icon control in layout, which is different from previous RH versions due to the clearer icons in the toolbar. Search enhancements include:

The ability to have topic descriptions and control what that text is to make the description more meaningful.
Breadcrumbs are now also part of the descriptions.
Output search results are available in a collapsible left panel for easier navigation.
Native social media widget control allows Facebook and Twitter icons to appear on the output so that you can share the information. This is displayed as an arrow on the side that can pop out the content as needed, so it’s not in the way, yet still available.
Flip layout to right to left with language attribute for Arabic and Hebrew. This will also work with linked or imported RTL Framemaker documents.
Generate faster, better responsive HTML5 output. Faster loading times reduced by half, smaller sized output–2MB less for every 100 topics, and no flickering screen are the result.
You can maintain the Table of Contents state in the left column, and in fact, you can expand more than one section at a time within that section.
Cleaner HTML5 coding.

Some other bonuses are that custom fonts can be embedded when generating high fidelity ePub, and more skins have been added for output formatting to provide more flexibility and to accomodate for RTL projects.

Dynamic Filters and Faceted Navigation Improve The End-User Content Consumption Experience

The new HTML5 layout and contextual search results can let your end users quickly navigate to the relevant content through dynamic filters. Based on existing conditional tags/expressions functionality, users can use the tags/expressions OR/AND at the build time and display these tags/expressions for dynamic filtering by the end users.

Tags can be grouped and filters shown in a two-level hierarchy. All the content is dynamically filtered (TOC, Index, Topics, Search Results etc.). You can choose a display name for both tags and expressions, which works for merged projects as well. Tags can be shown in the output for better testing (Maxwell said that Adobe is most likely the only one doing that with its product), which is currently supported ONLY in responsive HTML5 output and mobile apps.

Enhancements include the ability to enable a single selection or multiple selections of the tags in final output, and enhanced CSH support through a dynamic content URL, so the filter choices are actually seen in the URL of the output, which is great. In the demonstration given, Maxwell showed how you can navitgate through filtered content so only certain things show for certain audiences, which I thought was a great use of this feature.

Content Centric Apps (developing mobile apps)

Robohelp can publish content as mobile apps for iOS and Android which can be read remotely or downloaded directly on your device. Adobe has made it super easy to create mobile app for your documentation by using a PhoneGap:Build/CS subscription to generate multiple apps for both Android and iOS. (PhoneGap is considered an inexpensive subscription.) Mobile apps can easily be downloaded by scanning a generated QR code that can be shared, although a URL that can be shared, too.

Miscellaneous KEY enhancements
There are several extra enhancements that don’t fall under the other main categories, but are still equally important.

Users will be able to work more productively with a ribbon UI and enhanced search functionality, including bi-directional and multiline searches. The support for languages like Arabic and Hebrew, which was a major feature upgrade in FM 2015, is also included in this RH release. As of the new update released in late August, Farsi is also supported.
The “Find & Replace” functionality and searching abilities are significantly improved. Key enhancements include the ability to find results in Design Mode and open the files directly from search results.
Search scope has been extended, so you can also set the search scope to a current project, specific folders, the current window (including TOC/Index, etc. which is new), and all open files (also new), as well as do a multi-line search.
The standard keyboard shortcut of “Ctrl-F” now works to help do searches.
There are now separate tabs for find and replace. In the demonstration given, we were shown that you can find and replace within design mode instead of the HTML mod. There’s also the ability within the find/replace that if you have a long list of items, and you want to find where a specific item in located within that list, then you can go into the Project tab and click on “locate item”, and it will take you directly to the page in design mode. Really nice!
Search direction support–both forward and backwards– is available. You can also search within the source code as well through the line numbers listed in the search lists, which makes this feature very flexible.
Conditional text control has been improved with tagged output so that you can see what is conditional or not for QA purposes. Before, RH had slashed color tags that made it difficult to read and not always an exact match to what the conditional tag was. Now, it has a more intuitive conditional build tag display that is much easier to read text while editing–the overline color exactly matches the tag. The overline is used as a conditional indicator with better readability than cross hatches, the color of the overline is exactly that of the tag, and easy to figure out the tag boundaries.
Support is now provided for named expressions.
Other enhancements enhancements at the time of the release included miscellaneous search enhancements, better scripting support, remember project state, and “find now” works in project manager frame.

Within the update release in late August, some additional enhancements were made in addition to those already mentioned above. Windows 10 support, online video derived from HTTP URLs can now be embedded in RH output, playback settings for multimedia are available, and more than a dozen bugs have been fixed. They’ve evidently been working hard at Adobe to add such features in a short time since the May release!

Pricing

Pricing & Availability on June 2 (in USD and AUS):

Product	Full Price	Upgrade from last release	Upgrade from 2 releases	Subscription Price	Languages Supported
RoboHelp 2015	$999	RH 11: $399	RH 10: $599	$29.99/mo	English, French, German, Japanese
Technical Communications Suite 2015	$1699	TCS5: $699	TCS 4, 3, 2 or 1: $1199	$49.99/mo	English, French, German, Japanese

TCS 2015 Release includes RoboHelp, FrameMaker, Captivate, Acrobat, and Presenter–all at a price that is 57% less expensive that buying all products individually. It’s something to consider!

I think the thing that impresses me the most out of all the great new features truly is the new interface. Having a simpler, more user-friendly interface is going to bring more users–especially new users–towards this already powerful product. The continuing development on content design flexibility and inclusion of mobile output helps Adobe keep this product as one that will assist technical writers with creating more user-friendly help guides for customers.