chore: Delete solutions open source pages
Why is this change being made?
Delete pages which have been migrated to the BE repo already:
- Delete https://about.gitlab.com/solutions/open-source/join/ -->
data/solution_children/join.yml
- Delete https://about.gitlab.com/solutions/open-source/partners/ -->
data/solution_children/partners.yml
- Delete reference to both pages above:
sites/uncategorized/source/solutions/supply-chain/index.html.haml
- Delete
sites/uncategorized/source/solutions/supply-chain/index.html.haml
- Delete
sites/uncategorized/source/solutions/innersource/*
This is also related to gitlab-com/marketing/digital-experience/buyer-experience!3364 (merged)
💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.
CHANGEME - add the details saying why, not just what.
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
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
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 - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Edited by Miguel Duque