Google Wave, the latest tool in development at Google, offers workflow and collaboration capabilities that will be of interest to technical documentation teams. With Google Wave’s open API, there’s the potential for developers of Help Authoring Tools to integrate Wave into its application and into published Help. The first 50 minutes of the video below… Read more »
Cherryleaf Blog
Training Webinars/Webcast events for technical communicators
We would like to invite you to a programme of training Webcast events with us and our colleagues from the TechComm Alliance, where we will share our knowledge and advice that will make you a better technical communicator. We’re putting together a programme of the best speakers we can find – to improve your skills and… Read more »
Feedback on our 1st Documentation Managers/Leaders mentoring meeting
We hosted the first of our peer-group mentoring meetings on Tuesday, and I pleased to say the event went as well as we could have expected. We’ve attended and hosted sessions for other entrepreneurs, but this was our first experience of running such an event for documentation managers. The interactions and the nature of the outcomes… Read more »
TechCommAlliance founded as an international consortium for professional technical communication services
FOR IMMEDIATE RELEASE 26 May, 2009, 12.00 GMT Contact: Ellis Pratt +44 1784 258672 London, UK―Cherryleaf Ltd is joining with Scriptorium Publishing (United States of America) and HyperWrite (Australia) to create the TechComm Alliance. Ellis Pratt, Sales and Marketing Director at Cherryleaf Ltd., commented, “Working with TechComm Alliance means that you’re working with technical communicators… Read more »
Why bother with end user documentation for Web Applications?
In Rahel Bailie’s excellent presentation at the STC Conference (“The New Face of Documentation“), she looked at the “No Documentation” approach to software user assistance. This, she summed up, as the “we don’t document it; we just fix it” view of software development. She argued that a “No Documentation” approach doesn’t lead to no documentation. Users soon… Read more »