Recently, I’ve been considering my style of writing style. One of the things most of us are taught when we first become technical authors is that a user/reader shouldn’t be able to tell which technical author wrote the help or
At Armada we are very proud of our success rate in winning new business. Read our case study on a client requiring an online help solution.
Spam; love it or loathe it? This may seem like an odd question. Everybody hates spam don’t they?
Our client, Staffcare, developed a flexible software solution (also called Staffcare) for managing organisation’s HR, benefits and payroll data. Armada was commissioned to create a full user documentation set for System Administrators comprised of two formats: web-enabled online help PDF user
New software that creates documentation in all formats at the press of a button. The single sourcing revolution is here.
A huge part of what makes a technical writer’s documentation successful isn’t just that it is easy to read, but that it is also easy to search and find the information that you are looking for. Searchability nowadays isn’t just
I have worked as a technical author for nearly four years and have had to climb a steep learning curve. Today I am going to share with you a few of the common problems that I have encountered along the
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
U2 launched their latest album this week. ‘Songs of Innocence’ launched alongside Apple’s new iPhone 6. We all love a new Apple product in time for Christmas. As an added bonus, or not, your album is automatically listed on your