giseldo/neodataset huggingface dataset:
Install and Setup Tailwind CSS on www.gitlab.com Repo for Production

We need to setup Tailwind CSS into our www.gitlab.com repo. Since we have already tested this framework and we are satisfied that its' the best direction, its imperative that we should start using it to develop our marketing pages.

I have started the installation on this branch. https://gitlab.com/gitlab-com/www-gitlab-com/-/tree/tailwind-integrate-middleman

Story points: 4.0
Create "Continuous integration in Agile development" 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-agile


#### 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/1Gw7pppdf9QBSaAZsw0lfEla7FmoWRS5892JELkE6TWM/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
Edit CD Solution Overview blog - The basics of GitLab CD

<!-- 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

Will edit and re-purpose this [unfiltered blog](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10238) 

https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10238#note_473099796



### 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 separate CI and CD tags for the GitLab blog

With so much focus on Continuous Integration and Continuous Delivery as separate products, and with the creation of two separate topic pages, there is a greater need for separation of the two.

Currently, we have one blog tag for CI/CD in the [blog handbook](https://about.gitlab.com/handbook/marketing/blog/#tags), but it looks like there are separate tags for CI and CD showing up [here](https://about.gitlab.com/blog/tags.html).

Could we phase out the CI/CD blog tag and encourage using the CI and CD tags separately? 


Action Items:

- [ ] Organize blogs under the existing CI/CD tag into either CI, CD, or both.
- [ ] Update blog handbook to reflect two tags (CI and CD)

Story points: 2.0
Blog posts incorrectly placed in releases blog

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/releases/2019/09/11/how-to-avoid-broken-master-with-pipelines-for-merge-requests/

#### Briefly describe the bug

Some blog posts have been incorrectly placed in the releases blog repo.

#### If possible, please specify how to reproduce the bug

`Insert answer here`

#### 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/

`Insert screenshot here`

#### 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

`Insert results URL here`

#### What computing device are you using?

Please list the brand and model (Example: Samsung Galaxy S 10 Plus)

`Insert answer here`

#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state?

- [ ] 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.

`Insert answer here`

#### 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.

`Insert answer here`

#### What type of network are you connected to?

**Type**

- [ ] Wired
- [ ] Wifi
- [ ] Cellular (4G, 5G, etc)
- [ ] Satellite
- [ ] Other

`Insert details here if applicable`

**Location**

- [ ] Home
- [ ] Workplace
- [ ] Travel facility (hotel, airport, conference center, etc)
- [ ] Public venue (restaurant, library, cafe, etc)
- [ ] VPN
- [ ] Other

`Insert details here if applicable`

**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

`Insert details here if applicable`

<!-- 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
Typos in blog post titles

#### What is/are the relevant URL(s)

* https://about.gitlab.com/blog/2017/06/07/continous-integration-ticketmaster/
  * typo from `continous` to `continuous`
* https://about.gitlab.com/blog/2020/01/29/comparable-awards/
  * typo from `comparable` to `comparably`

#### Briefly describe the bug

Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned.

`Certain blog post URLs have typos in them`

#### Notes

* [Related slack thread](https://gitlab.slack.com/archives/C2R1NED61/p1608069001225700).

#### Deliverables

* [ ] Update the URLs
* [ ] Add redirects from old URL to new URL
* [ ] MR reviewed by `@shanerice` and `@rebecca`

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Blog Post: using GitLab SAST with Android - December 2020

<!-- 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

<!-- What do you want to blog about? Add your description here. If you are making an announcement, please open an `announcement` request issue in the Corporate Marketing project instead: https://about.gitlab.com/handbook/marketing/corporate-marketing/#requests-for-announcements -->

This blog post highlights the value of using GitLab SAST on Mobile Applications. It highlights specifically Android.
I created a video as well as an application that user can clone and follow through with.

### 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 `@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
Fix Broken Link and Update "Where we are Headed"

The `Mock Press Release` link at https://about.gitlab.com/direction/plan/time_tracking/#where-we-are-headed hits a 404 (and also talks about September 2020 being in the future)- I think it could use an update :)

![image](/uploads/59faf941f1cd7af2cec28c70c1237ed0/image.png)

As a bit of an aside, I tried adding a comment here, in the hope somehow I could escalate/convert to an issue-
https://gitlab.com/gitlab-com/www-gitlab-com/-/commit/779aac664fa6275e027c68754eecfbb68f1d8ff6#note_462135057 is there a clever way to do this that i'm missing?

Story points: 1.0
Blog post: How we prevented security fixes leaking into our public repositories (Dec 2020 / Jan 2021)

### Proposal

Publish an engineering blog post about how we resolved these issues:

* https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/426
* https://gitlab.com/gitlab-org/gitlab/-/issues/38386
* https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/914

### 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 `@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: Partial clone (TBD)

<!-- 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

(See https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10021#note_456867365). Answering some Qs about partial clone.

Previous post published on the topic: https://about.gitlab.com/blog/2020/03/13/partial-clone-for-massive-repositories/

Other resources:

- Transcript: https://docs.google.com/document/d/18udLM2RRnA5y48w2qnAaGB0zHotbG3Wnu-NQfb-lBBk/edit?usp=sharing
- https://gitlab.com/gitlab-org/gitlab-development-kit/-/merge_requests/1421
- https://gitlab.com/groups/gitlab-org/-/epics/773

### 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 `@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: 3.0
News category missing from /blog

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/blog/

#### Briefly describe the bug

https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/68857 was merged to address https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9985. Now the "News" category has disappeared from the blog homepage entirely and there is no way to view posts in this category:

![Screenshot_2020-11-26_at_10.29.20](/uploads/cfe897f41784a80164211c596e84e3c4/Screenshot_2020-11-26_at_10.29.20.png)

#### If possible, please specify how to reproduce the bug

Visit https://about.gitlab.com/blog/

#### Please provide any relevant screenshots or screencasts

See above

#### What is your window size, browser, operating system, and versions

https://www.whatsmybrowser.org/b/91AC9

#### What computing device are you using?

MacBook Pro 2020

#### 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

N/A

#### What is your geographic location

EU

#### What type of network are you connected to?

**Type**

- [ ] Wired
- [x] 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**

- [ ] 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`

<!-- 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
Error occurred while installing nokogiri (1.10.10), and Bundler cannot continue on MacOS Big Sur

Installing the repo for the first time and ran into an issue when running `bundle install`.

Lets diagnose what changes need to be made to our gemfile to fix this. 
````
An error occurred while installing nokogiri (1.10.10), and Bundler cannot continue.
Make sure that `gem install nokogiri -v '1.10.10' --source 'https://rubygems.org/'` succeeds before bundling.

In Gemfile:
  capybara-screenshot was resolved to 1.0.25, which depends on
    capybara was resolved to 3.31.0, which depends on
      xpath was resolved to 3.2.0, which depends on
        nokogiri
````

#### System Information
- macOS Big Sur
- Version 11.0.1
- MacBook Pro 15 Inch 2018

Story points: 5.0
Create "How to find the right continuous integration tool" 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/choose-continuous-integration-tool

This web article is repurposing an existing blog called **[How to find the right CI/CD solution](https://about.gitlab.com/blog/2019/07/15/finding-the-right-ci-cd/)**


#### 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/1CpMvT2-gKlUVNvgk8R8QcUNI4So5Hq2usR-wxjoxyz4/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: 1.0