Hey, I’m reviewing the Notenik documentation that’s out there, and looking for feedback on a few questions.
First, how useful have you found the following sorts of documentation?
Notenik Tips
Notenik 101 Video
Notenik Intro
Second, I’m thinking about breaking up the Notenik Knowledge Base a bit, primarily to get all the “how to use” stuff in its own document, to make it easier to search and find stuff.
Third, I’m wondering how useful people find the following types of documents:
1. Notenik Tips
Useful. Though I didn’t follow the good advice to make it auto-open. I have read them several times and continue to learn from them. My observation about TIPS is that it is a catch-22 for the beginner. At the outset, having tips presented in the format of the thing which you are wanting to learn is an obstacle. For the intermediate user that obstacle has disappeared but the need for tips has not, so they seem well suited for that audience (me).
2. Notenik 101 Video
Excellent. This was perfectly pitched for someone with no prior knowledge. I was hoping that there were more but it seems as though there is only one.
3. Notenik Intro
Excellent. As a completely new user, I found the web site was a much more comfortable learning environment. The other thing that I noticed was that the organisational structure of Notenik had a strong influence on the website. For consuming information, I found that the level of organisation helpful.
Having a compendium resource like the knowledge base is invaluable. However, the sheer size of it then makes it unwieldy, especially as search is linear, from the front.
Recently I was unable to locate the information about using #PATH#. I knew I had seen something about it but I didn’t find it. After you provided the information I looked again. Searching for the keyword “path”, it took a long time to get to the section on scripting that contained the information I needed. I imagine that a splitting the information up into sections would alleviate this to some extent.
I think you’ve placed them in exactly the right order. Text is a great way to transmit information. Screenshots illustrating the text improves the communication enormously. Videos are even better, as they reduce the cognitive load of the learner. They are easily the richest source of information and the easiest to consume when learning. Having said that, when reviewing a topic, or wanting documentation on a topic, text/image based materials are usually easier to access than video.
I know how much effort is required to produce good training content, especially videos! I’m very grateful, and impressed by the amount of content that you are able to provide.
I mainly use the Notenik Knowledge Base which is an excellent compendium of information about the software. I am not a great fan of multiple levels of indentation. Take for example Derived Variables (‘slugs’)—see screenshot. I know nothing about slugs but the left-hand pane in the knowledge Base is not so easy to navigate because of the multiple levels compared to the right-hand pane where I can easily see that there are 11 types of slugs. But this is a minor quibble. I also wonder whether it is necessary to have the complete version history in Section 19 and whether it would be better to be moved to a separate listing.
But none of these comments detract from the quality of Herb’s software and its documentation.
