giseldo/neodataset huggingface dataset:
Update social previews to new branding

## Goal
There are also social previews on some pages that use the old GitLab logo branding.

I saw it recently on LinkedIn with a URL to page.gitlab.com - and it sometimes seems to happen with about.gitlab.com/handbook too. I could not debug further yet.

An easy way to test social preview cards and tags is https://www.opengraph.xyz/ (documented in the [Developer evangelism handbook](https://about.gitlab.com/handbook/marketing/community-relations/developer-evangelism/social-media/#social-card-validators)).

#### Please provide more information related to this engineering request
Make sure the information you provide is relevant for your request. If unsure, please provide all the fields. Add/remove rows as needed.

## Which page(s) are involved in this request?
* page.gitlab.com
* about.gitlab.com

## In scope
What is within scope of this request?

- [ ] Ensure social previews for www-gitlab-com are using new branding (new logo)
- [ ] Ensure social previews for Buyer Experience are using new branding (new logo)
- [ ] Ensure social previews for page.gitlab.com are using new branding (new logo)

Story points: 2.0
Slippers devops stage icons rename to simplify template logic in Buyer Experience repo

The following discussion from !1651 should be addressed:

- [ ] @mpenagos-ext started a [discussion](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/1651#note_1269445712):  (+1 comment)

    > I think it would be better to rename the icons in slippers rather than having this specific logic for these stages :thinking: it's just a small nitpick so I'll mark the MR as approved!

Story points: 2.0
Update Icons on Get Started page

## Goal
As per the comment thread in [this MR](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/merge_requests/734#note_1016611043), we're waiting for the latest slippers icons to be released so we can make some updates on this page. 


## Page(s)
Which page(s) are involved in this request?
* about.gitlab.com/get-started

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @mduque-ext 
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 1.0
UX: Solutions Landing Page / Design / MVC 1

## Goal
We would like to update the [/solutions](https://about.gitlab.com/solutions/) page which will improve customers' product understanding as measured by CTA clicks further down the purchasing path.

## Page(s)
Which page(s) are involved in this request?
* [/solutions](https://about.gitlab.com/solutions/)

## Workfile
* [Figma file](https://www.figma.com/file/NFrVFwBzzRKiFas26f9uYU/Solutions-%2F-Refresh?node-id=2102%3A8148)
* [Copy doc](https://docs.google.com/document/d/1EP8tAlmI7QX1YfnE4J2lPYN29UNf__SLXOHdZjtgrQw/edit?usp=sharing)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @KristinaWeis @jhalloran   
- [ ] Informed: @fqureshi `@justin.vetter` `@dennischarukulvanich` `@hsmith-watson`

## In scope
What is within scope of this request?

- [ ] Page redesign


## Out of scope
What is out of scope and not part of this iteration?

- 


## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering

Story points: 4.0
ENG: Category Leadership / Add CTA to header area

## Goal
We would like to add relevant CTAs to the header area of the /topic pages which will reduce exit rates as measured by analytics.


## Page(s)
Which page(s) are involved in this request?
- about.gitlab.com/topics/devops/
- about.gitlab.com/topics/gitops/
- about.gitlab.com/topics/ci-cd/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: 
- [ ] Consulted: @ncregan @dennischarukulvanich @Tinaliseng 
- [ ] Informed: @fqureshi @justin.vetter 

## In scope
What is within scope of this request?

- [ ] ENG - Add buttons under the intro copy
- [ ] CNT - Provide links

![Screen_Shot_2022-07-06_at_2.39.31_PM](/uploads/d373987ea0bc5133bc0455bc817b836f/Screen_Shot_2022-07-06_at_2.39.31_PM.png)

## Out of scope

- Not in scope 1
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [x] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering

Story points: 1.0
Access to Sisense and Periscope

## Goal
We would like to acquire access to Sisense and Periscope to process data from the the `/gitlab-com/marketing/digital-experience` group. Then let's set up a dashboard using existing issue label data. This will enable our team to learn how to use these platforms and make informed decisions while we [implement and measure MRs by type](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1021). 

### Resources
- https://about.gitlab.com/handbook/business-technology/data-team/platform/sisensecdt/ 
- https://app.periscopedata.com/app/gitlab/976854/Merge-Request-Types-Detail  

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker @justin.vetter 
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Submit a group access request to Sisense for @mpreuss22 @dennischarukulvanich @justin.vetter @laurenbarker and @fqureshi 
- [ ] Submit a group access request to Periscope for @mpreuss22 @dennischarukulvanich @justin.vetter @laurenbarker and @fqureshi 
- [ ] Set up a dashboard that pulls in existing issue label data from `/gitlab-com/marketing/digital-experience` 
 
## Out of scope
What is out of scope and not part of this iteration?
- [ ] Creating new labels
- [ ] Creating dashboards to measure MRs by type


## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [x] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 1.0
Blog cards category is white

## Goal
We would like to X which will improve Y as measured by Z. Why is this changed needed?

### Describe the Bug
At the bottom of our blog posts there is section displaying blog post cards users can click. These blog post cards display the category. This text is white resulting it being unreadable. 

![Screen_Shot_2022-07-06_at_10.00.26_AM](/uploads/3160205b0d0be68b476b93a77452f3ef/Screen_Shot_2022-07-06_at_10.00.26_AM.png)

### What's my browser? 
Share your browser infromation from https://www.whatsmybrowser.org/b/M528L

## Page(s)
Which page(s) are involved in this request?
* All blog posts

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [x] Engineering

Story points: 2.0
Redirect Gitlab 15 Reg Page

## Goal
We would like to redirect the Gitlab 15 Reg Page to the on demand page which will improve customer ability to access the ondemand event as measured by video views/downloads.


## Page(s)
Which page(s) are involved in this request?
* `[GitLab 15 registration page--source](https://about.gitlab.com/fifteen/)`
* `[GitLab 15 on demand event page--destination](https://page.gitlab.com/fifteen.html)`


## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `@kbolton1`
- [ ] Consulted: `@cblake` @khartline 




## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ X] Engineering

Story points: 1.0
UX: Features landing page / Design Iteration / MVC 4

## Goal
After conducting [UX research](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1023) on the [/features](https://about.gitlab.com/features/) landing page, we would like to make additional updates which will improve how potential customers learn about the Features that GitLab offers and move them closer to our [conversion goals](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/1067#note_1016931422).

### Jobs To Be Done
* **Situation**: *When I am considering GitLab*
* **Motivation**: *I want to review the features that are relevant to my needs*
* **Outcome**: *So I can make an informed purchasing decision.*

## Approach
* We will explore taking an e-commerce approach to how we design the UI for this page
* Revisit the grouping and move away from stages to align with the recent /solutions groupings and pricing tiers

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/features/

## Workfiles
- [Figma file](https://www.figma.com/file/oFG1Yau7Sh4szuKTw13hiO/Features-%2F-Refresh?node-id=1083%3A8910) - WIP

## In scope
What is within scope of this request?

- [ ] Design updates


## Out of scope
What is out of scope and not part of this iteration?

- 

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: `@cblake` `@davistye` `@supadhyaya` `@awaters3` @jhalloran @dennischarukulvanich  
- [ ] Informed: @fqureshi @justin.vetter 

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering

Story points: 10.0
Sidebar navigation broken on Commit landing page

## Goal
We would like to X which will improve Y as measured by Z. Why is this changed needed?

### Describe the Bug
The sidebar on the commit landing page is floated to the center.

### What's my browser? 

https://www.whatsmybrowser.org/b/M528L

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/events/commit/
* https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/sites/uncategorized/source/events/commit/index.html.haml

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

## Additional Information

We are in the process of [migrating events over to the Buyer Experience repository](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/953). Therefore this issue is for making the page usable but we will be doing a full rebuild shortly.

Story points: 2.0
ENG: Revert depreciation of this page /services/implementation/enterprise/

## Goal
We would like to revert the depreciation of this page https://about.gitlab.com/services/implementation/enterprise/

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* https://about.gitlab.com/services/implementation/enterprise/

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @jgarc 
- [ ] Consulted: @justin.vetter 
- [ ] Informed: `@bryan-may`

## In scope
What is within scope of this request?

- [ ] Revert the depreciation of page

## Out of scope
What is out of scope and not part of this iteration?


## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0
ENG: Launchdarkly: Iteration 2

## Goal
In trying to [run a test experiment](https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/503), we see that conversions are showing up as unique clicks. 

From Launchdarkly support:

> 1) What does the button/link do (Purchase button, opens a new page/website, etc.)?
> 2) Do you see the event ever fire (You can check this in both the debugger and the network tab of your browser console)
> 3) Are you using Do Not Track/Adblock?
> 
> If you are changing the URL upon click, you would have to use a custom conversion (Such as if you were submitting a form that redirects to a new page, etc.).

### Jobs To Be Done
* **Situation**: *When ...*
* **Motivation**: *We want to ...*
* **Outcome**: *So we can ...*

## Page(s)
Which page(s) are involved in this request?
* `[Page Title](URL)`

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Deliverable 1
- [ ] Deliverable 2

## Out of scope
What is out of scope and not part of this iteration?

- Not in scope 1
- Not in scope 2

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 5.0
Follow-up from "Release navigation version 1.0.36"

## What does this affect? Check all that apply.
- [x] Navigation
  - [x] Mobile
  - [x] Desktop
- [ ] Footer
- [ ] Other (please explain)

## Problem
There's a critical A11y issue as reported by the Axe devtools when run in this repo as shown in the screenshot below

![Screen_Shot_2022-06-29_at_16.20.53](/uploads/cad18b61bebd7cd70457e403160823d5/Screen_Shot_2022-06-29_at_16.20.53.png)

## Goal
We would like to solve the reported issue and have zero critical issues in the Axe devtools report

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: @laurenbarker 
- [ ] Informed: `Everyone`

Story points: 2.0
ENG: Release Post template - Brand refresh (post release) pt 1

## Goal

Iterate over the recently updated blog post release template to match the [Figma](https://www.figma.com/file/JzLrT0korZQuRmnCv7md4K/Release-template?node-id=2%3A53) design as close as possible 

| Element | Figma | Current |
| ------ | ------ | ------ |
| Update twitter link styling  | ![Screen_Shot_2022-06-22_at_13.29.20](/uploads/3fae0fd41c5bcffaffb31f0d0b43008d/Screen_Shot_2022-06-22_at_13.29.20.png)  | ![Screen_Shot_2022-06-22_at_13.26.45](/uploads/763ed556f122defbf391150739f6a280/Screen_Shot_2022-06-22_at_13.26.45.png)  |
| Gitlab MVP Profile Image and reduce width to match rest of sections | ![Screen_Shot_2022-06-22_at_1.07.23_PM](/uploads/fe8d5ade8cc89a0b8e5e4d53cc3bc8b5/Screen_Shot_2022-06-22_at_1.07.23_PM.png) |![Screen_Shot_2022-06-22_at_1.26.29_PM](/uploads/623f7b3236e16b6fd10d3963ac166efe/Screen_Shot_2022-06-22_at_1.26.29_PM.png) |
| SaaS Self Managed buttons | ![Screen_Shot_2022-06-22_at_1.08.22_PM](/uploads/3229786b44b6c48629cdc440daa7a17e/Screen_Shot_2022-06-22_at_1.08.22_PM.png) | ![Screen_Shot_2022-06-22_at_1.26.21_PM](/uploads/57b6afeb82412a704bd0fab0f3d924f6/Screen_Shot_2022-06-22_at_1.26.21_PM.png) |
| Images+Text Layout | ![Screen_Shot_2022-06-22_at_1.21.35_PM](/uploads/ebca12af5fc570b230c851358f35dc6b/Screen_Shot_2022-06-22_at_1.21.35_PM.png) | ![Screen_Shot_2022-06-22_at_1.22.06_PM](/uploads/af200b5216053f62686bdb1fab84197c/Screen_Shot_2022-06-22_at_1.22.06_PM.png) |
| Update "performance improvements" and "usability improvements" section headers | ![Screen_Shot_2022-06-22_at_13.29.56](/uploads/56a70b54d7a8c82226cf843cd953ad5f/Screen_Shot_2022-06-22_at_13.29.56.png) |  ![Screen_Shot_2022-06-22_at_13.29.49](/uploads/7c1d8860632d71445c6d6c40e1c1b9fc/Screen_Shot_2022-06-22_at_13.29.49.png) |
| Newsletter Structure | ![Screen_Shot_2022-06-22_at_1.24.33_PM](/uploads/d0a84824cda642e291bd7f912743e3db/Screen_Shot_2022-06-22_at_1.24.33_PM.png) | ![Screen_Shot_2022-06-22_at_1.09.04_PM](/uploads/a691247074e3f5043826289538d66eb5/Screen_Shot_2022-06-22_at_1.09.04_PM.png) |

### Jobs To Be Done
* **Situation**: Our recently updated release template still needs more work to match the intended brand refresh 
* **Motivation**: Align the release template with the brand refresh
* **Outcome**: When someone goes to our release page the brand matches our new brand refresh

## Page(s)
Which page(s) are involved in this request?
* [Release Post Example](https://about.gitlab.com/releases/2022/05/22/gitlab-15-0-released/)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`


## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [ ] Engineering

Story points: 4.0
UX: Solutions / CTA Block to Get Started pages

## Goal
We would like to add links to get to the Get Started pages on the Solutions pages.

### Jobs To Be Done
* **Situation**: *When a customer visits GitLab and wants to get started quickly*
* **Motivation**: *We want to show them ways to get started*
* **Outcome**: *So we can increase conversions*

## Page(s)
Which page(s) are involved in this request?
- Solutions pages

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @Tinaliseng 
- [ ] Consulted: @ctsang-ext, @jhalloran 
- [ ] Informed: @fqureshi @laurenbarker

## In scope
What is within scope of this request?

- [ ] Design for ENG

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [X] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering

Story points: 2.0
UX: Navigation to the Get Started pages

## Goal
We would like to add links to get to the Get Started pages.

### Jobs To Be Done
* **Situation**: *When a customer visits GitLab and wants to get started quickly*
* **Motivation**: *We want to show them ways to get started*
* **Outcome**: *So we can increase conversions*

## Page(s)
Which page(s) are involved in this request?
- [Figma design](https://www.figma.com/file/3n0nVcktFGeJd5m874qW1y/Get-Started?node-id=1225%3A13216)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @ctsang-ext 
- [ ] Consulted: @Tinaliseng @jhalloran @cblake 
- [ ] Informed: @fqureshi @laurenbarker

## In scope
What is within scope of this request?

- [ ] Design for ENG

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [X] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [x] UX Design
- [ ] Engineering

Story points: 2.0
GA4: Content Security Policy

## Goal
Related: https://gitlab.com/gitlab-com/marketing/digital-experience/buyer-experience/-/issues/922#note_1000045146

Events are not sending to GA4 on gitlab.com. This is the JS error message I receive:
> it violates the following Content Security Policy directive: "connect-src 'self'

@tywilliams 's recommendation:
> To resolve that, we'll need to update the content security policy in `lib/gitlab/content_security_policy/directives.rb`, [similar to how it was updated in this MR](https://gitlab.com/gitlab-org/gitlab/-/commit/6bb099039e20bca19de5f61ecf98bc51e0a3c858/#3fe66e137a17241d7e683542368b77aa4f8c7b8d_11_11) and make it compatible with whatever GA4 needs, [which I think is listed here](https://developers.google.com/tag-platform/tag-manager/web/csp#google_analytics_4_google_analytics).

## Page(s)
Which page(s) are involved in this request?

gitlab.com pages with GTM and OneTrust in the registration flow 

![Screen_Shot_2022-06-22_at_11.13.50_AM](/uploads/0c78c116efab5c4dc3fd357f6caad0ec/Screen_Shot_2022-06-22_at_11.13.50_AM.png)

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: @miraclebanks @tywilliams 
- [ ] Consulted: @dennischarukulvanich 
- [ ] Informed: @laurenbarker 



## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 5.0
Add link to Leadership Team to People Sub Navigation

## Goal
We would like to add a link to GitLab's Leadership team within the People Sub Navigation which will improve access to this information as measured by traffic to the Leadership page.


## Page(s)
Which page(s) are involved in this request?
* Main navigation -> Resources -> People

## DCI
[DRI, Consulted, Informed](https://about.gitlab.com/handbook/people-group/directly-responsible-individuals/#dri-consulted-informed-dci)

- [ ] DRI: `GitLab Handle`
- [ ] Consulted: `GitLab Handle`
- [ ] Informed: `Everyone`

## In scope
What is within scope of this request?

- [ ] Add Navigation item `Leadership` that links to https://about.gitlab.com/company/team/e-group/

## Requirements
What are the requirements for this request? Checklist below is an example of common requirements, please check all that apply and adjust as necessary:

- [ ] Copy writing
- [ ] Illustration
- [ ] Custom Graphics
- [ ] Research
- [ ] Data / Analytics
- [ ] UX Design
- [x] Engineering

Story points: 1.0