Heading names and page titles

Follow these guidelines for authoring headings:

Guidelines Examples
Use sentence-style capitalization for all headings Per Adobe’s standards, headings should use sentence style capitalization.
Example: Create a workspace
However, for guide titles, use headline style capitalization.
Example: Experience Cloud Documentation
Keep headings short A heading isn’t a sentence. Keep page titles short with important keywords at the beginning.
Example: Upload customer attributes
Use nouns or short noun phrases for conceptual, overview headings (and TOC entries) Audiences
Experience Cloud integrations
Use keywords Keywords are feature names and accurate task names (verbs).
Example: Upload customer attribute data to Experience Cloud
This example contains all the keywords to accurately name a task and improve search results.
Create meaningful headings in an active, natural language.
Use infinitive verbs for task headings Run a Fallout report
Use the singular form for task headings Save a workspace
Use sentence style capitalization for all headings Create an audience
Use parallel structures A table of contents (TOC) or list should begin with the same verb or noun phrase. (see Structure and syntax for headings)
Avoid double headings Avoid following a heading with another heading. At least one line of text must separate headings.

Heading structure

Information design typically follows an overview > concept > task hierarchy. In highly structured authoring environments (like DITA), these content types are defined as separate pages or files, which are merged at help-build time. In Markdown authoring, however, you can put these content types natively on the page.

See Content types for a discussion about organizing content on the page.

On this page