test issue to see how MR handles branch selection
Change content in the handbook
The handbook page for something needs to change.
Suggesting a change
Identify The Five W's : who, what, when, where, and why.
Apply MoSCoW sorting to your requests (must, should, could, won't).
What is/are the expected URL(s)
Does this match existing strategies? Has keyword research been done?
Briefly describe the page/flow
(Example: Access to the accounting system requires submitting requests for accounts and tools, etc.)
If applicable, do you have any user journeys, wireframes, prototypes, content/data?
(Example: Paste image into the description, link to Google doc/sheet, balsamiq, etc)
What is the primary purpose of this page/flow?
(Example: Clarify qualifications for activity)
What are the KPI (Key Performance Indicators)
(Example: Premium signups per month as identified by Periscope dashboard URL)
What other purposes does this page/flow serve, if any?
(Example: Capture emails for campaign funnels)
What information is this page/flow trying to convey?
(Example: Forrester says GitLab is great)
Who is the primary audience? Be specific.
(Example: Potential customers vs developers vs CTO vs Jenkins users)
Any other audiences?
(Example: Media outlets, investors, etc)
Where do you expect traffic to come from?
(Example: Homepage direct link, on-site blog post, social media campaign, targeted ads)
If applicable, are there any items which can be hidden at first glance but still need to be present?
(Example: Tooltips, tabbed sections, collapsible sections, filterable items, different view-type toggles, view-more buttons, extra data)
Please provide some example websites for design guidance.
(Example: "Pinterest implements recommendations well", "Stripe has good payment UX", "I like the aesthetics of nike.com", animation examples, microinteractions, etc)
Does this page/flow require any events, parameters, or tracking?
(Example: Clicking button X should record a purchase into analytics)
Does this page/flow impact or need any reports?
(Example: This impacts the Retention dashboard in Periscope)
Does this page/flow require any automation?
(Example: Create a test ensuring a job listing is never empty)