Adobe has officially released the Adobe Technical Communication Suite (2017 release) including the new 2017 releases for Adobe FrameMaker, FrameMaker Publishing Server (2017 release) and RoboHelp. It has also released the 2.0 Release of XML Documentation Add-On for Adobe Experience Manager.
There have been a lot of improvements to the usability of the applications, reducing the number clicks required to carry out tasks.
For both FrameMaker and RoboHelp, Adobe has continued its developments in publishing HTML 5 output and personalised Help content. RoboHelp has a new, frameless Responsive HTML5 layouts that offer more intuitive navigation, and the ability to filter content dynamically. There is also a significantly improved search, which now has autocomplete.
It’s good that Adobe has focused on improving the usability this time – for Technical Authors and for the end users. It must be tempting to keep adding more to an application, when the best gains can be from improving what already exists.
Adobe released the latest version of RoboHelp last week, and we’ve taken it for a quick spin around the block. It’s called RoboHelp (2015 Release), but we’ll call simply call it RoboHelp 2015.
Continue reading “RoboHelp 2015 Release – A review”
Most of the Technical Authors I have met don’t have a good thing to say about Microsoft SharePoint. In many ways, it represents how not to publish content online. It is seen as encouraging people to move print-optimised documents (Blobs) around, rather than units of content (Chunks), and users are typically left to rely on search to find which document contains the information they are looking for.
For all those issues, SharePoint may still have its place – for managing documentation projects.
Continue reading “SharePoint for documentation projects”
Adobe released its latest version of RoboHelp Version 11 (and Technical Communications Suite 5), a while back and asked if we could write a review. There have been a number of excellent reviews, so we’ve been wondering what extra we can say. We’ve decided to address some of the questions we’re often asked by organisations when they’re deciding which Help Authoring Tool to choose.
Continue reading “RoboHelp 11 review (finally)”
You’re welcome to join us on our upcoming free webinar, “The changing nature of content”, which will be held at 7pm (GMT+1) on 24th April 2013.
In recent years, technical communicators have focused on improving User Assistance through new technologies and systems, with the assumption that the nature of the content the tone of voice, the writing style should remain the same. In this free webinar, sponsored and hosted by Adobe, we’ll investigate whether the tried and tested writing methods from past decades still make sense today. We’ll look at the reasons why some organisations are “breaking the rules” with the User Assistance they provide.
The registration details will be posted to the Adobe online events Web page in the next few days.
If you need a Technical Author who knows RoboHelp, then Cherryleaf can help. Our Projects team and many of our contractors have skills and experience in using RoboHelp to create great content for your users.
Contact us if you’d like to know more.
We’ve added two self-study training courses in Author-it version 5 today – one for Author-it users and the other for Author-it Administrators and Users.
This year, we’ve also introduced a classroom courses in RoboHelp 7 and FrameMaker 8, and we’ve launched an updated version of our DITA training course.
We’ve another course in development and one at planning stage.
Let us know if there’s any other training courses relating to technical writing that we should consider.
With the imminent release of DITA support in MadCap Flare, will competing Help authoring tools (HATS) suddenly seem inadequate to the task of technical writing?
Where does this leave Adobe’s RoboHelp?
I suspect it will be difficult technically and commercially (Adobe also owns FrameMaker) for Adobe to add DITA support into RoboHelp.
If writers are collaborating on a project or if a Help system needs be localised into foreign languages, then RoboHelp and other HATS may well lose out to Flare.
However, if a sole author just needs to write a straightforward Help File, then many may not feel the need to change from the tool they use today.
So what would you do if you were Adobe?
I wonder if Adobe will choose to compete with MadCap in other ways. RoboHelp could become more of an online training, performance support, tool. Also, Adobe could bundle RoboHelp with FrameMaker at a price that makes Flare seem very expensive.
This, of course, may be all academic if the DITA standard isn’t taken up by more authors.