TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
The only time documentation is required for a wizard is when you have
an unusable one that a pointy-haired manager won't let you fix.
A real wizard is, by definition, self-documenting. If there's anything
documentation could add that''s not on screen, it must be added to the
wizard. As Hannah made clear in follow-up posts she wrote the wizard
text and put everything in there.
One place I worked I inherited a project where my predecessors had
actually written a context-sensitive help topic for every page of
every wizard that simply repeated what was on that page. There were
around 60 topics that had nothing but a screen shot of the last page
of various wizards with the instruction, "Click Finish."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help 2014 v1 now available. SharePoint 2013 support, NetHelp enhancements, and more. Read all about it.
