A derivative came to mind while reading about how worldflows work better than sitemaps at the zurb site.
Normally in end-user documentation the table of contents (Toc) lists the contents at the start. Experienced technical writers often compare a toc with a sitemap, which is again a listing of the contents of a site.
Drawing a parallel from the article, it seems more beneficial to the user to have a Trail of contents (toc) which would explain say how best one could use this user manual or how the user could get more help on a specific query.
I find more value in understanding HOW to work with an interface rather than knowing WHAT is in it.
So would you still advocate a table of contents or have you switched loyalties to a trail of contents?
TOC or TOC?
March 1, 2011 by Sita Bhatt
Advertisement
I would still vouch for Table of Contents
1. For somebody to understand “How to Work” with an Interface, in the first place, you should have the “How to Work” section. TOC just does that – lists what is under the hood.
2. Trail generally means a track or a mark left behind (eg: pug marks) – TWs first develop the TOC (assume you are writing from the scratch for a new product) and then start writing content based on the developed TOC.