Microguide

Use the Microguide to guide users through features or functionality in small steps, supporting onboarding of new users and the introduction of new features.

OverviewPropertiesUsage

When to use

• To guide users through a feature or functionality in small steps without interrupting their workflow.
• When introducing new users to a feature or walking existing users through a new capability.

When not to use

• When the guidance is a one-time spotlight on a single interface element. Use FeatureHighlight instead.

Read about more Microguide best practices in Guided interaction.

Content guidelines

General

• Use sentence case in titles and body text.
• In the body text, all sentences get periods.
• Titles don't get periods.

Message content

• The title should give the user the most important information or action to take. Use an action verb to describe the action.
• The body text should give just the essential information about the concept, feature, or functionality.
• Keep the body text to a maximum of two sentences. Remove any words that can be removed without altering the meaning. Concise explanations help users scan and retain information.
• Avoid jargon or technical terms that could confuse new users. If you need to include a technical term or jargon, include a link for easy reference.
• When adding links, try to put the linked text at the end of the content so it doesn't break the reading flow.