Updated footer to include gartner content
Step 1: What is changing in this MR?
- Implement https://www.figma.com/file/SdaAIN4UcEQmUrysWj8mAi/Gartner-Report-Experience?type=design&node-id=127-2419&t=htcWhetP9WeJtrCZ-0 in Figma
Removepackage-lock.json
from the repo as we should stick to only one package manager.- run
yarn
off a freshmain
- I noticed a lot of the
yarn.lock
file being rebuilt, so maybe I did something wrong? I might include that in a different MR
- I noticed a lot of the
This content is set to only be visible on the English version of the site. I put a v-if
setting that up. The reviewer should verify that these changes only work on the English site.
I believe we are still waiting on @trevor-storey's stakeholder to see if we can actually do what we want to do here in the MR
Step 2: Ensure that your changes comply with the following, where applicable:
-
I, the Assignee, have run Axe tools on any updated pages, and fixed the relevant accessibility issues. -
These changes meet a specific OKR or item in our Quarterly Plan. -
These changes work on both Safari, Chrome, and Firefox. -
These changes have been reviewed for Visual Quality Assurance and Functional Quality Assurance on Mobile, Desktop, and Tablet. -
These changes work with our Google Analytics and SEO tools. -
These changes have been documented as expected.
Step 3: Add the appropriate labels for triage
This MR will have dex-approval::2-standard
automatically applied, but please update it as follows. If deciding between two levels, go with the higher of the two: https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/sites/handbook/source/handbook/marketing/digital-experience/marketing-site-approval-process/index.html.md
Step 4: Tag the appropriate person for review
Depending on which label is used, you may tag the following people as a Reviewer
on this MR: https://about.gitlab.com/handbook/marketing/digital-experience/marketing-site-approval-process/#step-3-tag-the-appropriate-people-for-review
Closes #134 (closed)