Skip to content
logo
Percona Documentation Style Guide
Callouts and admonitions
Initializing search
    percona/doc-style-guide
    percona/doc-style-guide
    • Home
    • Storytelling
      • Voice and Tone
      • Keep the Structure Simple
      • Use Cross-References Appropriately
    • Text
      • Hyphens
      • Paragraphs
      • Lists
      • Headings
      • Tables
      • Graphics
      • Callouts and admonitions
        • Rules
        • When to use the callout
      • Code descriptions
      • SQL statement conventions
      • Links
      • Legal information
      • None
    • Grammar
      • Capitalization
      • Punctuation
      • Spelling
      • Word usage
      • Numbers
    • Writing
      • Rules for specific documentation types
    • Guidelines
    • Markup
    • Copyright and licensing
    • Trademark policy
    • Rules
    • When to use the callout

    Callouts and admonitions¶

    Callouts emphasize important or helpful information that is not part of the text flow. Readers may skip callouts since they are outside of the paragraph. To test if something should be a note or warning, write the text first as part of the paragraph and then decide if you need to make the information a callout.

    Do not use too many callouts. When you use too many notes they lose their effectiveness and blend into the other information.

    Do not use a callout that provides information that the user needs to succeed with the task.

    The following callouts are used:

    Name Description
    Tip Provides helpful suggestions or useful information to improve user experience or provide alternative ways of doing something
    Important Provides essential points to complete a task or understand a topic
    Warning or Caution Highlight critical information that users must be aware of to avoid data loss, system misbehavior, etc.
    Note or Info Provides information to supplement the main idea and /or help users better understand the topic. Also provides information that applies in certain cases
    See also Provides additional materials (common cases, deeper context) that are related to the preceding text.
    Example Highlights examples

    Rules¶

    • Separate callouts with text paragraphs
    • Don’t group callouts together. Reorganize the content.
    • Avoid using a code-block inside callouts

    When to use the callout¶

    Create a callout when:

    • The information is not necessary for what the user is doing. Even if the user skips the information in the callout, the task succeeds.

    • The information is outside of the flow of the task.

    Contact Us

    For free technical help, visit the Percona Community Forum.

    To report bugs or submit feature requests, open a JIRA ticket.

    For paid support and managed or consulting services , contact Percona Sales.


    Last update: June 26, 2023
    Created: June 26, 2023
    Percona LLC and/or its affiliates, © 2023
    Made with Material for MkDocs

    Cookie consent

    We use cookies to recognize your repeated visits and preferences, as well as to measure the effectiveness of our documentation and whether users find what they're searching for. With your consent, you're helping us to make our documentation better. Read more about Percona Cookie Policy.