giseldo/neodataset huggingface dataset:
Collections post: How our engineering team built things at GitLab (Jan 6)

<!-- 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

Some of our top-performing technical posts were about how our engineering team built certain features at GitLab or how our engineering team troubleshooted different problems on GitLab. This is our second collection post that has a round-up of the best technical content that fits this frame. 

### 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: 1.0
Blog post: Learn more about Learn@GitLab - Jan 12

<!-- 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

Learn@GitLab is this beautiful resource that hasn't been promoted very much, so I'd like to write a blog about it and provide some details on how people can use it and link to a few of the videos and/or demos featured on the page.

[Draft doc](https://docs.google.com/document/d/1gPh4wBM848iVQGTuFcB49kJZLMwu5BzYUiAmFCrLTMU/edit?usp=sharing)

[Link to epic](https://gitlab.com/groups/gitlab-com/marketing/-/epics/954)

### 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: 1.0
Handbook update: Add DIB checklist

<!--

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

Drafting updates to the handbook so we can ensure all blog posts meet the DIB checklist criteria. This is a draft of the DIB checklist. 

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Set up markdown formatter that formats files following the Handbook’s Markdown style guide

### Proposal 

This is part of the effort to enforce a consistent markdown formatting style across Markdown pages in the Handbook. The goal is integrating a command line tool that formats markdown files following the [Handbook Markdown Style Guide](https://about.gitlab.com/handbook/markdown-guide/). 

There is an MR draft that implements the formatting tool. We plan to move these changes to a separate NPM repository to integrate the formatter in the Static Site Editor as well: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/68569/

Story points: 3.0
Follow-up from "Homepage Redesign MVC2"

The following discussions from !66787 should be addressed:

- [ ] @brandon_lyon started a [discussion](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/66787#note_451136114):  (+2 comments)

    > Feedback from Slack this morning
    > 
    > * White text link on white background under the customer case studies section.
    > * Video carousel on homepage is not inclusive/diverse, but this was a preexisting problem.
    > * Cookiebot might be blocking certain js on the homepage (icons on the devops tools comparison)
    > * "Learn more about our feature maturity" might not be linking to an appropriate spot.

Story points: 1.0
Make workflow diagram clickable

We made some progress on this but didn't merge the MR - https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/67804

We can use https://www.image-map.net/ to create the image map, however, the image is displayed at around 70% of the page width and the image map areas do not scale down, so the hotspots don't overlap with their parts of the diagram.

The HTML looks like this:

```
<!-- Image Map Generated by http://www.image-map.net/ -->
<img src="PDF-Diagram.svg" usemap="#image-map">
<!-->
<map name="image-map">
  <area target="_self" alt="Validation Backlog" title="Validation Backlog" href="/handbook/product-development-flow/product-development-flow-draft.html#validation-phase-1-validation-backlog" coords="175,253,305,333" shape="rect">
  <area target="_self" alt="Problem Validation" title="Problem Validation" href="/handbook/product-development-flow/product-development-flow-draft.html#validation-phase-2-problem-validation" coords="92,197,65" shape="circle">
  <area target="_self" alt="Design" title="Design" href="/handbook/product-development-flow/product-development-flow-draft.html#validation-phase-3-design" coords="166,81,43" shape="circle">
  <area target="_self" alt="Solution Validation" title="Solution Validation" href="/handbook/product-development-flow/product-development-flow-draft.html#validation-phase-4-solution-validation" coords="388,198,64" shape="circle">
  <area target="_self" alt="Plan" title="Plan" href="/handbook/product-development-flow/product-development-flow-draft.html#build-phase-1-plan" coords="538,159,672,242" shape="rect">
  <area target="_self" alt="Develop and Test" title="Develop and Test" href="/handbook/product-development-flow/product-development-flow-draft.html#build-phase-2-develop--test" coords="679,73,811,154" shape="rect">
  <area target="_self" alt="Launch" title="Launch" href="/handbook/product-development-flow/product-development-flow-draft.html#build-phase-3-launch" coords="820,160,951,239" shape="rect">
  <area target="_self" alt="Improve" title="Improve" href="/handbook/product-development-flow/product-development-flow-draft.html#build-phase-4-improve" coords="677,251,812,332" shape="rect">
</map>
```


**Notes**

- When copy/pasting from image-map.net, you will have to remove the indentation and re-add it from the beginning of each line.
- The source file for the diagram is in [Figma](https://www.figma.com/file/ZHll9R1ER7IlSkpZrIiff3/Product-Development-Flow?node-id=0%3A1).

Story points: 2.0
Creating People Data Team Catalog

Please select a template from the top left dropdown before continuing.

This repository primarily relates 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.

If you do not select an appropriate template then your issue might get lost. For more information about our workflows, please reference the handbook for the marketing website
https://about.gitlab.com/handbook/marketing/website/
or reference your team documentation.

### FAQ:

Q: Which template should I use?

A: Most people will use the "-website-bug-report" or "-handbook-update" issue templates. To request updates to existing pages or new content, please visit https://about.gitlab.com/handbook/marketing/growth-marketing/#requesting-support

There are also templates for writing various kinds of blog posts including the unfiltered category. Please see the blog handbook for instructions before you open an issue: https://about.gitlab.com/handbook/marketing/blog/#publishing-process 

The rest of the templates are likely specific to team, role, or special occasion.

Q: When will you get to this issue?

A: Your issue will be refined and then prioritized relative to other issues. Marketing's website development team is currently an impacted resource.

Q: How do I link to an issue template?

A: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=name-of-template

Q: How do I edit this FAQ? I have another question.

A: Submit an issue
https://gitlab.com/gitlab-com/www-gitlab-com/issues/new 
with FAQ in the title and assign it to @ brandon_lyon or another member of the website team
https://about.gitlab.com/handbook/marketing/website/

Story points: 3.0
Make lifecycle icon banner mobile friendly

Let's make the lifecycle icon banner displayed on https://about.gitlab.com/upcoming-releases/ mobile friendly. 

This element was originally pulled from https://about.gitlab.com/devops-tools/.


- Related https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/67340
- Related https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8746/

Story points: 3.0
"Configure" misspelled in DevOps Lifecycle image

### Problem

The DevOps Lifecycle image that is displayed at https://about.gitlab.com/stages-devops-lifecycle/ shows "CONFIGUR" instead of "CONFIGURE".  This image is frequently-used, so this is a relatively high-visibility misspelling.

### Screenshot

![Screen_Shot_2020-11-05_at_11.42.04_AM](/uploads/2e31793eb5b54145d588744783b23e5f/Screen_Shot_2020-11-05_at_11.42.04_AM.png)

Story points: 1.0
Feature "How GitLab Pages uses the GitLab API to serve content" on main 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.-->

<!-- Add a link to the original Unfiltered blog post and @ mention the author -->
Feature How GitLab Pages uses the GitLab API to serve content
https://about.gitlab.com/blog/2020/08/03/how-gitlab-pages-uses-the-gitlab-api-to-serve-content/
CC @jaime

Story points: 1.0
How to shift left with 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/shift-left-devops




#### 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/1q2YZpV0DzgattC84mg-zzplOk3lqqWzJ5u7SvzUJVFA/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
Blog: How pre-filled variables will make running pipelines easier - Dec 1

<!-- 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

https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/content-marketing/-/issues/241

*We have this feature coming out in 13.6 that I thought was really interesting and had a lot of engagement from the community.* 

- [Generate Run Pipeline form with pre-filled variables from .gitlab-ci.yml](https://gitlab.com/gitlab-org/gitlab/-/issues/30101)

What made this topic interesting was that it had a lot of engagement (over 100 likes and several dozen comments). I would like to talk about this feature and also give three real-world examples of how this feature will impact workflows. Who will get the most value out of this feature? Is it something that saves time? Does it help users in some kind of specific way, and what examples can we give?

### 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`)
  - [ ] 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: 1.0
Blog: How we're making migrating to GitLab CI easier - Dec 8

<!-- 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

https://gitlab.com/gitlab-com/marketing/growth-marketing/global-content/content-marketing/-/issues/232

We have a ton of documentation around making the migration process from Jenkins easier - let's talk about that. Found this product direction [here](https://about.gitlab.com/direction/verify/jenkins_importer/) and think it could be worth talking about.

We could make this specific to how we're improving the migration process from Jenkins and use it for the Jenkins competitive campaign relaunch. Would like to see your thoughts on this.

* [Reddit thread](https://www.reddit.com/r/devops/comments/8bxbyw/why_do_you_want_to_migrate_from_jenkins/) asking why you want to migrate from Jenkins

Could also really use your help on the title. Should I say migrating from Jeknins or migrating to GitLab CI and then mentioning Jenkins in the subtitle?

### 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)
- [x] Indicate if supporting an event or campaign - Jenkins campaign
- [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

Story points: 1.0
Collection: remote work + engineering - 2021-03-12

<!-- 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

Post collecting new and existing remote work + engineering stories.

To include new posts: 

- https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9899
- https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9898
- https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9809
- https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9810

Older posts to be considered:
- https://about.gitlab.com/blog/2020/08/27/measuring-engineering-productivity-at-gitlab/
- https://about.gitlab.com/blog/2019/06/03/how-we-turned-40-person-meeting-into-a-podcast/


### Checklist

- [ ] 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`)
  - [ ] 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