Skip to main content

 

  • arrow icon
Language Selector

  1. Other Languages

    (machine translation)

Planview Customer Success Center

Template guidelines

  1. Last updated
  2. Save as PDF

This documentation outlines the key standards and requirements for creating or duplicating guides across different template formats. Follow these guidelines to ensure consistency, accessibility, and readability across all user-facing guides.


Global guidelines

Across all Pendo-created templates

Accessibility standards Readability standards User Experience standards

All guides must meet keyboard accessibility requirements:

  • Focusable via Tab key navigation
  • Proper tabindex and ARIA attributes
  • Activation via both Enter and Space keys
  • Role attributes properly set

 
  • Always left-align instructional content
  • Keep headings concise and brief
  • Use emojis purposefully to support meaning, not for decoration
  • Maintain consistent emoji placement across similar guides
  •  Provide multiple dismissal options
  • Avoid blocking critical UI elements
  • Match product UI labels exactly in instructions
  • Structure content with purpose/value before action


Guide-specific guidelines

Based on template type



Forms/Polls

Collect structured user input within the product experience.
 



Notification/Informational messages

Communicate important information without requiring user interaction to proceed.

 


Walkthroughs

Step-based interaction designed to guide users through a defined sequence of actions.

 


Pop-ups/Badges

Contextual, anchored UI elements designed to draw attention to a specific feature, action, or change within the interface.

 

 

 

           

Forms/Polls

 

Poll.jpg

Purpose

Designed to collect structured user input within the product.
Key requirements
Headings
  • Use H1 level for primary heading
  • Use H2 for any subheadings
  • Keep headings concise and brief

Alignment
  • Left-align: Headers, Body text
  • Right-align: Buttons/Actions
  • Avoid centered paragraph text as it reduces readability for instructional content

Content structure
  • Lead with purpose/value, then state the action
  • Limit to 1-2 short sentences total
  • Use direct action sentences

Emoji usage
  • Limit to ONE emoji at H1 level only
  • Place emoji either before OR after header text (maintain consistency—don't alternate placement)
  • Do not use emojis in body paragraphs, navigation buttons, or instructional steps
Form fields Adhere to template guidelines allowing width to fill the body of the element

 

           

           

Notification/Informational messages

 

Poll.jpg

Purpose
Communicate important information without requiring user interaction to proceed.
Key requirements
Headings
  • Use H1 level for primary heading
  • Keep headings concise and brief

Alignment
  • Left-align: Headers, Body text
  • Right-align: Buttons/Actions (if applicable)
  • Avoid centered paragraph text as it reduces readability for instructional content

Content structure
  • Lead with purpose, then state the associated details
  • Limit to 1-2 short sentences total
  • Use direct action sentences
  • If using a salutory remark, bold text for consistency

Emoji usage
  • Limit to ONE emoji at H1 level only
  • Place emoji either before OR after header text (maintain consistency—don't alternate placement)
  • Do not use emojis in body paragraphs, navigation buttons, or instructional steps
  • Limit to one emoji at H1 level only
  • Place emoji either before the header text OR after the header text
  • Do not alternate placement across guides
  • Do not use emojis inside body paragraphs, navigation buttons, or instructional steps
  • Emojis must support meaning (e.g., success, warning, celebration), not decoration
Form fields Adhere to template guidelines allowing width to fill the body of the element