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.
Best practice for technical documentation page length on a website?
Subject:Best practice for technical documentation page length on a website? From:procrastiwriter <procrastiwriter -at- googlemail -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Thu, 26 Jul 2007 16:45:09 +0100
I'm looking for some advice with something I've been pondering for a while.
I'm working for a company where all documentation was transferred from CHM
files, to a website - I joined just as the migration happened.
Within the original CHM files, the tendency was to have a fairly 'deep'
table of contents and often lots of relatively short pages within each
section. This same structure was transferred to the website.
Understandably, some people are complaining that it takes too long to drill
down and find information, and I agree that many of the sections could be
combined into a single page (many pages are no more than a paragraph long).
I'm comfortable with this, but in the back of my mind I have the words of a
web developer ringing in my ears from years ago - "web users don't like
scrolling, pages should be short and snappy".
Now, this was some time ago, and I suspect that attitudes have changed,
particularly with the advent of wikis, etc. I also feel that there is a
significant difference between writing "short, snappy" pages for a standard
website, and writing pages that contain technical documentation.
I will obviously seek the views of people who use the documentation before I
make major changes, but I'm just wondering if anyone is aware of a 'best
practice' for this. What would you do if you had six separate pages of
technical documentation that could (logically) be combined into one, long
web page that would require multiple scrolls to read?
Thanks in advance.
P.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-