Chunking information (Was: multiple TWs for a project)

Subject: Chunking information (Was: multiple TWs for a project)
From: Jean Weber <jean -at- wrevenge -dot- com -dot- au>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Sat, 12 Feb 2000 17:08:02 +1000

Tony's use of the word "chunking" is the meaning I'm familiar with. Such "chunked" information can then become "chunks" in the presentation and layout sense. This use of the term (logical chunks rather than visual chunks) may be more apparent when writing online help, where the chunks of information must be able to stand alone, because you don't know in what order someone will read them.

In such a project, it's relatively easy to parcel out chunks of the work to different writers -- but planning, coordination and good editing is essential. I haven't been following this thread closely, so I'm not sure what "dependencies" Tony is talking about, but two I can think of are consistency of terminology and writing style, so that users can develop expectations of what they will find where in a help topic, and what the various *things* in the product are called.

Regards, Jean
Jean Hollis Weber
mailto:jean -at- wrevenge -dot- com -dot- au
The Technical Editors' Eyrie
Avalook at Australia Travel site:

At 02:16 2/11/00 -0500, Bonnie Granat wrote:

>Tony Markatos responds:
>The logical way to chunk (break into smaller pieces) procedural information
>is by task. In this way the dependencies between the chunks are minimized.
Is your use of the word common? "Chunking" in my experience is about
presentation and layout only. Rather than repeat my initial comment, please
read it again.

Bonnie Granat

Previous by Author: Re: HTML > PDF
Next by Author: Re: Electronic grammar-checker
Previous by Thread: Documenting Data Center Operations
Next by Thread: Re: Chunking information (Was: multiple TWs for a project)

What this post helpful? Share it with friends and colleagues:

Sponsored Ads