Salesforce Style Guide for Documentation and User Interface Text
j
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Titles and Headings
Title and heading styles depend on whether you are writing a concept, task, or reference topic. For title capitalization styles, see Capitalization.
Overview Titles
An overview is a topic focused entirely on conceptual information. Use the format: <X> Overview. For example: Cases Overview. Don't use Managing <X>, Working with <X>, What is <X>?, or About <X>.
Task Titles and Stems
- Use an imperative verb instead of a gerund for task titles. For example, use “Add Users” instead of “Adding Users” and “Create a Custom Field”, not “Creating Custom Fields”.
- Use a title that describes the customer’s goal, not the UI task, whenever possible. For example, the title “Create a Custom Object” for a task about creating custom objects is better than something more generic. Don’t use broad phrases like “Create the Infrastructure to Store Your Data”.
- Don't add an introductory phrase (also known as a stem) to a task or table that appears soon after a topic’s title. For example, a set of steps that immediately follows the title Editing a File does not need the introductory phrase “To edit a file:”. If you include only essential introductory content in a task, you’ll never need a stem.