giseldo/neodataset huggingface dataset:
Feature Unfiltered posts

<!-- 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.-->

Unfiltered posts to consider for featuring:

- https://about.gitlab.com/blog/2020/09/01/a-tale-of-two-editors/
  - This reminds me of [this post](https://about.gitlab.com/blog/2020/02/27/how-holistic-ux-design-increased-gitlab-free-trial-signups/) which got over 1,700 unique views in 2 months after publishing. Probably only needs a light edit.  
- https://about.gitlab.com/blog/2020/08/03/how-gitlab-pages-uses-the-gitlab-api-to-serve-content/
  - This seems like a classic technical post about a popular feature. 

These posts both got >200 unique views as Unfiltered posts.

Story points: 1.0
CI blogs for repurpose

I went through the spreadsheet of blogs [grouped by topic](https://docs.google.com/spreadsheets/d/15RorS3Y7fRHWoIaNR-37Oq34F_xRyihAjXM_o-yXous/edit?usp=sharing) and selected some CI blogs that would be good candidates for repurposing into web articles.

## [How to find the right CI/CD solution](https://about.gitlab.com/blog/2019/07/15/finding-the-right-ci-cd/)

This can be some helpful content that isn't GitLab-focused, and provides some good action steps that would fit into the CI topic page.

## [4 Benefits of CI/CD](https://about.gitlab.com/blog/2019/06/27/positive-outcomes-ci-cd/)

I can roll the benefits section into the existing benefits of continuous integration, but there's a section in this blog about measuring CI success that would be good for its own web article

## [Defending the CI/CD pipeline](https://about.gitlab.com/blog/2019/11/19/defend-cicd-security/)

Tips for defending pipelines would work well for CI

## [CI/CD: The ticket to multicloud](https://about.gitlab.com/blog/2020/01/17/ci-cd-the-ticket-to-multicloud/)

I think his would be a good tie in for CI or it could be a good web article for the multicloud page on "How to implement multicloud" or "the challenges of multicloud"

Story points: 1.0
Collection post: How to do XYZ with GitLab (Dec 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

"Collection" post highlighting our most popular engineering stories, including blog posts and potentially select videos from Commit sessions (https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/editorial/-/issues/43).

Supporting https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/137.

### Checklist

- [x] If you have a specific publish date in mind (please allow 3 weeks' lead time)
  - [x] Include it in the issue title and apply the appropriate milestone (e.g. `Blogs October 2020`)
  - [x] 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 `@TinaS`,  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 `@KimLock` and `@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
Continuous integration best practices  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 continuous integration best practices 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-best-practices




#### 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

- [x] Copy complete - [Draft](https://docs.google.com/document/d/1vy7N3gWUhd7lcDMG-rEePiF1ImNrELRG1xpxjgiGyis/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: 2.0
What is pipeline as code 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 pipeline as code 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/pipeline-as-code




#### 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

- [x] Copy complete - [Draft](https://docs.google.com/document/d/19R8JPLfo5dpIlSHpFdIpeQTI_sJMkzN4TS2t5sJNsk0/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: 2.0
How a continuous integration pipeline works 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 the benefits of 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-pipeline




#### 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

- [x] Copy complete - [Draft](https://docs.google.com/document/d/1-fnVAf0fZIl2O3vr6fSkSTeyz7iX6-FD7S3dsPtQErI/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: 2.0
The benefits of 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 the benefits of 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/benefits-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

- [x] Copy complete - [Draft](https://docs.google.com/document/d/1etfMVnLvzLbjGpv2pnh3sH1URxaB9aXJt3WLaoz_ABo/edit?usp=sharing)
- [x] 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: 2.0
Refactor and add tests for `generators/releases.rb`

- Refactor code
- Add tests

The following discussion from !64079 should be addressed:

- [ ] @sean_carroll started a [discussion](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/64079#note_422673457):  (+1 comment)

    > Hi @nfriend thanks for this change!
    > 
    > In reviewing the code, I was surprised to see that there are no tests for the existing code, before the changes on this MR. It is moderately complex code, and it is also quite visible being on our main website.
    > 
    > I think we should take this opportunity to add a spec for `generators/release`, we can use https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/spec/generators/org_chart_spec.rb as a model.
    > 
    > I'm happy to help with this if useful.
    > 
    > Back to you :ping_pong:

Story points: 1.0
Commit - on demand links switched to youtube playlist

Relates to https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/439

## Deliverables

- [x] Switch "view on demand" button URLS from `https://gitlabcommitvirtual.com/` to `https://www.youtube.com/c/Gitlab/playlists?view=50&sort=dd&shelf_id=5`
- [x] Swap the video recap section with a video slider of the above playlist.
- [x] Replace the Sched embed with a PDF.
- [x] Temporarily add then remove the manual_cookiebot frontmatter.

Story points: 2.0
Bug fix: # in blog frontmatter tweet field truncates the click to tweet

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)
about.gitlab.com/blog

#### Briefly describe the bug

If a # is used in the blog's tweet line in the front matter the click-to-tweet feature is truncated right before the hashtag.

#### If possible, please specify how to reproduce the bug

Just insert a # in the "tweet" line in the blog front matter.


<!-- 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
Dead link [bind us as a company] in jobs/faq

#### What is/are the relevant URL(s)

[https://about.gitlab.com/jobs/faq/#gitlabs-outbound-recruiting-model](https://about.gitlab.com/jobs/faq/#gitlabs-outbound-recruiting-model)

[https://about.gitlab.com/jobs/faq/handbook/leadership/biggest-risks/#loss-of-the-values-that-bind-us](https://about.gitlab.com/jobs/faq/handbook/leadership/biggest-risks/#loss-of-the-values-that-bind-us)

#### Briefly describe the bug

The link `bind us as a company` in **GitLab’s outbound recruiting model** section is broken and produces a 404 error.

#### If possible, please specify how to reproduce the bug

Click on the link `bind us as a company` on the page "Jobs at GitLab - FAQ", section **GitLab’s outbound recruiting model**

#### What is your window size, browser, operating system, and versions

`https://www.whatsmybrowser.org/b/QZ3DM`

#### What computing device are you using?

Custom build PC.

#### 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.

- Adblock Plus
- DuckDuckGo Privacy Essentials
- Facebook Container

#### What is your geographic location

Europe / France

#### What type of network are you connected to?

**Type**

- [x] Wired
- [ ] Wifi
- [ ] Cellular (4G, 5G, etc)
- [ ] Satellite
- [ ] Other

**Location**

- [x] Home
- [ ] Workplace
- [ ] Travel facility (hotel, airport, conference center, etc)
- [ ] Public venue (restaurant, library, cafe, etc)
- [ ] VPN
- [ ] Other

**Hardware**

- [ ] I am behind a network security appliance such as a firewall
- [ ] I am using a pi-hole or other hardware-based traffic blocker
- [ ] Other

<!-- 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: 1.0
Links to blog posts from review app wrong for file names with uppercase letters

Blog post urls are automatically downcased during the build. This is good because mixed case URLs are bad for SEO. 

However, when a review app links directly to blog post with a mixed case file name, it returns a error. This is because the review app link doesn't change the URL link to all downcase.

For example, a blog post file name of `2020-09-30-Q3-hackathon-recap.html.md.erb`  will directly link to this URL from the review app this https://hackathon-recap.about.gitlab-review.app/blog/2020/09/30/Q3-hackathon-recap/index.html.

That will return an "no file found" xml error because the of the mixed casing. The correct and reachable URL is https://hackathon-recap.about.gitlab-review.app/blog/2020/09/30/q3-hackathon-recap/index.html

The related MR to the blog post is [here](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/63488). I have also encountered this issue with other MRs too. 

Can we get the review app to link to the correct blog post?

Story points: 2.0
Define outcomes and activities for Validation phase 2: Problem validation

Associated MR: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/63272

**Problems to solve:**

- [x] Doesn’t Encourage Cross-Functional Collaboration
- [x] Too Many Steps
- [x] Too Prescriptive

Detailed problems to solve for reference: https://docs.google.com/presentation/d/1BxUVcoPyjYkR7MOHn1aZGllMCqlH5eb27JKM_bb_uDA/edit#slide=id.g94724597ab_3_0

**Requirements:** (can fall into multiple MRs)

- [x] Do not remove or change workflow labels
- [x] Maintain or add clarity on what is REQUIRED per https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9090
- [x] Maintain or add clarity on who the cross-functional collaborators in the phase are
- [x] Consider referencing the current step by step as a sample flow
- [x] Incorporate link outs to handbook resources that support activities to achieve outcomes

Potential template to leverage: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/61793

Story points: 3.0
Define outcomes and activities for Validation phase 1: Validation backlog

**Problems to solve:**

- [ ] Doesn’t Encourage Cross-Functional Collaboration
- [ ] Too Many Steps
- [ ] Too Prescriptive

Detailed problems to solve for reference: https://docs.google.com/presentation/d/1BxUVcoPyjYkR7MOHn1aZGllMCqlH5eb27JKM_bb_uDA/edit#slide=id.g94724597ab_3_0

**Requirements:** (can fall into multiple MRs)

- [ ] Do not remove or change workflow labels
- [ ] Maintain or add clarity on what is REQUIRED per https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9090
- [ ] Maintain or add clarity on who the cross-functional collaborators in the phase are
- [ ] Consider referencing the current step by step as a sample flow
- [ ] Incorporate link outs to handbook resources that support activities to achieve outcomes

Potential template to leverage: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/61793

Story points: 3.0
Update trademark module look & feel to be less prominent

Currently the trademark module on this page (https://about.gitlab.com/devops-tools/) is too prominent. See screenshot below:

![image](/uploads/05391e8ca47711db7865dec332c9ccc3/image.png)

Please update page design to de-emphasize this section, per Becky's comment on design item #10 here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8468/designs/screencapture-about-gitlab-devops-tools-2020-07-27-14_04_35.png#note_405511055

Story points: 1.0