Re: structuring chapters in a book.

Subject: Re: structuring chapters in a book.
From: Jim Jones <han4yu3 -at- gmail -dot- com>
To: Becca <becca -at- di -dot- org>, Techwr-l <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 24 May 2013 11:25:39 -0500

Not really - Each of the 37 ch would have its "Topic" and then just go into
the content section, without calling it anything.

Follow this with a named Discussion section.

The refs section would not need to have a title.

So the book would be:

Front matter, intro, 37 ch, glossary, index etc.

Each ch: Topic [A heading], content pages, Discussion [D heading],
discussion pages ...

Jim Jones

communication.openhill.com

On Fri, May 24, 2013 at 11:00 AM, Becca <becca_price -at- yahoo -dot- com> wrote:


Would you have a level 1 head that says "Content"?
>
>
> Regards,
> Becca
> _________________________
> There's no such thing as useless information; only information I haven't
> used yet.
>
> ------------------------------
> *From:* Jim Jones <han4yu3 -at- gmail -dot- com>
> *To:* Becca <becca -at- di -dot- org>
> *Cc:* tech2wr-l <techwr-l -at- lists -dot- techwr-l -dot- com>
> *Sent:* Friday, May 24, 2013 11:33 AM
> *Subject:* Re: structuring chapters in a book.
>
> 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?
>
> Learn more: http://bit.ly/13xpg5n
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as becca_price -at- yahoo -dot- com -dot-
>
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
> http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
>
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help sample with DISQUS for user commenting?

Learn more: http://bit.ly/13xpg5n

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


References:
structuring chapters in a book.: From: Becca
Re: structuring chapters in a book.: From: Jim Jones

Previous by Author: Re: structuring chapters in a book.
Next by Author: Re: Articulating and Establishing a Vision for Technical Publications
Previous by Thread: Re: structuring chapters in a book.
Next by Thread: TechWhirl: Technical Communication Recap for May 24, 2013


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

Sponsored Ads


Sponsored Ads