giseldo/neodataset huggingface dataset:
[Story][Web] Change link for Monday.com

<!-- Title suggestion: [Story][Web] Change link for Monday.com -->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user, when I click on the link to the Monday.com partner banner I am taken to the correct page.

## Details

Any related information

## Steps

- [x] Change href to https://mondaycom.grsm.io/mythictable

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.


- [ ] Clicking on Monday.com banner directs to correct location (https://mondaycom.grsm.io/mythictable)

    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Improvement] Improved Onboarding

<!-- Title suggestion: [Improvement] Name of improvement -->
<!-- Improvement issues are internal initiatives meant to improve code quality, tests, infrastructure or process -->

# Description

Streamline Onboarding

## The Problem

Slow. Too many drop outs

## Solution

Make it fu, interactive and fast

## Additional Information

## Steps

- [ ] TBD



<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story][Web] Discord Timestamp v2

<!-- Title suggestion: [Story][Web] Discord Timestamp v2 -->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user, I am notified of when I copy a discord time stamp to my clipboard and the table doesn't scroll on smaller screens

## Details

Any related information

## Steps

- [ ] Add toaster to click of discord button
- [ ] Adjust tables css to shrink on smaller screens

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

- [ ] Notification appears when button is clicked
- [ ] All elements fit when viewing on mobile screen
    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story][Web] Add March Financials

<!-- Title suggestion: [Story][Web] Add March Financials-->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user I can view March 2022 Financials

## Details

Add financials for March 2022

## Steps

- [ ] Add financials for March 2022

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

<!-- Some notes on Acceptance Criteria (AC)
If you are having issues creating Acceptance Criteria, please review [Some notes on Acceptance Criteria(AC)](https://gitlab.com/mythicteam/mythictable/-/wikis/qa/acceptace-criteria). Don't hesitate to ask for AC review or assistance in #qa, it's what we're here for.
-->

- [ ] March 2022 financials are accessible
    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story][Web] Add Spotlight for Roll vs. Evil event

<!-- Title suggestion: [Story][Web] Add Spotlight for Roll vs. Evil event  -->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user I am aware of the MT event for charity in partnership with RollvsEvil

## Details

Any related information

## Steps

- [ ] Create a spotlight for our event and partnership

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

- [ ] Spotlight is easily visible on the landing page for the site
- [ ] Users are able to join or watch our stream

    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story][Web] Add New Partners/Providers

<!-- Title suggestion: [Story][Web] Add New Partners/Providers -->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user I can see all the new partners and providers that have joined Mythic Table.

## Details

The new partners:
- monday.com
- browserstack
- libertas
- chronicles of elyria

## Steps

- [ ] Add new logos for new providers 
- [ ] Links for each logo work
- [ ] shrink logos to fit as needed

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

- [ ] New Partners/Providers Added and Linked
    - [ ] Monday.com
    - [ ] BrowserStack
    - [ ] Libertas
    - [ ] Chronicles of Elyria
- [ ] Logos fit and are visually appealing
    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story][Web] Find and Fix Disappearing 'X' on Modals

<!-- Title suggestion: [Story][Web] Find and Fix Disappearing 'X' on Modals-->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user, I can exit modals with an easy to see 'X' in top right corner

## Details

Any related information

## Steps

- [ ] Fix CSS for modal close 'X'

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

- [ ] Modals (Menu and Mail) are close-able with the 'X' and it appears in all browsers
    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story][Web]Add February 2022 financials

<!-- Title suggestion: [Story][Web]Add February 2022 Financials-->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user I can access the financial reports for February 2022

## Details

Any related information

## Steps

- [ ] Add Financial reports for February 2022

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

- [ ] Financial reports for February 2022 are added

<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story] [Web] Update/Fix Sitemap

<!-- Title suggestion: [Story][Web] Update/Fix Sitemap -->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user, I can navigate the entirety of MythicTable.com via the links available on the sitemap.

## Details

Update the links for the sitemap

## Steps

- [ ] Update each link in Sitemap
- [ ] Add missing links to Sitemap ie Reports 2022

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

- [ ] Each link in the sitemap takes user to correct page
    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story] [Website] Add February 2022 Report

<!-- Title suggestion: [Story][Web] Add February 2022 Report -->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user, I can read the latest report from MT for February 2022

## Details

Any related information

## Steps

- [ ] Add new report for February 2022

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.


- [ ] Report for February 2022 is added

<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story][Web] Missing 2021 Reports

<!-- Title suggestion: [Story][Web] Missing Reports for 2021-->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user, I can read reports for all the months of 2021. Right now, June through December are missing.

## Details

Any related information

## Steps

- [x] Add June Report
- [x] Add July Report
- [x] Add August Report
- [x] Add September Report
- [x] Add October Report
- [x] Add November Report
- [x] Add December Report
- [x] Link where needed

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

- [ ] All Reports are accessible from their intended locations.

    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story][Web]Missing Menu on Mobile

<!-- Title suggestion: [Story] Missing Menu on Mobile -->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user of the mobile site, I want to see the menu button

## Details

Missing menu on mobile version needs to be not missing

## Steps

- [x] Find issue in media query causing issue

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

- [ ] Restored Mobile Menu Button
    - [ ] Menu button is visible and function in mobile mode

    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story] [Web] Clicking OGN Image

<!-- Title suggestion: [Story] [Web] Clicking OGN Image -->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user, I expect to be taken to OGN site when I click on the OGN image

## Details

Currently a user clicking on the OGN image on https://www.mythictable.com/ogn takes me to the image file, not the OGN site.

## Steps

- [x] Change the image to link to the OGN site

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

- [ ] User can click on OGN image and is taken to OGN site

    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story] [Web] Fix Menu Modal

<!-- Title suggestion: [Story] [Web] Fix Menu Modal -->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a user, I can open the menu and exit it without selecting a link

## Details

Add an event listener to detect if user clicks outside of the modal and if so, closes the menu.

## Steps

- [x] Add event listener to close menu modal

## Acceptance Criteria (To be checked off **only** during Review)

This should be filled in prior to moving into ~"In Progress", but is not required upon first submitting the ticket.
**This list needs to be reviewed and completed by someone who did not work on the ticket.** Please do not pass Acceptance Criteria on a ticket you contributed code to. Ping #qa in Slack or #mythic-table to let someone know that a ticket is completed and ready for ~Review.

 - [ ] User can open menu
 - [ ] User can navigate site with links in menu
 - [ ] User can close menu modal by clicking outside menu area, returning to current page
    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Story] [Web] Sleepout

<!-- Title suggestion: [Story] [Web] Sleepout -->
<!-- Story issues track work to create new features and provide distinct new value to the user -->

## User Story

As a visitor to the site I should be able to quickly identify that Mythic Table is taking part in Sleep Out Vancouver to raise funds and awareness for the Covenant House Vancouver. I should be able to quickly access the information about this charity as well as the page to donate should I wish to.

## Details

- https://bit.ly/mtsleepout
- https://www.covenanthousebc.org/get-involved/sleepout-movement/
- https://secure3.convio.net/chb/site/SPageServer/?pagename=soch_fy22_home&_ga=2.122114635.119623761.1643607687-1322806052.1643041365
- https://secure3.convio.net/chb/site/SPageServer/?NONCE_TOKEN=CD9FC7F16DC793A95660E548DC5300BA&pagename=soch_fy22_socialguide
- https://secure3.convio.net/chb/site/SPageServer/?pagename=soch_fy22_toolkit

## Steps

- [ ] Update the site to include promotional material for Sleep Out Vancouver.

## Acceptance Criteria (To be checked off **only** during Review)

Visitors should be able to easily access information regarding the charitable event.

<!-- Some notes on Acceptance Criteria (AC)
If you are having issues creating Acceptance Criteria, please review [Some notes on Acceptance Criteria(AC)](https://gitlab.com/mythicteam/mythictable/-/wikis/qa/acceptace-criteria). Don't hesitate to ask for AC review or assistance in #qa, it's what we're here for.
-->

- [ ] Given: Samples Criteria exists in template
    - [ ] And: it has not been removed
    - [ ] When: the ticket has been submitted
    - [ ] Then: Someone else should update this
    - [ ] And: include acceptable Acceptance Criteria
    
<!-- A note on weights
0 is trivial. Does not involve code
1 is a button, documentation corrections, a quick fix
2 is a simple well known task
3 is for a somewhat simple task
5 is for a complicated story that requires a number of moving parts
8 is for a significant amount of work but should with perhaps some unknowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0