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.
Subject:Re: structuring chapters in a book. From:Jim Jones <han4yu3 -at- gmail -dot- com> To:Becca <becca -at- di -dot- org> Date:Fri, 24 May 2013 10:33:51 -0500
How about content or topic?
Intro chapter of the 37 ch book should be all they'd need wrt an intro,
perhaps. Then each of the 37 could be so:
Content
Discussion
References
No summary section.
Jim Jones
communication.openhill.com
On Fri, May 24, 2013 at 9:56 AM, Becca <becca_price -at- yahoo -dot- com> wrote:
> I'm editing a book of 37 chapters, each presented by a different author in
> their area of specialty. I'm supposed to come up with a general chapter
> structure that everyone will be using. This is a highly technical reference
> book that will be used by people studying for a certification exam.
>
>
> What we've got so far is:
>
> Introduction
> <main body>
> Summary
> Discussion Questions
> References
>
> My question is: I need a standard header that can be used for the main
> body of the text. Main Body is out. Any suggestions on how I can
> differentiate between the Introduction and the body of the text?..
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help sample with DISQUS for user commenting?
