Conceptual h1 |h1|

Leap straight into the introduction. Don't include a second heading after the topic heading. In the introduction

Explain the concept that underlies the topic. This often involves using boilerplate wording and key phrases that get repeated throughout a section devoted to a single concept. Try not to quote other topics verbatim, but worry more about consistency than originality.

Outline the facets of the concept the topic covers. Do this in the order they occur in the topic.

Heading 1 |h2|

When creating the heading:

The following guidelines are a general roadmap for crafting a section. These are not hard-and-fast rules, but rather are designed to get you going.

There are exceptions in terms of length and importance, of course, but each section should be able to answer the what, why, and how questions.

Heading 2 |h3|

For second- or third-level headings:

Because second- and third-tier sections are subordinate to sections that explain a concept thoroughly, they allow you to assume slightly more about what the user already knows. So you can be more frugal with the what and the why parts. This doesn’t mean you can skip ‘em necessarily, it just means you can assume more. Otherwise, the same guidelines apply to these as to the first-level sections.

Related Topics |relatedtopics|

Designing a Database Control

Using a Timer Control


Still need help? Post a question on the Workshop newsgroup.