Add demandbase to navigation
Step 1: What is changing in this MR?
This is a proof of concept MR that shows a variation of the navigation based on the audience/segment that a user is categorized in by DemandBase. This MR works by getting the audience, then updating css
classes in the top level navigation. If we want to start changing the order of content, it will require updates to the JSON files accordingly.
Note: If this MR is merged and released, it will make real changes to the navigation for different audiences. We should discuss these changes or revert them before merging (reverted)
We can test each variation by appending a query string to the url.
- For enterprise, append
?audience=enterprise
(review app) - For SMB, append
?audience=smb
(review app)
enterprise | smb |
---|---|
![]() |
![]() |
Review app | Review app |
This nav has three different variations: (reverted, added css class "enterprise" or "smb" to top level nav css)
Category | Description of change | Screenshot |
---|---|---|
Enterprise | updated the dropdown category heads to be black | ![]() |
SMB | category headers are purple | ![]() |
Default | category headers are purple | ![]() |
Closes: buyer-experience#1922 (closed)
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:
-
dex-approval::1-minor
-
Example of the type of change: typos or content changes.
- Anyone on the Digital Experience team can approve and merge.
- Once approved by the Digital Experience team, the MR creator can merge.
-
Example of the type of change: /customers filter is displaying the wrong results.
- Anyone on the Digital Experience team can approve and merge.
- Once approved by the Digital Experience team, the MR creator can merge.
-
Example of the type of change: typos or content changes.
-
dex-approval::2-standard
-
Example of the type of change: re-arranging components on a page.
- Once the Digital Experience team approves, members of the Digital Experience team can merge.
- Members of the Digital Experience team should keep their Managers informed.
- Manager’s discretion to align with the Director of Digital Experience or not.
-
Example of the type of change: Adding new pages.
- Managers of Digital Experience can approve and merge.
- Manager should align with Director, Digital Experience.
-
Example of the type of change: re-arranging components on a page.
-
dex-approval::3-key-page
-
Example of the type of change: Changing Nav
- Directors and Managers of Digital Experience need to align.
- Managers of Digital Experience can approve and merge.
-
Example of the type of change: Changes to key drivers of traffic and/or business goals etc. (Homepage, Pricing Page, Why GitLab).
- Director, Digital Experience can approve and merge.
- Director, Digital Experience will keep Marketing leadership informed of all Major Changes.
-
Example of the type of change: Changing Nav
-
dex-approval::4-legal
-
Example of the type of change: Any changes to company information, board/director information, etc.
- Legal and Director of Digital Experience must approve.
-
Example of the type of change: Changes to sign-up workflows or alteration/omission of footers/links to anything legal-related.
- Legal and Director of Digital Experience must approve.
-
Example of the type of change: Any changes to company information, board/director information, etc.
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:
- Level 1: Any member of the Digital Experience Team
- Level 2: Any member of the Digital Experience team
-
Level 3: Ping
@gitlab-com/marketing/digital-experience
in a comment. This will tag the Digital Experience Leadership team, and they can review. When in doubt, tag@mpreuss
as a reviewer. -
Level 4: This will need Legal approval. Tag
@mpreuss
and he can loop in the legal team.