Skip to content

Update sitemap creation logic

Megan Filo requested to merge update-main-sitemap into master

Why is this change being made?

Closes gitlab-com/marketing/digital-experience/buyer-experience#3310 (closed)

Updating the way our sitemap is built up. Recently we have made changes to the Buyer Experience sitemap + our Blog has moved to a new project, changing that sitemap's URL. This made the two blog sitemap (old_blog_sitemap and new_blog_sitemap) links from this www project obsolete.

This MR removes the deprecated blog sitemaps and adds in the new one.

Review app vs Production

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 Megan Filo

Merge request reports