giseldo/neodataset huggingface dataset:
Link to logo trademark is broken


<!--

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/handbook/marketing/corporate-marketing/#gitlab-trademark--logo-guidelines

#### Briefly describe the bug

<!--
Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned.
-->

I was looking for the logo trademarks as I wanted to link there. From https://about.gitlab.com/press/press-kit/ I clicked on "Trademark information" which then led me to https://about.gitlab.com/handbook/marketing/corporate-marketing/#gitlab-trademark--logo-guidelines but the anchor is gone.

@dmor My guess is that this was moved into growth marketing now?

https://about.gitlab.com/handbook/marketing/growth-marketing/brand-and-digital-design/brand-guidelines/#trademark

If yes, please re-assign to fix.

#### What are the steps to reproduce the bug

<!--
Example (In a bulleted list):
* Scroll to the W section of the page
* When condition X is true
* Hover over Y
-->

Find any page which links to the anchor:

```
➜  www-gitlab-com git:(master) grep -r '#gitlab-trademark--logo-guidelines' .
./source/press/press-kit/index.html.haml:  = link_to "Trademark information", "/handbook/marketing/corporate-marketing/#gitlab-trademark--logo-guidelines"
./source/handbook/finance/Procurement/index.html.md:* [Trademark](/handbook/marketing/corporate-marketing/#gitlab-trademark--logo-guidelines) - information regarding the usage of GitLab's trademark
./source/handbook/legal/index.html.md:* [Trademark](/handbook/marketing/corporate-marketing/#gitlab-trademark--logo-guidelines) - information regarding the usage of GitLab's trademark
```


<!-- 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
Blog: Newsletter subscription not possible


<!--

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?

https://about.gitlab.com/releases/categories/releases/ and the other blog categories

#### Briefly describe the bug

There is an introduction text shown about signing up to the newsletter but no textentry or button is there to actually do it.
The text ending with colons suggests there should be any way to progress.

#### What are the steps to reproduce the bug

* Visit https://about.gitlab.com/releases/categories/releases/
* Try to signup to the newsletter

#### Please provide any relevant screenshots or screencasts

![gitlab-newsletter](/uploads/06328ae32c48a0d7b66c037e746b129c/gitlab-newsletter.PNG)

#### What is your window size, browser, operating system, and versions

* Windows 10, Firefox 77.0.1, 1920x1200px, https://www.whatsmybrowser.org/b/PD973
* Windows 10, Microsoft Edge 44.18362.449.0, 1920x1200px, https://www.whatsmybrowser.org/b/W1IOL

#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state?

* Problem persists on Firefox with disabled Adblockers.
* Incognito mode in FF still shows the same behaviour.

#### What browser plugins do you have enabled?

A lot in Firefox, none in Edge.
Relevant FF plugins could be uBlock origin & Privacy Badger

#### What is your geographic location

Germany

#### What type of network are you connected to?

* Wired corporate network.

/cc @gl-website

Story points: 1.0
Web: Demo Landing Page Conversion - MVC 2

## Demo Landing Page Conversion MVC

### Goals
Increase Demo landing page conversion rate on about.gitlab.com with collaborative, data-driven MVC. The first attempt did not prove net positive, let's learn from that and try again.

### Audience
- Devs prospects new to gitlab at all stages of their careers.

### Requirements

Must Have

- Co-design an improved and compliant solution - Co-design a conversion-driven MVC that meets or exceeds the design and usability the current state solution. The MVC should be informed by conversion best practices, marketing strategy and brand and website standards. Consider page speed, content and form optimization.
- Set KPIs - Set MVC KPIs in order to test the positive and negative impacts of your change - especially marketing KPIs. How might your changes negatively affect experiences and metrics?
- Validate performance If testing proves the MVC is positive change, share demonstrable data, merge, and ensure health monitoring and reporting.
- Share change events - Document and share change events and results with relevant GitLab teams.
- Should Have

Could Have

Wont Have

- Non-cohesive demo experience - Ensure the new landing page experience is aligned to the overall demo workflow (i.e. continuous content and design experience).

### KPIs


### Proposed Tasks
- Conversion audit & recommendations (Shane)
- KPI's
- Planning
- MVC Requirements
- Iterative Co-Design
- Build the page @skarpeles
- Test
- If success: Merge, monitor and report
- Create follow-on issues, as needed.

@brandon_lyon @skarpeles @shanerice

Story points: 2.0
Sort/filter options for the release post blog page

### Proposal

As the monthly blog post gets longer (more teams shipping more items) it is challenging for users to find what they need.  Consider adding an option to the UI for users to sort by section (key features, other features, deprecations, etc) as well as sorting by plan type and/or stage. The default of the page would be to show everything as we now do, but then the user can sort/filter as needed. 

* What is/are the relevant URL(s): https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/
* What team/dept/company initiatives does this relate to?
     - Product Marketing
* What are the measurable key performance indicators (KPI)?
     - time on page
     - clicks on page
     - feature adoption

This suggesting has come cross-functionally from product, marketing, sales and engineering teams at different times. Product  stakeholders recommended for design review and or feedback on this one, should you decide to move forward @fseifoddini @sfwgitlab @adawar Recommended Marketing stakeholder @johnjeremiah

Story points: 5.0
Set cookiebot to refresh after accept

#### What problem(s) are we trying to solve? What are the project goals?

End users may be unaware that they need to refresh the page after accepting cookies. This used to happen automatically but something may have changed. This is likely impacting Marketo form conversion rate.

#### Briefly describe your request

Attempt to implement [this fix](https://support.cookiebot.com/hc/en-us/community/posts/360014661313/comments/360001582313).

```
  window.addEventListener('CookiebotOnAccept', function (e)
  {
    if (Cookiebot.changed)
    {
       document.location.reload();
    }
  });
```

#### What is/are the relevant URL(s)

https://about.gitlab.com/*

#### What team/dept/company initiatives does this relate to?

Improve conversion

#### Is there a due date? If so, why?

No due date, however ASAP is good.

#### Please identify the directly responsible individual (DRI), stakeholders, and roles

|Name|Role|
|------|------|
| `@brandon_lyon` | DRI |
| `@sdaily` | Cookiebot |
| `@amy.waller` | Marketo |
| `@shanerice` | Metrics |

<!--THE END-->

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 2.0
Add Value Calculator to the Data Team Handbook to support prioritization and ranking of new Issues, Epics, and Initiatives

<!--

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

Update Data Team "How We Work" section to include coverage of the a Value Calculator to aid in work prioritization.
Originating Issue: https://gitlab.com/gitlab-data/managers/-/issues/161

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 5.0
Update Data Team Handbook SLOs

<!--

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

Update the SLO section of the Data Team handbook to include coverage for Issues and MRs.

Origin Issue: https://gitlab.com/gitlab-data/analytics/-/issues/4734#note_340948597


<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Add video to commit landing page

#### What problem(s) are we trying to solve? What are the project goals?

* Communicate event expectations via [this video](https://www.youtube.com/watch?v=iQjMV-Ux8zE&feature=youtu.be).

#### Briefly describe your request

* Add a video block to the Commit event landing page.

#### What is/are the relevant URL(s)

* https://about.gitlab.com/events/commit/

#### What team/dept/company initiatives does this relate to?

* Unknown.

#### Is there a due date? If so, why?

* Sooner is better than later but no specific date is connected.

#### Who is the audience?

* (Primary) Potential event attendees.
* Speakers.
* Media.
* Potential sponsors.

#### What are the measurable key performance indicators (KPI)?

This phase:

* Email subscriptions.
* CFP submissions.
* Sponsorship info requests.

Eventually:

* Attendee signups.
* Scholarship requests.

#### Please identify the directly responsible individual (DRI), stakeholders, and roles

|Name|Role|
|------|------|
| `@Lconway` | DRI |
| `@brandon_lyon` | Developer |

#### Does this request require a form to capture registrations for a gated asset?

- [x] No
    * Forms on the page are preexisting and already developed with mktg ops.
- [ ] Yes
    * Gated assets require involvement from the MPM team to set up registration processing and tracking for reporting. Please open a [Gated Content Request](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/-/issues/new?issuable_template=Gated-Content-Request-MPM) for the MPM team.

#### Where do you expect traffic to come from?

* Linked from https://about.gitlab.com/
* Social media campaign.
* Targeted ads.
* Email campaigns.

#### If applicable, do you have any user journeys, prototypes, content/data?

* [Events template figma file](https://www.figma.com/file/frPfePiwZlywXoTkEsw5g1/Email-Web-Design-System---Commit-Example)

#### Proposed deliverables

* Add a block to the page where there is a video preview

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Update the issue template for website requests

#### What problem(s) are we trying to solve? What are the project goals?

Per @jennyt, we need to check if forms have reporting setup before releasing a page with a form on it.

#### Briefly describe your request

Update the "website-work-request" issue template with the following details BEFORE the "what are project must-haves" section:

> Does this request require a form to capture registrations for a gated asset?

* Checkbox for "no".
* Checkbox for "yes".
    * Gated assets require involvement from the MPM team to set up registration processing and tracking for reporting. Please open a [Gated Content Request](https://gitlab.com/gitlab-com/marketing/digital-marketing-programs/-/issues/new?issuable_template=Gated-Content-Request-MPM) for the MPM team.

#### Who is the audience?

* GitLab team members.

#### 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|
|------|------|
| `@jennyT` | DRI |
| `@brandon_lyon` | Developer |

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Update Data Team Handbook Charter

<!--

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

Update Data Team Handbook Charter to include our new Mission and other adjustments to help everyone better understand the direction the Data Team is heading, towards providing more complete and scalable solutions.



<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Image broken on Guide to the Cloud resource

#### What is/are the relevant URLs or emails?

* https://about.gitlab.com/resources/guide-to-the-cloud/

#### Briefly describe the bug

* One of the SVG images doesn't look like it should (it should have a building and aircraft).

![Greenshot_2020-05-15_06.15.07](/uploads/37c9edc0e1ea01c4a2cc8e436bdd2351/Greenshot_2020-05-15_06.15.07.png)

#### What is your window size, browser, operating system, and versions

* https://www.whatsmybrowser.org/b/4YUV8SF

#### What device are you using

Macbook 15 2019

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Update button text on GitLab for Remote video form

Update button text on form CTA to say "Watch Video". Page is here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/7098#note_338454573

Brandon Lyon's comment about adding the button text code is here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/7098#note_338454573

Story points: 1.0
New Page for Forrester TEI project

<!--

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

-->

#### Briefly describe the request

Create a new page for a new customer project from Forrester, the Total Economic Impact

#### What is/are the relevant URL(s)

about.gitlab.com/analysts/forrester-tei2020

#### What team/dept/company initiatives does this relate to?

Strategic marketing has commissioned a Total Economic Impact report to be used as a sales tool to help customers realize their cost savings in using GitLab for specific use cases.

#### Is there a due date? If so, why?

Our due date is late May 2020 as we will get the final report from Forrester and have sales training for Sales and a place to direct them to for messaging and links to the tool and other assets.

#### What problem(s) are we trying to solve? What are the goals?

It's a brand new commissioned report that provides tools for sales and competitive

#### Who is the audience?

* Sales
* Customers
* Prospects

#### What are the measurable key performance indicators (KPI)?

* how many visit the page
* downloads of the report
* visits to the intereactive tool that Forrester is creating for us

#### Please identify the directly responsible individual (DRI), stakeholders, and roles



|Name|Role|
|------|------|
| @cfletcher1 | DRI |
| @Tompsett  | maintenance and admin |
| @rragozzine  |maintenance and admin|




#### What are the project must-haves?

* the web page



#### Where do you expect traffic to come from?

* social
* requesting this be linked to main about.gitlab.com page
* use case campaigns

#### Please provide any related media files

* forthcoming from Forrester, but likely links at this point

#### Will you need an opengraph image for social sharing?

no, as I still have no idea what that is


#### Please create a checklist of deliverables in this phase

* create and populate web page

#### Please apply your team's label using the dropdown menu below

Strategic Marketing, Analyst Relations

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
New Page for 2020 for Gartner MQ for AST


#### Briefly describe the request

Create a new web page for a new Gartner Magic Quadrant featuring GitLab

#### What is/are the relevant URL(s)

https://about.gitlab.com/analysts/gartner-ast20

#### What team/dept/company initiatives does this relate to?

Strategic Marketing always requests a web page for a new analyst report where we share information with sales on how to position this document for best advantage and frame GitLab properly in the context of their sales environment.

#### Is there a due date? If so, why?

The report is expected to come out the week of 2020-04-27.  If we can have it that week, that would be good.

#### What problem(s) are we trying to solve? What are the goals?

* provide information to Sales

#### Who is the audience?

* sales
* customers and prospects
* analyst community

#### What are the measurable key performance indicators (KPI)?

* SEO

#### Please identify the directly responsible individual (DRI), stakeholders, and roles




|Name|Role|
|------|------|
| @tompsett | DRI |
| @cfletcher1  | Content|
| @cblake  | Content |
| @NicoleSchwartz  | Content |



#### What are the project must-haves?

The web page set up like other web pages on that *.../analysts/* group of pages


#### What are the project should-haves?

Nothing else really


#### Where do you expect traffic to come from?

* Sales
* Blog posts

#### Please provide any related media files

We do not have that media yet. It is not released until the analysts release the page. We are not given more than 24 hours notice of this going live.

#### Will you need an opengraph image for social sharing?

I don't think so, since I have no idea what that is.

#### If applicable, please provide some example webpages for design guidance.

../analysts/gartner-aro19


#### Please create a checklist of deliverables in this phase


- [ ] create new page in same manner as others in that group

Marked confidential because we cannot have anyone know we are anticipating being in this report until it is published.


<!--THE END-->

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Blog Post: Show GitLab UI changed over years in pictures (Date TBD/by end of May)

### Proposal

I have quite a few screenshots of different old versions of GitLab. When I show it to some GitLab people, they were excited about it. One person suggested I make a blog post out of it. 

This can be a single blog post or series. With few screenshots per-year and some little text. Or more extended version. Right now its a raw idea. I don't have a good plan yet. Want to check out what people think.  

Few example of screenshots I have: 

| Page | Year | Screenshot |
|---|---|---|
| merge_request| 2012 | ![frame_generic_light](/uploads/94ecfa024b5d3430c5717603b39d8e37/frame_generic_light.png) |
| dashboard |  2013 | ![frame_generic_light_3_2](/uploads/61afebd6884e58b0c5f51a2b6cf3988b/frame_generic_light_3_2.png) |
|  dashboard/issues | 2014 | ![frame_generic_light_2014](/uploads/4e49b78538103152daba1c8f42b5f381/frame_generic_light_2014.png)|
|  project/tree | 2015 | ![Screenshot_2015-05-19_22.54.04](/uploads/252533fe20af955baf3920cfb9dcc75a/Screenshot_2015-05-19_22.54.04.png) |


### Checklist

- [x] If you have a specific publish date in mind (please allow 3 weeks' lead time)
  - [x] 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/#time-sensitive-posts-official-announcements-company-updates-breaking-changes-and-news)
  - [ ] Added ~"priority" label and supplied rationale in description
  - [ ] Mentioned `@rebecca` to give her a heads up ASAP
- [ ] If wide-spread customer impacting or sensitive
  - [ ] Add ~"sensitive" label
  - [ ] Mention `@nwoods` to give her a heads up ASAP
- [ ] If the post is about one of GitLab's Technology Partners, including integration partners, mention `@TinaS` 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
DevOpsTools Comparison Pages - Design

This is issue is related to all design work required to build and launch the new Dev Ops Tool Comparison webpage. 

You can view the broad stroke estimate and initial planning here: https://gitlab.com/gitlab-com/marketing/product-marketing/-/issues/2266

There is a another issue related to the development of this page here: https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/7052


# Helpful Links
* [latest wires](https://www.figma.com/file/4EDH2Zc8bXRjQ4cVL3cdlr/GitLab-vs.-Campaign?node-id=142%3A0) to clarify scope of work
* [Initial Estimates in Days](https://docs.google.com/spreadsheets/d/13hrQGM1re7k9LD0LrZYTYj1Qisx5e6aUvV84-CXUKhw/edit#gid=0) (1 work day considered 6.5 hours of work).

Story points: 3.0