|
|
Posted by Sander Tekelenburg on 04/22/06 04:50
In article <ikki42h7fvruvnf6bvnpaarpd82n8n0v4v@4ax.com>,
firewood <firewood@ironwork.com> wrote:
> I am developing a CMS/web-building website, and I need to include a
> good help system to help my customers learn how to use the features of
> what my project offers.
The best help system is the one that isn't needed. While it is likely
that you'll need to offer *some* help/documentation, don't be the
zilionth developer to use documentation as an excuse to not aim for a
self-explanatory UI.
I realise that's not what you asked for and I realise it's not easy to
achieve. But I do think it's the only 'right' goal to aim for.
[...]
> I want the standard outline system, with a column showing chapters, an
> index, and search box.
Searchability is good to offer, but only if it produces relevant
results. Too often such systems are in practice useless. Personally I
prefer contextual help: provide a mechanism that offers help relating to
the current context, whatever it is.
> Any leads will be greatly appreciated
HTH
--
Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/>
Mac user: "Macs only have 40 viruses, tops!"
PC user: "SEE! Not even the virus writers support Macs!"
Navigation:
[Reply to this message]
|