Skip to main content

Planning a User Guide - Part 4/5 - Get Your Toolbox Together


Photo by Fleur Treurniet on Unsplash


In the previous post, I had discussed how to organize the team for creating your software's user manual. With the team ready, the next step is to select the tools.

Working with the right technical writing tools is as important in technical writing as it is in building software. The right tools will help you be more organized, productive, and accurate in your work. 

In software, we use an IDEs, testing tools, and version control tools to manage our work. In technical writing, at a bare minimum, we use a content authoring tool, an automated grammar checker, and visual tools to assist us in our work. 

I'll discuss various tools that are available in the market, link to comparisons, and share my opinion to help you make the right choice.

Help Authoring Tools

A Help Authoring Tool (HAT) offers several features that go beyond simple word processing software for writing technical documents. HATs support publishing the content in multiple formats, responsive design for different devices, indexing, single-sourcing, and context-sensitive features. 

Here are a few popular Help Authoring Tools:
  1. Adobe RoboHelp
  2. Author-it
  3. ComponentOne Doc-To-Help
  4. EC Software Help and Manual
  5. MadCap Flare
  6. Dr. Explain
Even though HATs are useful, I have yet to come across a small/mid-sized software company that uses them. It's because, at most small companies, it is the developers who write the first version of their technical manual. Using a HAT cuts on two sides: first the company has to pay a rather steep fee for using the HAT, and second, the developers will have to invest time in learning the software. Both money and time are at a premium in small organizations and their requirements are usually sufficiently fulfilled by MS Word or Google Docs.

It doesn't mean that HATs are not useful. If you feel that the features that a HAT offers will add significant value to your product, then I recommend that you read through the posts I have linked below to get an understanding of how they compare before making a purchase decision.


Automated Grammar Checker

An automated grammar checker is an invaluable tool for all writers. There are several automated grammar checkers on the market. Most have a freemium model where the free version at the very least corrects punctuation errors and basic grammatical mistakes and the paid version corrects more advanced grammatical issues and other issues related to sentence construction, readability, and plagiarism. Some software will also help you enhance your vocabulary - which is super awesome.

I personally use the free editions of both Grammarly and ProWritingAid.

Grammarly is great at detecting punctuation and basic grammatical mistakes. Also, Grammarly's free Chrome plugin totally rocks. It's a huge help when I compose emails in the browser or when I write blog posts. The only downside is that the plugin does not support Google Docs.  

ProWritingAid's free version which runs on a web interface is very intuitive and easy to use. It gives a great summary of the analyzed text, offers readability checks, checks for cliches, overused words, and several other features. Unfortunately, they include the browser plugin only in the paid version.

I suggest that you begin with the free versions of ProWritingAid and Grammarly. They may be all you need for working on a technical manual. 


Visual Tools

From the perspective of writing software user manuals, the most important visual tools are screen capturing software (to capture screenshots) and image editing software (to do minor edits to the screenshots). 

There are many free as well as paid screen capturing software available on the market. Here's a list of ten best screen capture software for 2018. I personally use the free version of Jing and am very happy with it.

Once you have the screenshots, you might want to do minor edits to highlight certain parts of the screen. Jing (and other screen capture software as well) will allow you to make highlights, circles, etc, but I don't like the quality much. I prefer to use a proper image editor. 

Online image editors work best since they do not require installation and some even have team features. Here's a list of great online image editors.
Labels:

Comments

Post a Comment

Popular posts from this blog

Inheritance vs. composition depending on how much is same and how much differs

I am reading the excellent Django book right now. In the 4th chapter on Django templates , there is an example of includes and inheritance in Django templates. Without going into details about Django templates, the include is very similar to composition where we can include the text of another template for evaluation. Inheritance in Django templates works in a way similar to object inheritance. Django templates can specify certain blocks which can be redefined in subtemplates. The subtemplates use the rest of the parent template as is. Now we have all learned that inheritance is used when we have a is-a relationship between classes, and composition is used when we have a contains-a relationship. This is absolutely right, but while reading about Django templates, I just realized another pattern in these relationships. This is really simple and perhaps many of you may have already have had this insight... We use inheritance when we want to allow reuse of the bulk of one object in other ...
3 comments
Read more

Commenting your code

Comments are an integral part of any program, even though they do not contribute to the logic. Appropriate comments add to the maintainability of a software. I have heard developers complain about not remembering the logic of some code they wrote a few months back. Can you imagine how difficult it can be to understand programs written by others, when we sometimes find it hard to understand our own code. It is a nightmare to maintain programs that are not appropriately commented. Java classes should contain comments at various levels. There are two types of comments; implementation comments and documentation comments. Implementation comments usually explain design desicisions, or a particularly intricate peice of code. If you find the need to make a lot of implementation comments, then it may signal overly complex code. Documentation comments usually describe the API of a program, they are meant for developers who are going to use your classes. All classes, methods and variables ...
Post a Comment
Read more

Running your own one person company

Recently there was a post on PuneTech on mom's re-entering the IT work force after a break. Two of the biggest concerns mentioned were : Coping with vast advances (changes) in the IT landscape Balancing work and family responsibilities Since I have been running a one person company for a good amount of time, I suggested that as an option. In this post I will discuss various aspects of running a one person company. Advantages: You have full control of your time. You can choose to spend as much or as little time as you would like. There is also a good chance that you will be able to decide when you want to spend that time. You get to work on something that you enjoy doing. Tremendous work satisfaction. You have the option of working from home. Disadvantages: It can take a little while for the work to get set, so you may not be able to see revenues for some time. It takes a huge amount of discipline to work without a boss, and without deadlines. You will not get the benefits (insuranc...
10 comments
Read more