Salesforce Style Guide for Documentation and User Interface Text

Below you will find brief information for the Salesforce Style Guide for Documentation and User Interface Text Winter '17. This comprehensive guide provides essential terminology and usage guidelines for creating consistent, professional, and easy-to-learn user interface text and customer-facing documentation materials across Salesforce applications.

PDF
Document
Salesforce Style Guide for Docs Winter '17 | AI Chat & PDF | Manualzz

Advertisement

Advertisement

/

Advertisement

Key features

  • Provides terminology and usage guidelines for UI text and documentation.

  • Ensures consistent style and usage across materials.

  • Facilitates professional-looking documents and user interface text.

  • Aids users in learning the Salesforce system faster and more efficiently.

  • Serves as an alphabetical reference for grammar and usage rules.

  • Includes definitions and usage of Salesforce-specific terms.

  • Designed for technical writers, curriculum developers, trainers, and product managers.

Frequently asked questions

The primary purpose of this guide is to provide terminology and usage guidelines for user interface text and customer-facing documentation, ensuring consistency, professionalism, and ease of learning for Salesforce users.

This guide is intended for anyone who builds applications or creates instructional and reference materials for Salesforce, including technical writers, curriculum developers, trainers, editors, product managers, developers, and user experience professionals.

For general style issues, you can refer to The Chicago Manual of Style and the Microsoft Manual of Style for Technical Publications. For spelling questions, dictionary.reference.com (based on the Random House Unabridged Dictionary) is recommended.

The first time you use an acronym or abbreviation, spell out the full word or phrase and follow it with the shortened form in parentheses. Use the acronym or abbreviation in all subsequent references. In long manuals, repeat this for each new topic.

Button names should use title capitalization, such as 'Clone' or 'Run Report', and should not include ending punctuation.

Preparing document for printing…
0%