LiteHelp is a lightweight non-HTML portable help system for Windows intended to be CHM (HTML Help) replacement, or, at least, alternative. I created it becuase my clients had numerous problems with online help in CHM format. It is long abandoned by Microsoft and ever since continues to grow security issues like a snowball.
I thought to myself: “What the hell, it’s 2019, we don’t need all those fancy HTML bells and whistles anymore. The content is what matters and markdown popularity shows it best”. So I decided to put together somewhat shelved help viewer project and my recent developments in Helpinator and create a help system of my dreams with just enough features and nothing more.
The viewer itself resembles that of HTML Help – a pane with 3 tabs on the left (Table of Contents, Index, Search) and content display area at the right. The only question was what component to use for content rendering but actually it was not much of a question since my code base is heavily dependent on excellent TRichView component from Sergei Tkachenko.
OK, yes, we do not need all that versatality, but we still need some cool things to let our users understand things we talk about faster. If you take a look at modern technical writing it’s not mostly about writing but about structured authoring. Specilized content items are what matters now, and I decided to follow that approach too. Helpinator was based on this approach from the start and in recent versions the number of content items even increased. So far we have:
- Regular text items with basic formatting – nothing fancy here
- Tables – OK, everybody need them
- Figures – this is not just a picture, but a picture with a title and formatted in the output accordingly
- Asides/admonitions – that colored paragraphs with title and icons intended to bring reader’s attention to.
- Code samples – need to have syntax highlight
- Step-by-step guides – not very common item, but it built into Helpinator for a long time already. Also DITA has a similar element.
- Videos – both embeddable (Youtube/Vimeo) and local
- FAQs. Though FAQs can be just plain formatted text it’s more convinient to render them as collapsible sections if the output format supports such dynamics.
- Quizzes. Not that all necessary element, but learning assessment is important part of technical documentation nowdays.
- Glossary of terms used in documentation.
I managed to implement them all in LiteHelp, so, yes, it’s a very cool help system.
Another feature to be noted is language support. LiteHelp format allows to store all content in one project, and it is possible to switch languages both programmatically and manually by user actions.