For many years I’ve regarded Simplified Technical English as an outdated legacy from the Aerospace industry. But that opinion has changed radically in the last few weeks and I’m becoming a big fan.
In a previous blog I provided lesser known top tips for users of Adobe RoboHelp 11. They were described as “valuable hints learnt by technical writers who attend my Adobe RoboHelp training courses”. And now, back by popular demand, I
Spam; love it or loathe it? This may seem like an odd question. Everybody hates spam don’t they?
“So, Lynne what do you do for a living?” “Oh, I work as a technical author.” “Really? What’s that?” “I write help guides for software applications.” “You must be very clever. I’m useless with computers!”
“What makes a good technical writer?” … a question frequently asked on Armada’s Technical Writing, RoboHelp, FrameMaker and Flare training courses, particularly those relatively new to technical writing. The answer, of course, cannot be both concise and comprehensive, though below
The intention of a technical writer is usually to inform, guide, instruct or perhaps persuade your audience. This requires that the documents you produce are easy to read and interpret by all those who need access to them. They must have
It’s a question we hear sporadically here at Armada on the Technical Writing, RoboHelp, FrameMaker and Flare training courses we run – do we class the profession we’re in as science or art? Are technical authors scientists or artists? Some people
Following on from my recent blog post discussing the use of Plain English by technical authors, I have compiled a list of commonly used technical authoring terms. Have a look and test your knowledge.
Here at Armada HQ we have been working hard on the launch of our latest website. This has involved a number of discussions over the meaning of some of the terms that we use day-to-day in technical authoring. It has