giseldo/neodataset huggingface dataset:
Update merging during broken `master` process

This issue is tracking progress on https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/77343.

Post-merge checklist:

- [x] Add a note to the Engineering Week in Review about the change.
- [ ] Update our [code review](https://docs.gitlab.com/ee/development/code_review.html) process and links to the new process.

Story points: 1.0
Feature Unfiltered Post: Slippers design system

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.-->

<!-- Add a link to the original Unfiltered blog post and @ mention the author -->

https://about.gitlab.com/blog/2021/03/05/starting-from-the-start-slippers-design-system/ @smcguinness1 thanks for writing this blog post! Moving to the main blog.

Story points: 1.0
Feature Production-Grade Infrastructure and DevSecOps in Under Five Minutes on blog

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.-->

Feature https://about.gitlab.com/blog/2021/02/24/production-grade-infra-devsecops-with-five-minute-production/ on main blog

(FYI @skassabian)

Story points: 1.0
Adjust MTTP KPI to only count working days

Original Issue Link: https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/12524

> Currently MTTP shows the time MRs take to reach production, measured across the entire month however this gives an inaccurate view because we intentionally don't deploy on weekends.

>We should adjust https://app.periscopedata.com/app/gitlab/764878/MTTP-KPI-Dashboard?widget=10055732 to only count working days within a month to give a true measure of MTTP.

>@davis_townsend do you think we could make this change?

Story points: 3.0
Feature "Redesigning our docs"

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.-->

Feature https://about.gitlab.com/blog/2021/02/12/redesigning-our-docs/ on main blog.

Story points: 1.0
Update Ruby from 2.7 to 3.0 to use on build/test

We need to continuously keep updating the build/test environments of the repository itself.

Relates to gitlab-org&5149 (initiative upgrading Ruby 2.7 to 3.0 in GitLab product)

### Prerequisites

- [x] gitlab-org/gitlab-build-images!372

### TODO

- [x] !75872
- [x] !78849
- [x] !79022
- [x] !79284
- [x] !79480
- [x] !79484
- [x] !79491
- [x] [middleman/middleman#2460](https://github.com/middleman/middleman/pull/2460)
- [x] [middleman/middleman#2462](https://github.com/middleman/middleman/pull/2462)
- [x] !78850

### cf.

- Previous update: !73459

Story points: 128.0
Blog update: Add GitOps tag to relevant blog posts

I added a "gitops" tag to the blog handbook and now need to add the tag to past published, relevant blog posts: 

- https://about.gitlab.com/blog/2020/12/17/gitlab-for-cicd-agile-gitops-cloudnative/
- https://about.gitlab.com/blog/2020/07/14/gitops-next-big-thing-automation/
- https://about.gitlab.com/blog/2020/04/17/why-gitops-should-be-workflow-of-choice/
- https://about.gitlab.com/blog/2019/11/18/gitops-prt-3/
- https://about.gitlab.com/blog/2019/11/12/gitops-part-2/
- https://about.gitlab.com/blog/2019/11/04/gitlab-for-gitops-prt-1/
- https://about.gitlab.com/blog/2019/10/28/optimize-gitops-workflow/

Story points: 1.0
DE ENG: Marketo privacy subprocessors form

## This issue relates to https://gitlab.com/gitlab-com/marketing/marketing-operations/-/issues/4263#note_513238603

URL: https://about.gitlab.com/privacy/subprocessors/#sign-up

Steps to reproduce: Submit the form.

Observed: Page reloads and sends to /pricing/

Expected: For says "thank you for submitting" with no page redirect.

![Screen_Shot_2021-02-19_at_10.10.46_AM](/uploads/86dfa537355ef81ec57b521688fc1b27/Screen_Shot_2021-02-19_at_10.10.46_AM.png)

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 2.0
Feature Unfiltered post: Meet Pipeline Editor

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.-->

Opening to consider featuring the following Unfiltered post: https://about.gitlab.com/blog/2021/02/22/pipeline-editor-overview/

Story points: 1.0
Handbook update: Add GitOps tag

<!--

This template is for requesting work related to the [company handbook](https://about.gitlab.com/handbook/).

This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items.

You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-handbook-update

-->

#### Briefly describe the update

I realized we should probably add a 'gitops' tag to the [Blog Handbook](https://about.gitlab.com/handbook/marketing/blog/#tags). I'm not sure how to do add a tag, could we work on this during our next 1:1 @rebecca? 



<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Feature Unfiltered post: This SRE attempted to roll out an HAProxy config change. You won't believe what happened next...

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.-->

Review https://about.gitlab.com/blog/2021/01/14/this-sre-attempted-to-roll-out-an-haproxy-change/ for featuring on main blog.

Story points: 1.0
Blog post: Roundup of debugging stories - 2021-03-31

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. -->

### Proposal

Roundup of the best stories coming out of https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/4077.

Inspired by https://boleary.dev/blog/2021-01-27-the-purse-caper-debugging-can-be-hard.html.

### Checklist

- [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time)
  - [ ] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`)
  - [ ] Give the issue a due date of a minimum of 2 working days prior
  - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
- [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts)
  - [ ] Add ~"Blog: Priority" label and supplied rationale in description
  - [ ] Mention `@rebecca` to give her a heads up ASAP
- [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue
- [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`,  apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts)
- [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts)
- [ ] Indicate if supporting an event or campaign
- [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

Story points: 2.0
Create "What is cloud native continuous integration" web article

<!--

This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/).

This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items.

For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/)

You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request

-->

#### What problem(s) are we trying to solve? What are the project goals?

This will be a web article describing how to implement continuous integration that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/)

#### Briefly describe your request

Create a web article nested within the CI/CD topics page

#### What is/are the relevant URL(s)

https://about.gitlab.com/topics/ci-cd/cloud-native-continuous-integration


#### Please identify the directly responsible individual (DRI), stakeholders, and roles

<!--
Who should we be asking for questions and reviews?
Example in a markdown table:

|Name|Role|
|------|------|
| `@cbuchanan` | DRI |
| `tbd` | MPM |
| `tbd` | PMM |
| `tbd` | Design |

-->

#### Does this request require a form to capture registrations for a gated asset?

- [x] No
- [ ] Yes



#### What are the project should-haves?

This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc

#### What are the project could-haves?



#### Where do you expect traffic to come from?

* links from blogs
* links from pdf assets
* visitors searching for continuous integration topics online

#### Please provide any related media files



#### Will you need an opengraph image for social sharing?

Not sure

#### If applicable, please provide some example webpages for design guidance.

Examples:
* Pinterest implements recommendations well
* Stripe has good payment UX
* I like the aesthetics of nike.com
* Animation examples, microinteractions, etc
-->

#### If applicable, do you have any user journeys, prototypes, content/data?




#### Please create a checklist of deliverables in this phase

- [ ] Copy complete - [Draft](https://docs.google.com/document/d/1LbUehBdSfaelENMsxW6PriuVrt0xpoAg9iGIobOQPEk/edit?usp=sharing)
- [ ] First draft of page delivered
- [ ] Page reviewed
- [ ] Page live


<!--THE END-->

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Improve findability of different release information about GitLab

Problem: We have too much information about releases in different places, and we might not have the SEO optimized. Example: I did a Google search for "GitLab Releases" and ended up on [this page](https://about.gitlab.com/releases/), which is a really poor customer experience. 

@timnoah and I compared what we saw when we did the same Google search, and had different results:

My result:
![image](/uploads/31aec3a7e0eb065899e5bc36bad94bfb/image.png)

His result:
![image](/uploads/8ff4289276e740d1ce5287550698763a/image.png)

Story points: 8.0
Marketing site Event list sorting incorrect in some cases when event date is a range

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/

This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items.

#### What is/are the relevant URL(s)

`https://about.gitlab.com/events/`

#### Briefly describe the bug

The Event list sorting does not always work correctly for events where the date is a date range.

In development, you need to be running the marketing site (not the handbook) to view the `/events` page.

#### If possible, please specify how to reproduce the bug

In `events.yml` define an event with `date:` as a range.

`date: December 30 - January 4, 2021`

or 

`date: December 30 - January 4, 2022`

or 

`date: December 30 - December 31, 1999`

In all cases GitLab::Homepage::Event `sort_date` will parse `December 30` as `December 30, 2021` (the current year).



<!-- Please do not remove the items below, they are needed to automatically notify the relevant entities -->
/cc @gl-website

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 2.0
Privacy policy page is bugged

This template is for filing a bug report related to the logged out marketing website https://about.gitlab.com/ and company handbook https://about.gitlab.com/handbook/

This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items.

#### What is/are the relevant URL(s)

`https://about.gitlab.com/privacy/`

#### Briefly describe the bug

Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned.

`@sdaily reported. The page looks unstyled and has broken formatting.`

#### If possible, please specify how to reproduce the bug

`Visit the page`

#### Please provide any relevant screenshots or screencasts

How to take a screenshot: https://www.howtogeek.com/205375/how-to-take-screenshots-on-almost-any-device/

![Greenshot_2021-01-11_09.35.19](/uploads/18237fecdcf0d4f24ff94023578b4b6d/Greenshot_2021-01-11_09.35.19.png)

#### What is your window size, browser, operating system, and versions

Please use the following website to determine your browser specifications and provide a link developers can follow:

What is my browser https://www.whatsmybrowser.org

`https://www.whatsmybrowser.org/b/4YUV8SF`

#### What computing device are you using?

Please list the brand and model (Example: Samsung Galaxy S 10 Plus)

`Macbook pro 15" 2019`

#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state?

- [x] I tried a fresh incognito window & it had no impact.
- [ ] The problem goes away when using an incognito window.
- [ ] The problem only happens when certain cookies are set to a specific value (please specify below).

#### Please list any browser plugins you have enabled

Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing.

`N/A`

#### What is your geographic location

Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies.

`California. Other locations have reported this as well.`

#### What type of network are you connected to?

**Type**

- [x] Wired
- [ ] Wifi
- [ ] Cellular (4G, 5G, etc)
- [ ] Satellite
- [ ] Other

`Insert details here if applicable`

**Location**

- [x] Home
- [ ] Workplace
- [ ] Travel facility (hotel, airport, conference center, etc)
- [ ] Public venue (restaurant, library, cafe, etc)
- [ ] VPN
- [ ] Other

`Insert details here if applicable`

**Hardware**

- [x] I am behind a network security appliance such as a firewall
- [ ] I am using a pi-hole or other hardware-based traffic blocker
- [ ] Other

`Insert details here if applicable`

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Blog post: How to balance iteration with stability in engineering (Aug 17)

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. -->

### Proposal

Based on discussion with ZJ re: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10021. 

Transcript: https://docs.google.com/document/d/1mduHzWXoaXo09Q6R4-oU9QPjR4AZwOzN22Nb4I7v6Kc/edit?usp=sharing

### Checklist

- [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time)
  - [ ] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`)
  - [ ] Give the issue a due date of a minimum of 2 working days prior
  - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
- [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts)
  - [ ] Add ~"Blog: Priority" label and supplied rationale in description
  - [ ] Mention `@rebecca` to give her a heads up ASAP
- [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue
- [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`,  apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts)
- [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts)
- [ ] Indicate if supporting an event or campaign
- [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

Story points: 4.0
Blog post: Why you should be doing engineering demos

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process. Unless you are just suggesting a blog post idea, you will need to create the formatted merge request for your blog post in order for it to be reviewed and published. -->

### Proposal

Resources:

* https://gitlab.com/gitlab-org/gitaly/-/blob/master/.gitlab/issue_templates/Demo.md
* https://about.gitlab.com/handbook/engineering/development/demos.html
* From interview with ZJ: https://docs.google.com/document/d/1TtqTcqXk27CQeGlPgn-nPGl127KiER8YVGyfV_QywDc/edit?usp=sharing

Inspired by conversation from https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10021.

### Checklist

- [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time)
  - [ ] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`)
  - [ ] Give the issue a due date of a minimum of 2 working days prior
  - [ ] If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
- [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#process-for-time-sensitive-posts)
  - [ ] Add ~"Blog: Priority" label and supplied rationale in description
  - [ ] Mention `@rebecca` to give her a heads up ASAP
- [ ] If wide-spread customer impacting or sensitive, mention `@nwoods` to give her a heads up ASAP, apply the ~"sensitive" label, and check the [PR handbook](https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements) in case you need to open an announcement request instead of a blog post issue
- [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@arashidi`,  apply the ~"Partner Marketing" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts)
- [ ] If the post is about one of GitLab's customers, mention `@FionaOKeeffe`, apply the ~"Customer Reference Program" label, and see the [blog handbook for more on third-party posts](https://about.gitlab.com/handbook/marketing/blog/index.html#third-party-posts)
- [ ] Indicate if supporting an event or campaign
- [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

Story points: 2.0
Update agile delivery topics/solutions pages

The Agile Delivery Solutions page is linked under Agile Delivery on the topics page. 

In this [MR](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/70991), we removed agile delivery from the monorepo, and it's showing as nested under the `topics` folder. But when you go to the [topics](https://about.gitlab.com/topics/) live page, it still links to about.gitlab.com/solutions/agile-delivery

I'm not sure why it would still be linking to the solutions page after the changes we made.

Thank you for taking another look at this!

Story points: 1.0
Create "What is a continuous integration server" web article

<!--

This template is for requesting work related to the logged out [marketing website](https://about.gitlab.com/) and [company handbook](https://about.gitlab.com/handbook/).

This is not the correct repository for requests related to docs.gitlab.com, the GitLab product, or other items.

For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/brand-and-digital-design/)

You may link to this issue template using the following URL: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=-website-work-request

-->

#### What problem(s) are we trying to solve? What are the project goals?

This will be a web article describing how to implement continuous integration that will be linked from the [CI/CD topics page](https://about.gitlab.com/topics/ci-cd/)

#### Briefly describe your request

Create a web article nested within the CI/CD topics page

#### What is/are the relevant URL(s)

https://about.gitlab.com/topics/ci-cd/continuous-integration-server


#### Please identify the directly responsible individual (DRI), stakeholders, and roles

<!--
Who should we be asking for questions and reviews?
Example in a markdown table:

|Name|Role|
|------|------|
| `@cbuchanan` | DRI |
| `tbd` | MPM |
| `tbd` | PMM |
| `tbd` | Design |

-->

#### Does this request require a form to capture registrations for a gated asset?

- [x] No
- [ ] Yes



#### What are the project should-haves?

This page should have the look and layout of other topics pages and sections at the bottom for listing other resources: eBooks, blogs, whitepapers, webcasts, etc

#### What are the project could-haves?



#### Where do you expect traffic to come from?

* links from blogs
* links from pdf assets
* visitors searching for continuous integration topics online

#### Please provide any related media files



#### Will you need an opengraph image for social sharing?

Not sure

#### If applicable, please provide some example webpages for design guidance.

Examples:
* Pinterest implements recommendations well
* Stripe has good payment UX
* I like the aesthetics of nike.com
* Animation examples, microinteractions, etc
-->

#### If applicable, do you have any user journeys, prototypes, content/data?




#### Please create a checklist of deliverables in this phase

- [ ] Copy complete - [Draft](https://docs.google.com/document/d/1LbUehBdSfaelENMsxW6PriuVrt0xpoAg9iGIobOQPEk/edit?usp=sharing)
- [ ] First draft of page delivered
- [ ] Page reviewed
- [ ] Page live


<!--THE END-->

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0