Headings and page names headings

Do not punctuate a heading like a sentence. Punctuation exists only to remove confusion (such as a period to separate sentences).

Exceptions:

Use a question mark only if the heading asks a question (such as in an FAQ).

Certain creative, marketing style headings may need punctuation (to avoid a sentence splice)

Maintain a parallel structure whenever creating scannable content. Headings, like lists, should be parallel in most cases.

For example, on a page with several headings for concepts and tasks, use noun phrases for all first-level headings, verb phrases for second-level headings, and infinitive phrases for headings preceding a procedure.

Avoid multinoun concept headings.

Difficult: Adobe Photoshop layers video playlist

Simple: Video playlist for Photoshop layers

Avoid multiverb tasks headings.

Difficult: Create, edit, and upload customer attributes

Simple: Manage customer attributes

Keywords improve SEO. They include feature names, interface elements, and the task being performed.

Example: Upload customer attributes contains action performed in the interface.

Consistent use of the singular form is easier to read.

Example: Save a workspace (not Save workspaces)

Localization must be able to translate all headings, so show restraint regarding informal headings or jargon. Product documentation must follow this guidance.

Videos (and events) that feature personalities have more room to be slightly creative and informal, but not overly so.

• Introduction to Adobe Target
• Introduction to Adobe Experience Manager 6.4

Introductions present a new product and generally describe what it does at a high level. Your guide should include only one introduction, placed at the beginning of the guide where new customers see it. (Not to be confused with overview.)

Never use the single word Introduction by itself in a heading.

• Overview of Adobe Analytics
• Overview of Analytics segmentation

Overviews describe multiple or single features, how products and features work together, and what you can accomplish using the product.

Important: Never name a page Overview without naming what the overview is about.

Do not name a landing page Overview. If you must describe the purpose of your guide on its landing page, use an About this guide subheading and describe it there.

• Analytics Tutorials
• Campaign v8 Tutorials
• Tutorials for XML Documentation for AEM
• Analytics Tutorials and Videos

Use What’s new headings to introduce new features in a product release. Use the product name with What’s new headings. These headings differ from release notes, which provide features and fixes in a release.

Do not add a question mark after this heading.

Adobe Campaign integration with Adobe Experience Manager

Integrate Adobe Campaign and Experience Manager

This heading is automatically added at the bottom of a page (assuming that the Recommendations feature is enabled by SCCM). A bullet list of recommended articles is also added.

Ensure that your H1 headings adhere to capitalization standards, and that you have feature tagging correctly set up for this feature to work.

The Recommendations feature pulls in the H1 from other pages and creates a bullet list. If the H1 being fetched is Overview or Introduction (only one word), the list of recommendations will not make sense.