feat(solutions): [ENG] /solutions/open-source/join migration
Step 1: What is changing in this MR?
-
Adds
/solutions/open-source/join/
to Contenful in this entry. This page does not have localized content on either Contenful or /content folder. - Adds a new
/pages/_solutions
template architecture inspired on the new/pages/_contentful
template:- The folder structure for the first level of solutions pages ends up being /pages/_solutions/.index.vue
- For the second level pages, the template is /pages/_solutions/_subpage/index.vue
- Both templates re-use a custom layout which is named /layouts/solutions.page that re-uses the same logic to render equal solutions pages in both templates.
- Modifies
solutions
service and mapping helpers - Removes old page content from the
/content
folder - Adds icons to buttons in
/components/solutions/hero.vue
- Adds documentation to props and variants in the same Solutions hero component
TODO before merge:
- Publish the new page in Contenful
Sister MR in www repo deleting /open-source/join
and /open-source/partners/
content: gitlab-com/www-gitlab-com!132397 (merged)
Review app | Production |
---|---|
https://feat-open-source-join-migration.about.gitlab-review.app/solutions/open-source/join/ | https://about.gitlab.com/solutions/open-source/join/ |
Other /solutions/* pages that may be affected by these changes:
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
Related to #3186 (closed)