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.
Don't mistake me--I've worked on documents that were several hundred
pages--we used Framemaker.
Had a client that want every user to know everything about every
command and error message in every subsytem in a complex product.
DID manage to reduce 600 pages to 540 by some formatting improvements.
Lost the war to split it into two or more manuals, but always ask
regardless.
Peter Sturgeon
--- John Posada <jposada01 -at- yahoo -dot- com> wrote:
> > 555 pages of System Design, in any application, suggests
> > to me that content is the problem.
>
> Peter...granted, it needs to be a large system, but for some systems,
> 500+ pages does not seem unreasonable.
>
> For instance...I used to work at B&N.com. That application had 11
> identified subsystems, including SAP, several hundred databases, a
> fraud control and credit card verification system, order processing,
> purchasing, front end GUI, etc. When I left, I had over 5,000 pages
> and I was only part way through it.
>
> One person reading the who thing? Not a chance. However, each system
> needed to be represented in the event that someone, such as a DBA or
> a capacity management person needed to see how any particular part
> interacted with others.
>
>
> John Posada
> Senior Technical Writer
>
> "So long and thanks for all the fish."
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Now Shipping -- WebWorks ePublisher Pro for Word! Easily create
> online
> Help. And online anything else. Redesigned interface with a new
> project-based workflow. Try it today!
>http://www.webworks.com/techwr-l
>
> Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
> content and configure Help in MS Word or any HTML editor. No
> proprietary editor! *August release.
>http://www.componentone.com/TECHWRL/DocToHelp2005
>
> ---
> You are currently subscribed to TECHWR-L as prsturgeon -at- yahoo -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
> http://lists.techwr-l.com/mailman/options/techwr-l/prsturgeon%40yahoo.com
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/techwhirl/ for more resources and info.
>
>
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
