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.
One exception to that rule: I use single child topics for
internal-only notes on the parent topic to be included in
for-internal-distribution-only version of the docs and excluded from
customer docs. That makes the internal-only topics appear in the TOC /
page nav / PDF bookmarks so they're more obvious.
On Wed, Oct 28, 2015 at 7:25 PM, Sean Brierley
<sean -dot- brierley -at- gerberscientific -dot- com> wrote:
> And, to add more thought about your approach in addition to what Fred said,
> avoid solo headings. Headings should exist at least in pairs at any given
> level.
>
> If you only need a single level-3 heading, get rid of it and include its
> content in the preceding level-2 section. Perhaps you might have to modify
> the level-2 section heading to accommodate the added content.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
