feat: Create standard Event template in Contentful
Step 1: What is changing in this MR?
Changes to the components are done mostly to inject one single text object instead of multiple text fields that would require new content types or adding more complexity to existing ones.
I extracted most of the data handliong logic into a file called events.service.ts. This is will need more work in the future to follow the Layered architecture model that John suggested but it has the basic logic needed to get the standard events working.
Template Entry : https://app.contentful.com/spaces/xz1dnu24egyd/entries/2NxNjKkXEPIcY8cu3PikXT
Migrated Events:
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
Closes #2867 (closed)