giseldo/neodataset huggingface dataset:
Friday: Investigate refresh loop fix

Noting to myself to try a new fix on Friday afternoon when fewer people are using the site.

I have a new idea about how to potentially fix the refresh loop.

This investigation relates to https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8052 and https://gitlab.com/groups/gitlab-com/-/epics/681

```javascript
  window.addEventListener('CookiebotOnAccept', function (e)
  {
    if (Cookiebot.changed)
    {
      isCookieConsentStillRequired = getCookie("CookieConsent");
      isMarketingStillTrue = isCookieConsentStillRequired.includes('marketing:true');
      //console.log('cookie changed to ' + isCookieConsentStillRequired);
      if (isMarketingStillTrue == true)
      {
        //console.log('On change marketing is ' + isMarketingStillTrue);
        document.location.reload();
      };
    }
  });
```

Story points: 1.0
Phase 2 Website Update - free-trial page

This template if for the Marketing Growth Team for their Phase 2 Webpage updates

Title this issue: Phase 2 Website Update - (Page Name) 
## Metadata for page
- Intent: Free trial MQL (WIP)
- Goal: User clicks free trial (WIP) 
- Who is code owner: Growth Marketing 
- SME Group: Product Marketing 


## 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
- [ ] 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/66)

## Roles and Responsibilities

| Role | DRI |
| ------ | ------ |
| Project DRI | @rreich  |
| Marketing Analytics | @shanerice  |
| Content/Messaging | @erica|
| Web Dev | @brandon_lyon  |
| Brand/Design Desktop and Mobile | @sbouchard |
| Website DRI (Intent, Goal, Oversight)| @mpreuss22 |
| GM Stakeholder | @dmor  |

## To Do
- [x] Add relevant WIP MRs
- [x] Add this issue to the page epic description 
- [ ] Close issue once set of MRs is complete 
label ~"mktg-growth" ~"mktg-website" ~"mktg-status::wip" ~"Global Content" ~"mktg-analytics"

Story points: 1.0
Update secondary button style on homepage hero

#### What is/are the relevant URLs or emails?

https://about.gitlab.com/

#### Briefly describe the bug

Secondary CTA button in hero homepage should be white outlined with white text (not white background). 

#### Please provide any relevant screenshots or screencasts

![image](/uploads/d8d24eb68aedbeabd7b8e37824c8bcb7/image.png)

#### Design 

Based on Figma file here: https://www.figma.com/file/gvc1olvwp99YncG2EgihK8/Home-Page-Merchandising-Spec?node-id=61%3A99

Story points: 1.0
Blog Post (Unfiltered): Tips and habits for efficient Code Reviews

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/blog/unfiltered for details on the Unfiltered blog process.-->

### Proposal

<!-- What do you want to blog about? Add your description here -->

Write down several habits, tips and suggestions that make for an efficient code review process from the perspective of the reviewer.

In specific, from the perspective of a long time frontend maintainer: @iamphill

Story points: 2.0
Test a Marketo form without cookies

## Overview

#### Briefly describe your request

Implement a page where we can test theories related to marketo forms. In particular, the use of Marketo forms without tracking cookies.

#### Describe why this update is being requested:

What problem(s) are you trying to solve? What are the goals?

1. Marketo is a third party marketing tool.
2. Third party marketing tools are blocked by privacy strict browsers, adblockers, firewalls, and impacted by cookie consent legislation such as GDPR / CCPA.

#### What is/are the relevant URL(s)

`https://about.gitlab.com/handbook/marketing/growth-marketing/marketo-test-cookies/`

_________

## Project Management

#### What is the due date AND WHY? Dates without reason are difficult to prioritize. If there is no due date, please be as specific as possible about a timeframe and need.

No specific due date but the sooner the better since forms directly impact growth.

#### Please identify the directly responsible individual (DRI), stakeholders, and roles

|Name|Role|
|------|------|
| `???` | DRI |
| `@brandon_lyon` | Marketing web developer |
| `@amy.waller` | Marketo tool lead |
| `@shanerice` | Analytics |
| `@j.carey` | Analyst | 
| `@jstava` | Product growth |

 ____________

## Audience

All visitors to about.gitlab.com

___________

## Promotion and Measurable Goals

#### What are the measurable key performance indicators (KPI)?

* `Form completions`
* `Self-managed trial signups`

_____________

## Relevant Documents/Information

* [Code snippet for conditionally deferred cookies](https://blog.teknkl.com/conditionally-loading-munchkin-on-marketo-lps-for-gdpr-related-policies/)
* [Why to defer cookies and how it works](https://nation.marketo.com/t5/Product-Discussions/Preventing-embed-forms-from-setting-cookies-tracking-before/td-p/201848).

_____________

## Requestor Checklist

* [x] All sections have been filled out
* [x] All media and relevant documents have been linked or added
* [x] A due date and rationale for the due date has been added
* [x] Your team labels have been added

Story points: 2.0
Competitive Comparison pages don't render correctly in PDF view


<!--

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?

These two pages should render the same content
- https://about.gitlab.com/devops-tools/ca-veracode-vs-gitlab.html
- https://about.gitlab.com/devops-tools/pdfs/ca-veracode-vs-gitlab.html


#### Briefly describe the bug

Rendering a comparison with details doesn't properly work for the PDF render. 

[Example features.yml line](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/data/features.yml#L5903)
```
    gitlab_ci: true
    blackduck: false
    synopsys:
      valid: true
      details: 'supports 20 languages' # https://www.synopsys.com/content/dam/synopsys/sig-assets/datasheets/SAST-Coverity-datasheet.pdf
    snyk: false
    ca_veracode: true
```

#### What are the steps to reproduce the bug

View both of the pages listed above. 

#### Please provide any relevant screenshots or screencasts

https://about.gitlab.com/devops-tools/ca-veracode-vs-gitlab.html
![Screen_Shot_2020-07-13_at_4.31.27_PM](/uploads/420e1ac2ba82ed1413300d7eac5f74f5/Screen_Shot_2020-07-13_at_4.31.27_PM.png)


https://about.gitlab.com/devops-tools/pdfs/ca-veracode-vs-gitlab.html
![Screen_Shot_2020-07-13_at_4.31.22_PM](/uploads/703cb5314369b82a34b129b812d3deb3/Screen_Shot_2020-07-13_at_4.31.22_PM.png)


<!-- 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: 2.0
/multicloud topics page update

## Issue purpose

Update the [/multicloud](https://about.gitlab.com/multicloud/) topic page to incorporate SEO strategy. 

## Types of changes requested

- add/remove sections
- edit copy within existing sections
- add links to bottom of sections

### [COPY doc with final changes](https://docs.google.com/document/d/1zV7vT6Z1l_Of-HCqdN9T4jtvpA8Tnuao0rKqzN40cZ8/edit#)

Story points: 2.0
Demo form not working

#### What is/are the relevant URLs or emails?

https://about.gitlab.com/demo/

#### Briefly describe the bug

Filling out and submitting the form leaves the button hanging at "Please Wait"

#### Please provide any relevant screenshots or screencasts

![Greenshot_2020-07-06_07.59.36](/uploads/0bfec39d4d59b1dba16c520e5b6b1e71/Greenshot_2020-07-06_07.59.36.png)

#### What is your window size, browser, operating system, and versions

https://www.whatsmybrowser.org/b/4YUV8SF

#### What device are you using

Macbook Pro 2019 15"

#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state?

Yes, this reproduces incognito after cookie consent.

#### What browser plugins do you have enabled?

None

#### What is your geographic location

* (native) CA, USA
* (VPN) Frankfurt, Germany

#### What type of network are you connected to?

Wired at home

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Incorrect notation for PG upgrade on "Release post - GitLab 13.0"

In !48201 (13.0 release note), we made an incorrect notation around automatic upgrade of PostgreSQL in upgrading omnibus package from 12.x to 13.0 without either PG HA or Geo configurations or opt-out with `/etc/gitlab/disable-postgresql-upgrade`. We should rewrite it along with the omnibus implementation.

See [the thread](https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5412#note_372826639) for the confirmation.

Story points: 2.0
Test a Marketo form with static html

## Overview

#### Briefly describe your request

Implement a page where we can test theories related to marketo forms. In particular, https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/1604#note_368531411

#### Describe why this update is being requested:

What problem(s) are you trying to solve? What are the goals?

1. Marketo is a third party marketing tool.
2. Third party marketing tools are blocked by privacy strict browsers, adblockers, firewalls, and impacted by cookie consent legislation such as GDPR / CCPA.

#### What is/are the relevant URL(s)

`https://about.gitlab.com/handbook/marketing/growth-marketing/marketo-test-static/`

_________

## Project Management

#### What is the due date AND WHY? Dates without reason are difficult to prioritize. If there is no due date, please be as specific as possible about a timeframe and need.

No specific due date but the sooner the better since forms directly impact growth.

#### Please identify the directly responsible individual (DRI), stakeholders, and roles

|Name|Role|
|------|------|
| `???` | DRI |
| `@brandon_lyon` | Marketing web developer |
| `@amy.waller` | Marketo tool lead |
| `@shanerice` | Analytics |
| `@j.carey` | Analyst | 
| `@jstava` | Product growth |

 ____________

## Audience

All visitors to about.gitlab.com

___________

## Promotion and Measurable Goals

#### What are the measurable key performance indicators (KPI)?

* `Form completions`
* `Self-managed trial signups`

_____________

## Relevant Documents/Information

* [Marketo form best practices](https://nation.marketo.com/t5/Product-Blogs/Really-finally-winning-the-Marketo-Forms-vs-Tracking-Protection/ba-p/244434)
* [Cookiebot improvements](https://gitlab.com/groups/gitlab-com/-/epics/681).

_____________

## Requestor Checklist

* [x] All sections have been filled out
* [x] All media and relevant documents have been linked or added
* [x] A due date and rationale for the due date has been added
* [x] Your team labels have been added

Story points: 2.0
Add promo banner to Google Solution page.

#### What is/are the relevant URL(s)

https://about.gitlab.com/solutions/google-cloud-platform/

#### Briefly describe the page/flow

Speaks to our partnership with Google Cloud

#### What is the primary reason for updating this page?

To add a banner that we have a speaking slot at Google Cloud Next On Air and encourage people to register through our link. We get the leads of anyone who registers through this link and the event is free. 

#### What exactly do you want to change on this page?  
To add a banner that we have a speaking slot at Google Cloud Next On Air and encourage people to register through our link. The banner should say "Join our session at Google Cloud Next On Air" and link to https://cloud.withgoogle.com/next/sf/?utm_source=google&utm_medium=partnerreferral&utm_campaign=FY20-Q3-global-next-operational-er-nextonair_em_partner&utm_content=GR_1_RegOpen_ERC&utm_term=GitLab&pcn_code=0014M00001h35gDQAQ 

#### What are the KPI (Key Performance Indicators)

Get 50 leads.

Story points: 1.0
Users experiencing refresh loop when loading 13.1 blog post

#### What is/are the relevant URLs or emails?

https://about.gitlab.com/releases/2020/06/22/gitlab-13-1-released/

#### Briefly describe the bug

Details from the community members who are experiencing this issue can be found on the HackerNews thread re: the 13.1 release post: https://news.ycombinator.com/item?id=23604638

#### What are the steps to reproduce the bug

From AaronFriel:

> If anyone from GitLab is reading this, these pages are locked in a refresh loop. I can't read the content because it is scrolling/moving slightly with every refresh which is happening constantly.
> Latest version of Chrome stable, uBlock Origin in default config, HTTPS Everywhere, React/Redux devtools are the extensions I have installed.
> 
> I let the page run for 30 seconds and:
> 
> * CPU usage on two cores was at 100%
> 
> * 2,943 requests were made for 319 MB of resources over 30.06 seconds
> 
> A staggering rate of 100 requests per second that persists indefinitely - I have no reason to believe the refresh loop is broken at any point.

From Earwig: 

> Same issue here as the original post and similar extensions. I followed the suggestion of clearing cookies for about.gitlab.com and it doesn't help.


#### Please provide any relevant screenshots or screencasts

Video of related issue that was reported in Slack by @caalberts 

![screen-capture-1](/uploads/25bd4e78f1d8d569d0faef568bc9d02f/screen-capture-1.mov)

#### What is your window size, browser, operating system, and versions

* Safari
* Firefox
* Chrome

#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state?

* (One report) If I open up the page in incognito, I see two requests in the network tab for the page.
* (Another report) Incognito appears to be working as expected.

#### What is your geographic location

* India
* Colorado

#### What type of network are you connected to?

* Unspecified
* Wifi Comcast (Colorado)

#### What cookie values have been observed by users?

* CookieConsent = -1
    * The user is not within a region that requires consent - all cookies are accepted.
* CookieConsent = -3
    * Unknown cause.


#### 2020-07-06 Potentially related issue?

Upon further investigation, I'm seeing some 301 redirects.

Story points: 3.0
Cleanup demo experiment

## Overview

#### Briefly describe your request

Cleaning up the files named `OLD` and the experiment on the /demo/ page cc @cwoolley-gitlab

#### Describe why this update is being requested

Assisting the Static Site team with updates to the build process in order to facilitate efficient builds and monorepo projects.

#### What is/are the relevant URLs or emails?

https://about.gitlab.com/demo/

## Project Management

#### What is the due date and why? If there is no due date, please be as specific as possible about a timeframe and need.

`ASAP`, lack of progress is blocking other teams' work.

<!--
Please note: Without sufficient lead time we will likely be unable to meet your deadline. Marketing web development is currently an impacted resource.

Example: Our due date is XXXX-XX-XX. We want to launch this page before a trade show happens on YYYY-YY-YY. We need a week of lead time to coordinate a press release before the event.
-->

#### Please identify the directly responsible individual (DRI), stakeholders, and roles

<!--
Who should we be asking for questions and reviews?
-->

|Name|Role|
|------|------|
| `@cwoolley-gitlab` | `DRI` |
| `@brandon_lyon` | `developer` |

## Requestor Checklist

* [x] All sections have been filled out
* [x] All media and relevant documents have been linked or added
* [x] A due date and rationale for the due date has been added
* [x] Your team labels have been added

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Bug on the trial banner (FE)


<!--

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/2020/05/22/gitlab-13-0-released/

#### Briefly describe the bug

Footer overlays "GitLab Free Trial" banner:

![bug-banner](/uploads/e0771b680f4873870a6274ed112f7850/bug-banner.mp4)

#### What are the steps to reproduce the bug

Scroll to the end of the page and look at the "GL trial" banner. It's overlayed by the footer.

#### 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/)
-->

#### What is your window size, browser, operating system, and versions

- macOS Catalina 10.15.5 (19F101)
- Chrome Version 83.0.4103.61 (Official Build) (64-bit)
- Large screen

#### What device are you using

MacBook Pro

#### Have you tried a fresh incognito window? Could this be related to cookies or account type/state?

Reproduces on Firefox Developer 78.0b9 (64-bit)

#### What browser plugins do you have enabled?

Doesn't seem related

#### What is your geographic location

Doesn't seem related

#### What type of network are you connected to?


* Wifi at home.


<!-- 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
Add the blocked resource warning to more locations

## Overview

#### Briefly describe your request

Add the blocked resource warning to the education solutions page.

![Greenshot_2020-05-28_08.01.07](/uploads/34f37988cc5a56560dae579ef0cd6923/Greenshot_2020-05-28_08.01.07.png)

#### Describe why this update is being requested:

Users aren't aware they need to accept cookies to view the form to apply.

#### What is/are the relevant URL(s)

* https://about.gitlab.com/solutions/education/
    * Other pages which are built similarly using shared code (exact URLs unknown)
* https://about.gitlab.com/free-trial/self-managed/
* https://about.gitlab.com/demo/
* https://about.gitlab.com/developer-survey/
* https://about.gitlab.com/company/contact/

_________

## Project Management

#### What is the due date and why? If there is no due date, please be as specific as possible about a timeframe and need.

ASAP. It's a quick fix and we keep getting asked about this, particularly for German users.

#### Please identify the directly responsible individual (DRI), stakeholders, and roles

|Name|Role|
|------|------|
| `@brandon_lyon` | `DRI` |

 ____________

## Audience

#### Who is primarily looking at this page AND what will they they be doing with it/what do we want them to do? Write specifics AND check off below anything relevant

**Specific Details**
<!-- Write in specifics. Example: People looking for more info about devsecops", or "potential event attendees vs event sponsors. Want them to sign up for event"
-->
`SPECIFICS`

**Person**
[x] Individual (looking for information on GitLab features, events, community, documentation)
[x] Person representing company (looking for a solution for DevOps, getting a trial, etc)
[ ] PR/Media
[ ] Investors/Board members

**How much do they know about GitLab?**
[x] Very new or first time visiting (most likely came from ads or search)
[ ] Has been here a few times 
[ ] Very familiar (likely looking for documentation, resources, new features, community projects, etc. )

**Special Considerations (check if applicable):**

[ ] Government
[x] Outside U.S. (primary)
[ ] Direct Competitive (ex: OctoCat Campaign}

___________

## Promotion and Measurable Goals

#### What are the measurable key performance indicators (KPI)?

* `Form signups`

#### Where do you expect traffic to come from?

* `Organic`

___________

## Project Deliverables

#### What are the project must-haves?

* [x] Blocked resource warning added to the page

_____________

## Requestor Checklist

* [x] All sections have been filled out
* [x] All media and relevant documents have been linked or added
* [x] A due date and rationale for the due date has been added
* [x] Your team labels have been added

Story points: 1.0