Skip to content

Resolve "Phase 2 Website Update - why/"

Erica requested to merge 8471-phase-2-website-update-why into master

🗺 Overview

This MR is to update the /why/ page.

#8471 (closed)

👀 Changelog

  1. Adds an H2 to the hero
  2. Updates the hero button copy
  3. Moves the what section above the social proof section.
  4. Updates the what section copy
  5. Adds a why section -- this may be out of scope.
  6. Adds a case study to the social proof section -- this may be out of scope
  7. Moves the Bridging silos section above the benefits section
  8. Removes the Taking work out of your hands and The Goal sections
  9. Adds a Free Trial module to the bottom of the page

Copy Document


This checklist is based on the Growth Marketing Team's documentation for reviewing merge requests.

  • UX research has been done that supports this MR.
  • This MR has been reviewed for accessibility best practices.
  • This MR maintains the single-source-of-truth principle (SSOT).
  • This MR has been through SEO review.
  • This MR has been reviewed for security best practices.
  • If applicable, automation has been updated or created and operates as expected.
  • All blank-states are accounted for.
  • All interaction states have been tested (before, during, after).
  • All images, PDFs, and other files have been optimized and follow our image guidelines.
  • Conversion best practices have been followed.
  • All items necessary to measure conversion impact have been accounted for.
  • All other guidelines have been taken under advisement.
  • You have searched for any pages using the updated files to ensure those pages won't be negatively impacted by these changes (ie regression tests).
  • The impact of this MR on site speed has been recorded below.
  • This page behaves as expected in all supported browsers (Chrome [Blink], Safari [Webkit], and Firefox[Gecko]).
  • This page behaves as expected on phone, tablet, laptop, and desktop screen sizes.
  • This MR works on a touchscreen (ie important information isn't contained solely within hover events).
  • This MR works with cookiebot.
  • All console logs have been disabled before releasing to production.
  • All buttons and links go to where they're supposed to go.
  • Relevant codeowners and stakeholders have reviewed the MR.
Edited by Stephen Karpeles

Merge request reports