giseldo/neodataset huggingface dataset:
Geo: Write blog post "How to install GitLab 11.9 with Geo on AWS" tutorial

- [ ] Follow up https://gitlab.com/gitlab-org/gitlab-ee/issues/7360#note_150168367:

>>>
I had an idea. Do we need some kind of initiative like DigitalOcean seems to have for writing tutorial-style blog posts? Similar to https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-gitlab-on-ubuntu-18-04.

`How to install GitLab 11.9 with Geo on AWS` sounds attractive.

We can only do so much to make our docs apply generally *and* add cloud-provider-specific exceptions *and* keep them up-to-date. I'd like to avoid making our general docs more confusing with too much specificity. But without specificity, the sysadmin needs to learn how the whole system works.

Blog posts like this acknowledge this problem. They are hyper-specific. They go out-of-date, but the type of people installing GitLab should understand that, and should be able to adapt these tutorials to their purposes until a better one comes along that bumps the old one down the Google results.

Would a blog post resolve this issue?
>>>

Story points: 3.0
Designing with a vision in mind

<!-- See https://about.gitlab.com/handbook/marketing/blog/ for details on the blog process -->

### Proposal

Write about how we set our vision for the things we design, how it adapts through time but most importantly, how it guides us towards better solutions.

### Checklist

- [ ] Due date and milestone added for the desired publish date
- [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#time-sensitive-posts-official-announcements-company-updates-breaking-changes-and-news)
  - [ ] Added ~"priority" label
  - [ ] Mentioned `@rebecca` to give her a heads up ASAP

Story points: 2.0
"GitLab workflow" link at the "Engineering workflow" page seems to be dead

The [engineering workflow page](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/handbook/engineering/workflow/index.html.md) refers to the "GitLab workflow" (at [this line](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/source/handbook/engineering/workflow/index.html.md#L103) and more). 

But the corresponding link `/handbook/communication/#gitlab-workflow` is dead - no such anchor at the ["Communication"](https://about.gitlab.com/handbook/communication/) page of the handbook.

What was meant by this link? Should this reference be removed or updated with anything else?

Story points: 1.0
Show title on previous and next posts

At the bottom of a blog post are "next" and "previous" links: 

![image](/uploads/a5cd29478d3db1c8e397628c51147b50/image.png)

Update so that they include the title of the blog post. 

## Todo
- [ ] Make a mockup of what the previous/next button should look like 
- [ ] Implement the logic to add the title 
- [ ] Build the CSS to make the buttons match the mockup

cc @rebecca

Story points: 2.0
Add an email signature example to the tools-and-tips page

### Description

In the `tools-and-tips` section I want to add an email signature example to make it easier for the reader to setup a GitLab email signature.

Checklist when modifying an existing page:

- [ ] What is the goal of changing the page?
**To make it easier for the reader to setup a GitLab email signature.**
- [ ] Would we revert the changes if we decided that it was not a success? 
**Yes**

### Proposal
![Screenshot_2018-10-02_at_09.47.44](/uploads/a85d888730506c258bb248bda5d74643/Screenshot_2018-10-02_at_09.47.44.png)

### Links / references
https://about.gitlab.com/handbook/tools-and-tips/#email-signature

Story points: 1.0
Fix spelling errors on tools-and-tips page

### Description

I found some spelling errors while reading throigh the `tools-and-tips` section of the handbook.

Checklist when modifying an existing page:

- [ ] What is the goal of changing the page?
**To fix spelling errors**
- [ ] How will we decide if the change was successful or not?
**Check for spelling errors**
- [ ] Would we revert the changes if we decided that it was not a success?
**Yes**

### Proposal
stereoids -> steroids

manpulations -> manipulations

dirctory -> directory

### Links / references
https://about.gitlab.com/handbook/tools-and-tips/

Story points: 1.0
GitLab Issue

Hello World! :wave: 

This is my issue's description, written in markdown (GitLab Flavored Markdown).

### This is an `<h3>`

> _Let's quote someone here_

Add a task list:

- [ ] Task 1
- [ ] Task 2

Mention merge requests (https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1784) and issues (https://gitlab.com/gitlab-org/gitlab-ee/issues/2101) and hover over them to see their titles.

Invite users to collaborate with `@mentions`: @marcia 

Story points: 3.0
Communicate between Programmers.

* For medium sized issues there will always be a frontend or backend. 
* For bigger issues there should be a whole team. UX, Frontend, Backend, Product
* If you are starting on a new feature that is sizable you should expect at least a FE and BE programmer. If for some reason there isn’t than make sure you ask why there isn’t. If it is a bigger (direction/large customer) issue then expect a whole team. 
* Make a call with your team when you start. 
* Communicate throughout the whole process. So that when the MR comes in there will be less questions in the end. Questions can be brought up in the beginning and during the process.

Story points: 1.0
Feature to Feature Comparison to BitBucket

Looking to establish a page or section on gitlab.com with an apples-to-apples comparison between GitLab EE and Atlasssian products. The goal is to have a more direct comparison to features and the advantages we hold over Atlassian. The current comparison here(https://about.gitlab.com/comparison/#gitlab-vs-bitbucket-server) is a bit outdated according to conversations with prospects, and does not highlight the feature-to-feature comparisons in depth. 

The goal is for the sales team to be able to send a link(s) to prospects/customers considering BitBucket so they can clearly see the differences in more detail. I've talked with Job about this this morning and he is putting a few things together to update the website. Thoughts are always welcome!  @ChadMalchow @AshleyS @jwrede @ronstroschein @sytses @malessio @balameb @JobV    

Story points: 7.0
Release post tier badge text is misaligned

#### What is/are the relevant URLs or emails?

Any release page, e.g.: https://about.gitlab.com/releases/2020/07/22/gitlab-13-2-released/

#### Briefly describe the bug

The tier badges' texts are misaligned.

#### What are the steps to reproduce the bug

1. Visit any release page, e.g.: https://about.gitlab.com/releases/2020/07/22/gitlab-13-2-released/
1. Look at the tier badges under a feature headline

#### Please provide any relevant screenshots or screencasts

![Screenshot_from_2020-08-12_10-33-40](/uploads/e5f772c69afd65ef91fa70ab17d097a1/Screenshot_from_2020-08-12_10-33-40.png)

#### What is your window size, browser, operating system, and versions

Tested in Firefox 79.0 and Chromium Version 84.0.4147.105 (Official Build) snap (64-bit) on Ubuntu 20.04.1 LTS

#### Possible fix

The badges have a fixed width of `60px`, which is not enough to contain the longer strings like `ULTIMATE`. Two possible fixes:

1. Rely on a `display: table` layout more for these badges, without setting a fixed width on each badge
1. Use `display: grid` :tada: 

<!-- If you do not want to ping the website team, please remove the following cc -->
/cc @gl-website

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Newsletter subscription form white text white background

<!--

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.

For information regarding working on the about website please visit the [Brand and Digital Handbook](https://about.gitlab.com/handbook/marketing/growth-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-bug-report

-->

#### What is/are the relevant URLs or emails?

<!--
Example: https://about.gitlab.com/something/etc/
-->

https://about.gitlab.com/events/commit/

#### Briefly describe the bug

<!--
Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned.
-->

The newsletter subscription form has white text over a white background and therefore is practically invisible. It technically still functions but this bug is likely be a barrier to use.

#### Please provide any relevant screenshots or screencasts

![Greenshot_2020-08-11_14.49.11](/uploads/5aaa60cbd519210c1e075b48778ab9ab/Greenshot_2020-08-11_14.49.11.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)
Example: Chrome 77, macOS 10.15.0, 944px by 977px, https://whatsmybrowser.org/b/MPC757K
-->

https://www.whatsmybrowser.org/b/4YUV8SF

#### What device are you using

<!--
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?

<!--
Examples:
* I tried a fresh incognito window & it had no impact.
* The problem goes away when using an incognito window.
* It only happens when YYYYYY cookies are set to ZZZZZZ.
-->

N/A

#### What browser plugins do you have enabled?

<!--
Example: Adblock, noscript, ghostery, safe browsing.
Why?: Certain website bugs may be caused by plugins.
-->

N/A

#### What is your geographic location

<!--
Why?: 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

#### What type of network are you connected to?

<!--
Examples:
* Wired corporate network.
* Wifi at home.
* Restaurant wifi.
* AT&T 4G.
-->

Home cable

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
What are Versioned Tests and why should you use them?

<!-- 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

Versioned tests are listed as one of the highlighted features of GitLab CI/CD, but it doesn't look like we use that term or have fully explained what that looks like and what that means. I would like to make a post that talks about versioned tests and what they are, what they do, how to set them up, and why they're a good feature.

This is for the CI Use Case Campaign. Publish date is not time-sensitive, anytime in Q3 is fine.

### Checklist

- [ ] If you have a specific publish date in mind (please allow 3 weeks' lead time)
  - [ ] Include it in the issue title
  - [ ] 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](http://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
- [ ] Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)

Story points: 2.0
Investigate using a serverless app to process Marketo forms

`@jeanduplessis` recently pointed out a potential way to process Marketo forms without a server is via a serverless application such as Lambda. This would allow us to combine the best of both worlds, our static website and a dynamic server. We should investigate and see if this is something we could potentially use to fix our Marketo privacy issues.

Due to cost and time required, before we do this we should try other solutions first:

* https://gitlab.com/gitlab-com/marketing/growth-marketing/brand-and-digital/brand-and-digital/-/issues/256
* https://gitlab.com/gitlab-com/marketing/growth-marketing/growth/-/issues/214

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 10.0
Update default MR template

## Please update the default MR template

```

<!--Before proceeding, please check if you need to apply a specific MR description template from the dropdown menu above next to `Description` (e.g. blog post, website bug report).-->

## Why is this change being made?

<!--
Provide a detailed answer to question on why this change is being proposed, in accordance with our value of [Transparency][transparency].
-->

## Author Checklist
- [ ] Provided a concise title for the MR
- [ ] Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency]
- [ ] Assign this change to the correct DRI
    - If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack].
    - If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping `@gl-static-site-editor` in a comment for a review and merge. For example changes to `.gitlab-ci.yml`, JavaScript/CSS/Ruby code or the layout files.
```

Story points: 1.0
Remove JS files from blog post and move blog post to correct directory

#### What is/are the relevant URLs or emails?
This blog post does not have a current URL because it is in the depreciated `source/posts` directory. The blog post also references javascript files uploaded directly to its image directory.
```
source/images/blogimages/gitlab-daily-tools/Handy GitLab actions.user.js
source/images/blogimages/gitlab-daily-tools/GitLab filters.user.js
```
Having javascript files located in the image directory will confuse linters and filters.

#### Where is the blog post located
https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/source/posts/2019-11-26-gitlab-daily-tools.html.md

<!-- If you do not want to ping the website team, please remove the following cc -->
/cc @gl-website

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Team map not loading in Safari

#### What is/are the relevant URLs or emails?

https://about.gitlab.com/company/team/

#### Briefly describe the bug

Team map not loading in Safari.

#### Please provide any relevant screenshots or screencasts

![image](/uploads/383afca895ff6b22b513e8b8d7651d38/image.png)

#### What is your window size, browser, operating system, and versions

Mojave 10.14.5 and Safari 13.1.1

#### What device are you using

Macbook Pro

Story points: 2.0
Phase 2 Website Update - search

```

BL notes to self:

* The parts left for me are outlined in a comment near the bottom
  https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8470#note_422300928


```

This template if for the Marketing Growth Team for their Phase 2 Webpage updates

Title this issue: Phase 2 Website Update - (Page Name) 

[Phase 2 Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23)

## Metadata for page
- **Intent:** 
- **Goal:** 
- **Who is code owner:**  
- **SME Group:** 

## Adjustments to be made:
These adjustments are from this audit round

- [x] Add metadata
- [ ] Swapping content or content links
- [ ] Adding pathfactory link 
- [ ] Adjusting SEO 
- [x] Adding CTA buttons
- [ ] Adjusting copy on CTA buttons
- [x] Adjusting old/erroneous messaging
- [ ] Improve mobile optimization
- [ ] Clean up alignment
- [ ] Adjust color schemes
- [x] Swap out old assets


## Relevant Links:
- [Page Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23)
- [Survey](https://docs.google.com/forms/d/1GsZ4IoIAeLssROY_JfoWuOFPWyO5M4ykgYBNhD5sU8o/edit)

## Roles and Responsibilities

| Role | DRI |
| ------ | ------ |
| Project DRI | @rreich  |
| Marketing Analytics | @shanerice  |
| Content/Messaging | @erica|
| Web Dev | @skarpeles  |
| Brand/Design  | @luke |
| GM Stakeholder | @dmor  |

## Production
**Project DRI**
- [x] Add design to design tab
- [ ] Decide on audit items and check-off
- [ ] Assign to relevant Team Leads for visibility 
- [ ] Make relevant WIP MRs
- [ ] Add this issue to the page epic description 
- [ ] Close issue once set of MRs is complete 

**Team Leads**
You may make comments in the design tab for tracking, but conversations on updates should be kept to the relevant MRs

Story points: 1.0
Phase 2 Website Update - community/index

This template if for the Marketing Growth Team for their Phase 2 Webpage updates

Title this issue: Phase 2 Website Update - (Page Name) 

[Phase 2 Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23)

## Metadata for page
- **Intent:** 
- **Goal:** 
- **Who is code owner:**  Growth Marketing
- **SME Group:** Community Team

## Adjustments to be made:
These adjustments are from this audit round

- [x] Add metadata
- [ ] Swapping content or content links
- [ ] Adding pathfactory link 
- [x] Adjusting SEO 
- [x] Adding CTA buttons
- [x] Adjusting copy on CTA buttons
- [x] Adjusting old/erroneous messaging
- [ ] Improve mobile optimization
- [x] Clean up alignment
- [ ] Adjust color schemes
- [x] Swap out old assets


## Relevant Links:
- [Page Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23)

## Roles and Responsibilities

| Role | DRI |
| ------ | ------ |
| Project DRI | @rreich  |
| Marketing Analytics | @shanerice  |
| Content/Messaging | @erica|
| Web Dev | @skarpeles  |
| Brand/Design  | @luke |
| GM Stakeholder | @dmor  |

## Production
**Project DRI**
- [x] Add design to design tab
- [x] Decide on audit items and check-off
- [x] Assign to relevant Team Leads for visibility 
- [x] Make relevant WIP MRs
- [x] Add this issue to the page epic description 
- [ ] Close issue once set of MRs is complete 

**Team Leads**
You may make comments in the design tab for tracking, but conversations on updates should be kept to the relevant MRs

Story points: 1.0
Change all mentions of WIP to Draft in Blog Handbook



#### Briefly describe the update

WIP prefix for merge request has been depreciated in favor of using Draft instead. 

This was documented here https://gitlab.com/gitlab-org/gitlab/-/issues/228685

Let's change all documentation in the handbook related to creating abd publishing blog posts to use the new prefix. 

This will apply to the following pages: 
https://about.gitlab.com/handbook/marketing/blog/
More TBD


<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Phase 2 Website Update - what-is-gitlab/index

This template if for the Marketing Growth Team for their Phase 2 Webpage updates

Title this issue: Phase 2 Website Update - (Page Name) 

[Phase 2 Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23)

## Metadata for page
- **Intent:** About GitLab the company
- **Goal:** Learn more about GitLab the company
- **Who is code owner:** Growth Marketing 
- **SME Group:** Corporate Marketing

## Adjustments to be made:
These adjustments are from this audit round

- [x] Add metadata
- [x] Swapping content or content links
- [ ] Adding pathfactory link 
- [ ] Adjusting SEO 
- [x] Adding CTA buttons
- [x] Adjusting copy on CTA buttons
- [x] Adjusting old/erroneous messaging
- [ ] Improve mobile optimization
- [ ] Clean up alignment
- [ ] Adjust color schemes
- [ ] Swap out old assets

## Relevant Links:
- [Page Epic](https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/23)

## Roles and Responsibilities

| Role | DRI |
| ------ | ------ |
| Project DRI | @rreich  |
| Marketing Analytics | @shanerice  |
| Content/Messaging | @erica|
| Web Dev | @skarpeles  |
| Brand/Design UX Desktop and Mobile | @sbouchard |
| Brand/Design Dev  | @mpreuss22 |
| GM Stakeholder | @dmor  |

## Production
**Project DRI**
- [x] Add design to design tab
- [x] Decide on audit items and check-off
- [x] Assign to relevant Team Leads for visibility 
- [x] Make relevant WIP MRs
- [x] Add this issue to the page epic description 
- [x] Close issue once set of MRs is complete 

**Team Leads**
You may make comments in the design tab for tracking, but conversations on updates should be kept to the relevant MRs

Story points: 4.0
Investigate deferring the load of below-the-fold images in marketing site

Can we dramatically improve performance by deferring the load of below-the-fold images and third-party <iframe> in the marketing website? 

During this investigation of [this issue](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/6665), it was found that images are a significant factor to long page load times. 

What methods exist today for this? What solutions would work well with our stack?

Story points: 2.0
Can we get rid of https://about.staging.gitlab.com/ entirely?

The staging environment and its deploy job ~~continues to add extra complexity for the work @cwoolley-gitlab is doing in the CI file related to https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8302~~ has been removed from the CI/CD deploy process and has not been updated for years.

Is it possible to have redirect testing done via the review app?

Are testing redirects the only reason staging is used? Let's identify who, when, and why the staging area is used. Because every MR fires up it's own dedicated review app, seems that we may be able to remove the staging URL entirely. 

The staging URL: https://about.staging.gitlab.com/

Related https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8337
Related https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8302

Story points: 3.0