giseldo/neodataset huggingface dataset:
DevOpsTools Comparison Pages - Development

This is issue is related to all development 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 design of this page here: 


# 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).

Figma Design Link: https://www.figma.com/file/kQjjTnRL6aFhhvdE4Zd4AO/GitLab-vs.-GitHub?node-id=0%3A1

Story points: 10.0
2020Q2 update website issue templates and documentation

### Broad goals

* Communicate how to work with the marketing Brand and Digital team.
* Improve the quality of issues received in the www-gitlab-com repository.

### Pain points

* "How do I create a website request?"
* "Which template do I use for what?"
* Documents are TLDR.

### Specific goals, default issue template

* People aren't reading. Replace this copy with a simple "Please select a template from above. Issues without a template are unlikely to be prioritized"
* Link to B&D as the repository DRI.
* Each template should describe it's use, first thing.
* Improve clarity of template titles ("be as explicit as possible").
* Consolidate templates & reduce choice overload.

### Specific goals, other issue templates

* Add more sections...
    * What are the pain points?
    * What company or team goals/initiatives does this align with?
    * **What are the deliverables?**
        * Explore the use of checklists, particularly in the case of deliverables.
    * **Directly ask for MOSCOW** instead of indirectly asking...
        * What are the must-haves?
        * What are the should-haves?
        * What are the could-haves?
        * What are the wont-haves?
* Consolidate templates & reduce choice overload.
    * Streamline templates based on organic changes made over time via observation, similar to examples:
        * Issue description in [this issue](https://gitlab.com/gitlab-com/www-gitlab-com/issues/6294)
        * "Deliverables" comment in [this issue](https://gitlab.com/gitlab-com/marketing/corporate-marketing/-/issues/1596#note_274860052)
* Add more information and requirements around due-dates.
    * Emphasize the use of phases and MVC.
* Add section for requesting opengraph images so this isn't an afterthought.
* Consider hiding titles and examples behind comments so that they aren't visible when someone forgets to delete sections.
* People often aren't reading. Consider limiting details.
    * Remove sections which aren't commonly used or at the very least move them towards the bottom of the issue template.
    * Similarly move the most used sections towards the top.
* Make labels as automated as possible.
    * Only require the most necessary labels, others can be added during grooming.
* Reassess which parts should be opt-in vs opt-out.
    * switch cc pings @ gl-website from opt-out to opt-in.
    * switch from "manually add labels" to opt-out of labels.
* Add breadcrumbs such as "if you require any redesign to this page, you're using the wrong template. Please use X instead [link]."
* Consider adding collapsible sections.
* Add a label identifying which template was used. Certain templates already have this, many do not. This will help provide metrics around use.

### Deliverables

- [x] Updated default issue template.
- [x] Updated individual issue templates.
- [x] Search documentation for links to old templates and replace with new links.

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 4.0
Update & to and in location factor targets

This repository primarily relates to the logged out marketing website
https://about.gitlab.com/ 
and company handbook
https://about.gitlab.com/handbook/ 
This is not the repository for requests related to docs.gitlab.com, product, or other parts of GitLab.

## Issues should identify The Five W's
https://en.wikipedia.org/wiki/Five_Ws
who, what, when, where, and why.

We also recommended MoSCoW sorting
https://en.wikipedia.org/wiki/MoSCoW_method 
things the issue Must, Should, Could, and Won't do.

* Please apply appropriate labels or your issue may not be sorted into appropriate boards.
* Please select a template from the top left menu before continuing.

Note there is a blank template
https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=blank-template
pre-populated with labels and @ mentions.

If you do not select an appropriate template then your issue might get lost. For more information about our workflows, please reference the handbook for the marketing website
https://about.gitlab.com/handbook/marketing/website/ 
website issue labels 
https://about.gitlab.com/handbook/marketing/brand-and-digital-design#working-with-issues-groups-and-labels 
or reference your team documentation.

If you are not using a template then please add appropriate labels and @ mentions. Issues lacking known labels may not appear on work boards.

### FAQ:

Q: Which template should I use?

A: Most people will use the template for bug reports or requesting page updates. Occasionally redesigns, new pages, feature proposals, or new templates are requested. There are also templates for writing various kinds of blog posts including the unfiltered category.

The rest of the templates are specific to team, role, or special occasion.

Q: When will you get to this issue?

A: Your issue will be refined and then prioritized relative to other issues. Marketing's website development team is currently an impacted resource.

Q: I have a hard deadline **related to contracts or events**. How do I ensure the issue gets done by then?

A: Apply the label "hard-deadline" and assign a due date BEFORE the actual deadline. Leave a comment in the issue or description mentioning that it's time-sensitive and needs to be finished before the date in question if possible.

Q: How does marketing's web development team determine priority levels?

A: Please see our prioritization documentation
https://about.gitlab.com/handbook/marketing/brand-and-digital-design/#prioritization

Q: How do I link to an issue template?

A: https://gitlab.com/gitlab-com/www-gitlab-com/issues/new?issuable_template=name-of-template

Q: How do I edit this FAQ? I have another question.

A: Submit an issue
https://gitlab.com/gitlab-com/www-gitlab-com/issues/new 
with FAQ in the title and assign it to @ brandon_lyon or another member of the website team
https://about.gitlab.com/handbook/marketing/website/

Story points: 1.0
Show the "You're running out of CI minutes" warnings on relevant pages in GitLab

We currently only show the "You're running out of CI minutes" banner warning on the Project overview page. Let's change that so that we'll also show it on Group overview, Projects Dashboard (`/dashboard/projects`), Groups dashboard pages (`/dashboard/groups`). Let's show these banners only to the owner of the group that's running out of CI minutes.

We're updating the content and the styling of the banners via gitlab-org/growth/product#1514

## Proposal

| Group overview | Groups dashboard | Projects dashboard |
|----------------|------------------|--------------------|
| ![group-overview](/uploads/5aa8d929a9f5d27166100b40be096901/group-overview.jpg) | ![groups](/uploads/80771f8fdcddf870d807d2daeeb11e40/groups.jpg) | ![projects](/uploads/a2e2f0812f657d9de633a06ff70afcf0/projects.jpg) |

Changes:
* Depending on the percentage remaining (30 or 5, see https://gitlab.com/gitlab-org/growth/product/-/issues/1514/designs#banner-warnings-update), show either a warning- or a danger-styled banner on Group overview of the group that is running out of CI minutes. Show it only to group owners.
* Depending on the percentage remaining (30 or 5), show either a warning- or a danger-styled banner on Groups dashboard. Show it only to group owners.
* Depending on the percentage remaining (30 or 5), show either a warning- or a danger-styled banner on Projects dashboard. Show it only to group owners.

Let's use vertical margins of 16 pixels to separate the banner from the main nav and the content of the page. 

Story points: 1.0
Ecosystem Team page in Google results is invalid

When Google searching for `gitlab ecosystem`, the first hit is https://about.gitlab.com/handbook/engineering/development/enablement/ecosystem/, which is a 404:

![gitlab_ecosystem_-_Google_Search_2020-03-19_10-39-11_1_](/uploads/326b0ed978afc00155fb9fad8abd021e/gitlab_ecosystem_-_Google_Search_2020-03-19_10-39-11_1_.png)

The correct page is https://about.gitlab.com/handbook/engineering/development/dev/ecosystem/

Story points: 1.0
Pricing page A/B test

Implement [new pricing page](https://gitlab.com/gitlab-org/growth/team-tasks/uploads/1e276f257d2bf72c3a61fec75868fa52/image.png) as experiment.

Parent issue: https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/73

MR: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/44494

Story points: 3.0
Followup AB test to valuedriver

This issue is a followup for https://gitlab.com/gitlab-com/www-gitlab-com/issues/6595

## Relevant URL

* https://about.gitlab.com/just-commit/reduce-cycle-time/

## AB testing LaunchDarkly documentation

* https://docs.google.com/document/d/1_XztSRs_CMBulZDvrVbSHmCjtOnL0xd6gFUEVo_NxoA/edit?usp=sharing

## Results of prior test found in

* https://gitlab.com/gitlab-com/marketing/corporate-marketing/issues/1596#note_299047010

## Requested deliverables

* Switch the main nav so it doesn't have the free-trial CTA (free trial is distracting).
    * The thank you popup after submit could have free-trial as secondary CTA.
    * Make sure there is only one CTA.
        * Remove the "ready to talk" section at the bottom of the page.
* Change the download CTA phrase from "Read the Whitepaper" to "Get your Whitepaper".
    * Suggested copy: any action word that doesn't sound like work (ie not "read")
* Try different report screenshots or potentially animations, have a more graphical cover.
    * Ask Luke for suggestions, we could create a cover, perhaps some synergy of the graphic with the CTA button.
* Try moving the bullet points into the purple section before the CTA button (what you will learn is important).
* Change the popup title to match the button (Get your whitepaper).
* Bump up the font size of and adjust copy to "trusted by 100,000+ organizations worldwide" and make it bigger.
* Check with @ mnguyen4 to ensure copy is consistent with what interested them in the first place.

## Valuedriver reference material

* https://docs.google.com/presentation/d/1adRX6Vua7LhpZNgG6scqn4uH8Mz3rDVhNGBUU8RFZ2o/edit#slide=id.g7e88ccd42e_0_57

## Notes:

* Please do not run this test for too long so we don't use up our allocated MAU (monthly active users). Last time we ended up with ~ 2000 hits (1,000 each) in ~ 5 days for this particular page which should suffice.
* Shane Rice suggested removing the form from the popup and leaving it on the page. That's a good suggestion but for efficiency & time sensitivity I would suggest that as a followup and doing this first.

Story points: 4.0
Unfiltered posts with "featured" appearing on /blog

Before the new /blog design, posts in the `unfiltered` category did not appear on /blog. I think if the post contained `featured: yes` in the frontmatter, it resulted in a blank block on the index page (not ideal, which is why we do have documentation to remove it: https://about.gitlab.com/handbook/marketing/blog/unfiltered/#review)

I noticed before a new featured post was published today that an Unfiltered post (where `featured: yes` had been left in the frontmatter) was appearing as the featured post on /blog.

Is there a way to prevent this? As mentioned above we do ask people not to include this in the frontmatter but it does happen occasionally.

Story points: 2.0
Add Hotjar polls to the about website

Per @sbouchard1 this issue will explore the addition of Hotjar polls to the website as useful way to gather feedback privately in addition to potential use as a KPI.

## Requirements

Starting with just one poll for now:

- [ ] Discuss with other teams where polls have been used, where we might benefit from their use, tips & tricks, etc.
- [ ] Identify [type of poll](https://help.hotjar.com/hc/en-us/articles/115011624547-Creating-Your-First-Poll).
- [ ] Identify questions for poll.
- [ ] Identify pages where the poll will or won't be served.
- [ ] Identify where the poll will live on the page for desktop/tablet/mobile.
- [ ] Implement the form.
- [ ] Create a followup issue to identify next steps (what do we do with the info gathered, what other polls should we make, create documentation, create an issue template for requesting polls, etc...)

## Note
* Need to be careful Hotjar feedback loops do not negatively impact conversion (funnels, etc)
* Also need to avoid any conflicts with chat bot (@bethpeterson for awareness)

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 2.0
Migrate only/except CI to rules

Many of our CI jobs in .gitlab-ci.yml use the only/except(advanced) feature described here: 
https://docs.gitlab.com/ee/ci/yaml/#onlyexcept-advanced

This feature is marked as "an alpha feature, and it is subject to change at any time without prior notice!"

Only/Except is [planned to be deprecated](https://docs.gitlab.com/ee/ci/yaml/#onlyexcept-basic).

Either-way, I think we should migrate all of our CI jobs to use rules instead of the only/except feature. Rules allow for more complex pipelines and will set us up for a monorepo build process. 
https://docs.gitlab.com/ee/ci/yaml/#rules

See also [original issue for rules](https://gitlab.com/gitlab-org/gitlab/issues/27863)

Story points: 2.0
[new webpage] - Topic page -  /version-control

### [COPY](https://docs.google.com/document/d/1T2_3fEZfGPY_1TvpHGYz0Ku_MR7lsO-hMdMvdej4tT4/edit#)

#### What is/are the expected URL(s)

/topics/version-control/

Does this match existing strategies? **Yes** Has keyword research been done? **Yes**

#### Briefly describe the page/flow

This is a topic page to provide awareness-level information. It mirrors the [agile delivery](https://about.gitlab.com/agile-delivery/) page.

#### If applicable, do you have any user journeys, wireframes, prototypes, content/data?

I have a [google doc with a wireframe and content](https://docs.google.com/document/d/1T2_3fEZfGPY_1TvpHGYz0Ku_MR7lsO-hMdMvdej4tT4/edit) (it's still in the planning stage). it'll be similar to this [doc for the agile delivery page](https://docs.google.com/document/d/1UxcdvnRAIKVPln-Fgo_LHKwc8mMQ-QDXGjacO2pqbhU/edit#)

#### What is the primary purpose of this page/flow?

- increase awareness
- drive people to the pathfactory path 

#### What are the KPI (Key Performance Indicators)

- number of sessions

#### What other purposes does this page/flow serve, if any?

- capture emails for campaign funnels

#### What information is this page/flow trying to convey?

- what is scm 
- what are the benefits

### Who is the primary audience? Be specific.

-  prospective customers
-  developers
-  devs learning about scm

#### Where do you expect traffic to come from?

- organic search
- blog posts

#### Please provide some example websites for design guidance.

- https://about.gitlab.com/agile-delivery
- https://about.gitlab.com/devops


Story points: 3.0
Document kramdown abbreviation syntax in handbook

As documented in https://gitlab.com/gitlab-com/www-gitlab-com/issues/4762, usability of acronyms is limited when the definition is made in place on a long document. Kramdown already supports a [lightweight markup for abbreviations](https://kramdown.gettalong.org/syntax.html#abbreviations) but it is fairly opaque to the user. 

## Proposal

Update the handbook to include specific usage of the Kramdown abbreviation syntax until we can build a more automated solution as recommended in #4762

Story points: 1.0
Improve styling of acronyms

## Problem to solve

The display of acronyms defined in the handbook [using Kramdown's abbreviation syntax](https://kramdown.gettalong.org/syntax.html#abbreviations) could use some help. Currently, there is a combination of a dotted border and underline. The styling should make the abbreviation stand out but remain consistent with the rest of the site. 

Current display on the handbook: 

![Screen_Shot_2020-02-10_at_2.43.32_PM](/uploads/1ec147b116a3bb89a837cca033ff1863/Screen_Shot_2020-02-10_at_2.43.32_PM.png)

## Proposal

Update the styling to remove the double dashed/dotted border. Start by removing the unstyled user agent text-decoration and then evaluate the legibility of the user-defined style.

Story points: 1.0
Investigate feature flag AB testing tools

Relates to https://gitlab.com/gitlab-com/www-gitlab-com/issues/6151 and https://gitlab.com/groups/gitlab-com/-/epics/290

This issue will investigate if we can use LaunchDarkly as an A/B test tool and attempt implementation.

Always be thinking MVC.

- [x] Sign up for trial accounts and create simple tests to familiarize yourself with the tools.
- [x] Assess what (if any) additional items are required for implementation.
- [x] Implement a test to verify the chosen tool is functioning as expected and evaluate the efficacy of the tool.
- [x] Ensure necessary tracking is in place (analytics, heatmaps, and test significance).
- [x] Ensure this plays nicely with cookiebot.
- [x] Document relevant processes and responsibilities related to the new tool(s).

Related to the documentation item, here's a video about [managing feature flags at full scale](https://www.youtube.com/watch?v=uFW4SSRtkUU).

<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 6.0
Create a dashboard in Periscope for blog pipeline metrics

We need to create a pipeline metrics dashboard in Periscope specifically to the blog child pipeline.

The dashboard should be based on the existing one for all of the website: https://app.periscopedata.com/app/gitlab/561277/WIP:-www.gitlab.com-Pipeline-Metrics

This issue is dependent on https://gitlab.com/gitlab-com/www-gitlab-com/issues/6355

Story points: 2.0
Upgrade www-gitlab-com repo to Ruby 2.6.5

Upgrade the `www-gitlab-com` repo to Ruby 2.6.5, to match the recent upgrade of the `gitlab-org` repo.

Based on a [slack question](https://gitlab.slack.com/archives/C8HG8D9MY/p1579047921205700), there doesn't appear to already be an issue for this.

This should be straightforward.  Looking at the history of `.ruby-version`, it looks like only a couple of changes were needed for the last upgrade.

Story points: 2.0
Provide a quicker way to open the Web IDE from a Handbook page

## Problem to solve

Handbook pages offer a quick way to view the source file in the repository or open the source file immediately in the web IDE. 

![Screen_Shot_2020-01-24_at_4.04.24_PM](/uploads/4807b415b3776dc9b33916a40e3cd1fd/Screen_Shot_2020-01-24_at_4.04.24_PM.png)

However, this functionality is found in the last 40px of the page, below the footer, and over 900px removed from the content itself. Users would benefit from a more easily accessible way to transition from reading to editing handbook content.

## Proposal

Building off the work in #6027 we should add two buttons to the popover when text is highlighted on a handbook page. One icon to open the file in the file browser. Another to open it in the web IDE. 

Something like this: 

![Mockup](/uploads/afeb42e4caa1a59f088137b7eda31a99/Artboard.png)

## Implementation details

* The twitter/social sharing options should be visually separated from the editing options in order to distinguish between the intent for each
* We should not remove the links from the bottom of the page


## What comes next?

* The web IDE button should take the user to the exact line of code that matches their selection

Story points: 1.0
Create separate Middleman instance for blog

## Who
The Static Site Editor Group and Brand and Digital Design team are working together to create monorepo structure for www-gitlab-com. 

## What
We are creating a distinct Middleman build for just the blog. By isolating the blog into separate middleman build, we can start to develop blog centric features for just this part of the site.

## Why
We are doing this so the blog becomes isolated from other parts of the website and deployment time are reduced. This is also a required step toward creating a true monorepo structure for www-gitlab-com

## When
Based on the [Monorepo Approval issue](https://gitlab.com/gitlab-com/www-gitlab-com/issues/6213) and timeline for deliverables, we need to complete this by Feb 3rd

## References

* ["how to share assets with multiple sites and allow "local" overrules?" - middleman issue](https://github.com/middleman/middleman/issues/1902)

Story points: 4.0
Standard for helper indicators in KPI/RPI charts

We need to come up with a standard to represent helper indicators for KPI/PIs. Examples 

* Number of bugs in timing KPIs
* Cost/user and % of rev indicators 


### Proposal 

Taking into account https://about.gitlab.com/handbook/engineering/quality/performance-indicators/#average-age-of-open-s1-bugs 
* Instead of 2 lines intersecting it would be best to have
  1. A bar chart to represent age => purple to indicate primary indicator 
  1. A red line for target age => KPI/PI target
  1. Area chart represent number of open bugs per month => grey? to indicate supplemental indicator
* Using purple to designate primary indicator as a constant formatting
* Grey color for supplemental indicator

#### Mockup
![Screen_Shot_2021-04-09_at_3.41.09_AM](/uploads/1a5155ed2bf82533abb9379356845441/Screen_Shot_2021-04-09_at_3.41.09_AM.png)

@lmai1 @davis_townsend for your review and feedback kindly :slight_smile:

Story points: 1.0
Enterprise page feature list has repeated bullet points

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/enterprise/`

#### Briefly describe the bug

Example: A link is broken and when hovering over it the color is the wrong color and poorly aligned.

`See the screenshot below for details. Two sections of the feature list have duplicate bullet points.`

#### 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/

![Greenshot_2021-04-07_15.02.05](/uploads/4be1b7d22d75e221f1a234af863c40e0/Greenshot_2021-04-07_15.02.05.png)


<!-- These labels will be automatically applied unless you edit or delete the following section -->

Story points: 1.0
Feature Unfiltered Post: How we tested a feature that affected GitLab

<!-- PLEASE READ: See https://about.gitlab.com/handbook/marketing/corporate-marketing/content/editorial-team/#featuring-unfiltered-posts for details on the process for featuring Unfiltered blog posts on the main GitLab blog.-->

<!-- Add a link to the original Unfiltered blog post and @ mention the author -->

How we tested a feature that affected (almost) all parts of GitLab
https://about.gitlab.com/blog/2021/03/17/collaborating-on-a-cross-stage-feature/

Story points: 2.0