Skip to content

remove absolute links to marketing site features

Lauren Barker requested to merge be-3565-features into master

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Removes the hard links to features on the marketing site, enable through testing in review apps.

  • Current state in prod - using absolute links for features in the categorie.yml file takes a user from a review app to production. This creates additional friction in QAing any changes to the behaviour when linking from /platform to /features.
  • These changes + this MR - Will enable persons QAing that MR to stay with in the review app environment and test changes. Related thread in issue here.
  1. Related gitlab-com/marketing/digital-experience/buyer-experience!3659 (merged)
  2. Related gitlab-com/marketing/digital-experience/buyer-experience#3565 (closed)
  3. Related gitlab-com/marketing/digital-experience/buyer-experience#3625 (closed)

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Lauren Barker

Merge request reports