Restoring file path and file that redirects to current Gitlab Webinar Calendar

Step 1: What is changing in this MR?

I am trying to recreate the file path and an index.html file for display on for this public URL path that CS Ops has already sent to customers in outbound email campaigns:

https://about.gitlab.com/handbook/customer-success/tam/segment/scale/webinar-calendar/

The idea is if we recreate that file and it contains a tag for redirection to the webinar calendar page that is currently operational, then we can resolve the 404 issue for the page that was evidently deprecated from the main branch of the Buyer Experience project:

Step 2: Ensure that your changes comply with the following, where applicable:

• [ does not apply because the meta tag automatically redirects the viewer to the operating webinar calendar page ] 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:

1. dex-approval::1-minor
   1. Example of the type of change: typos or content changes.
      1. Anyone on the Digital Experience team can approve and merge.
      2. Once approved by the Digital Experience team, the MR creator can merge.
   2. Example of the type of change: /customers filter is displaying the wrong results.
      1. Anyone on the Digital Experience team can approve and merge.
      2. Once approved by the Digital Experience team, the MR creator can merge.
2. dex-approval::2-standard
   1. Example of the type of change: re-arranging components on a page.
      1. Once the Digital Experience team approves, members of the Digital Experience team can merge.
      2. Members of the Digital Experience team should keep their Managers informed.
      3. Manager’s discretion to align with the Director of Digital Experience or not.
   2. Example of the type of change: Adding new pages.
      1. Managers of Digital Experience can approve and merge.
      2. Manager should align with Director, Digital Experience.
3. dex-approval::3-key-page
   1. Example of the type of change: Changing Nav
      1. Directors and Managers of Digital Experience need to align.
      2. Managers of Digital Experience can approve and merge.
   2. Example of the type of change: Changes to key drivers of traffic and/or business goals etc. (Homepage, Pricing Page, Why GitLab).
      1. Director, Digital Experience can approve and merge.
      2. Director, Digital Experience will keep Marketing leadership informed of all Major Changes.
4. dex-approval::4-legal
   1. Example of the type of change: Any changes to company information, board/director information, etc.
      1. Legal and Director of Digital Experience must approve.
   2. Example of the type of change: Changes to sign-up workflows or alteration/omission of footers/links to anything legal-related.
      1. Legal and Director of Digital Experience must approve.

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:

1. Level 1: Any member of the Digital Experience Team
2. Level 2: Any member of the Digital Experience team
3. Level 3: Ping @gitlab-com/marketing/digital-experience in a comment. This will tag the Digital Experience Leadership team, and they can review. When in doubt, tag @mpreuss as a reviewer.
4. Level 4: This will need Legal approval. Tag @mpreuss and he can loop in the legal team.