giseldo/neodataset huggingface dataset:
[Polish] Token Accessibility

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

What is the work we're doign and why?

## Current State

Where are we now?

"This is pretty much needed, i'm colour blind and the different token colours dont help much, also, most of my players are colorblind so adding a miriad other token shapes would be pretty nice."
https://gitlab.com/mythicteam/mythictable/-/issues/179#note_418483500

Tokens are hard to differentiate for people with visual impairments. 

## How should it look/feel?

We should use form and texture to help differentiate token types from each-other, either by default, or have an option that can be enabled. 

We can either use the actual shape of the token, an overlay over top of the image, a small icon that is attached to it, or a combination of all of the above to indicate the type of token (swords, shields, hearts, etc.)

## Acceptance Criteria

- [x] Tokens can have an icon in the top right corner
- [x] Users can change icons
- [x] Changed icons are visible on other clients
- [x] Changed icons persist restarts
- [x] Changing a icon in the character list changes it for all tokens created from that character
- [x] Icons can be removed

<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 4.0
[Polish] Zooming is choppy and behaves differently on different machines

# Description

Zooming in Mythic Table has never felt good. It MUST be smooth on all operating systems.

## Current State

Scrolling is a little choppy and laggy. It must be smoother and more responsive.


<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Polish] Adjust UI scaling on different screen sizes

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

## Current State

Where are we now?
The UI on smaller displays (<1920x1080) does not look good. A lot of it is cut off and takes up a considerable amount of space

## How should it look/feel?

UI should look good all the way down to 720p (for now)

How to Fix it?
Adjust CSS rules to take screen size into account


<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
[Improvement] Mythic Analytics

# Description

Implement an analytics system with Matomo to measure how our system is being used.

## The Problem

We are blind with regards to how users are using our systems. We need to understand how they are using things.

## Background/Current State

We had been using Google Analytics, but Matomo is a more responsible choice for data privacy concerns.

## Solution

- [x] Implement Matomo in the client as a Vuex Store
- [ ] Implement Matomo in the server as a middleware
- [ ] Document clearly how the they are to be used and configured
- [ ] Build a sample Dashboard
- [ ] Document how Team members can get access to the analytics



<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 5.0
[Polish] Revisit Font Choice

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description
Investigate fonts that will work better with our layouts

## Current State

Where are we now?
The current font, while nice looking causes layout issues due to an abnormally high baseline level




<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->
tg

Story points: 2.0
[Polish] Profile Editor

# Description

The Profile Editor needs love

## Current State

![image](/uploads/97df9023c4cafc28b8d247cbbd650a4c/image.png)

## How should it look/feel?

More like this...

![image](/uploads/66fc74719d40f7620dfa273b4fc9c13c/image.png)


<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Polish] Error Dialog

# Description

Bring the Error Dialog in line with the rest of the application style.

## Current State

![image](/uploads/4c8718ce6fa2e63f786a9ca7156ce984/image.png)


<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
[Polish] Profile Image is square in Campaign List Header

# Description

If you use a square image for your profile you get something like this:

![image](/uploads/7b09d8fdd2c8f5cafb3ad662af3755fd/image.png)

## How should it look/feel?

This should be rounded


<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
[Improvement] Move all ids over to the Profile Id

# Description

Currently the backend uses a mix of ids to reference users and ownership. This is sometimes the username and in other times the profile idea.  This MUST be the same in all cases. To make things easier we will use the profile id.

## The Problem

Ownership of items is not always clear.

## Background/Current State

We had started by just using the user name as an identifier. We now need something that is a bit more robust.

## Solution

Switch to the Profile Id. Cache the database look up.

## Additional Information

## Steps

- [ ] TBD



<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Polish] Shortened Campaign Invite IDs

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

It would be good to have Campaign Invitation IDs be significantly shorter, to allow for users to manually enter in the invitation. 

## Current State

We have a 24 digit alphanumeric game ID. This would be very difficult, if not impossible for someone to be able to manually enter. 

## How should it look/feel?

Somewhere in the region of a 6-10 digit ID, to easily allow for manual entry. If we are going alphanumeric, removal of characters that look the same (l, 1, I), and vowels (as well as 0) to make it impossible to accidentally generate offensive words. 



<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
Obscure rolls

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Rolling dice in chat wont make obvious if the player rolled the correct dice roll, you have to click the message to get detailed info.

## Current State

Dice rolls display only the resulting number.

![image](/uploads/9843bfe4c4a4534a7cbe44176e44a6bb/image.png)

## How should it look/feel?

Dice shoulds should display the command used on the roll.

![image](/uploads/3918a574facc3b1909e72e6d06305c82/image.png)

<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
Map can be lost in boardview

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Between zooms with scrollwheels and pannings you can easily loose focus of the map, requiring either a scene change or 

## Current State

Map pans and zooms indefinitely.

## How should it look/feel?

Add a center map button, limit the map panning to somewhere near its border or add a double middle mouse button click to fit everything in view like most CAD sofwares do.


<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
Log Out button inside board view

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Inside the board view, in the play UI, is a unecessary logout button right next to the annotation button, it's probably going to cause more frustration than give utility.

## Current State

Pressing the button instantly logs out, without asking for confirmation.

## How should it look/feel?

Remove it or ask for confirmation.


<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
Mythic Table logo implies clickable functionality

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

The Mythic Table logo in the campaign banners screen implies that clicking on it does something.

## Current State

Clicking on the logo does nothing.

## How should it look/feel?

Either make it do soemthing or remove the clickable cursor on hover.

<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
Campaign banners are too large

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Campaign banners occupy too much space inside the window without giving value to the space used.

## Current State

The campaign banners are so big that only two of them fit on a 1920x1080 display.
![image](/uploads/f1f332a2cb78620a3f9e1a3290668f5b/image.png)

## How should it look/feel?

Make the campaign banner have a lower maximum size and resize as the window containing it is resized.
Fit more campaigns inside a window.
Use the banner state to display more information.

50% zoom seems like a good size.
![image](/uploads/db0a5a03aa8295a0505ce6f618701b3e/image.png)

<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
No confirmation on campaign delete

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Pressing the Trashbin red icon under 'info' in a campaign banner instantly deletes the entire campaign without confirmation.

## Current State

Pressing the delete campaign button asks for no confirmation on campaign deletion.

## How should it look/feel?

It should ask for confirmation taking care to emphasize the "no" button for safety.


<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
Player invites are not intuitive

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

The current way of inviting players isn't obvious and prone to frustrating mistakes.

## Current State

You have to click 'info' inside the campaign banner, then copy the link inside the info and then send it to the player.
The link, however, is blue and underscored, it implies that it needs to be clicked on to work, instead it redirects you to the player connection window.

## How should it look/feel?

The link text shoouldn't be clickable, instead a copy link button should be used.

![image](/uploads/bb2d38ca1320f80c79a0ca026d4e8007/image.png)

<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
Clicking on the campaign banner does nothing

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

Clicking on the campaign banner does nothing even tough there are multiple indications that it does: hovering the banner expands it and clicking on the big plus button for creating a campaign acts just as expected.

## Current State

The info button does the functionality suggested by the hovering.

## How should it look/feel?

Remove the info button, replace that with clicking the banner.


<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 1.0
[Polish] Redirect Mobile Users to a Coming Soon page

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

What is the work we're doign and why?

## Current State
When someone logs into mythic on a phone, they are presented with a very broken view. 

## How should it look/feel?

We should redirect them to a "Mobile support coming soon" page, with additional details, redirecting them to use Mythic on a desktop device

Design Mockup TBD


<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Bug] Create Campaign hangs when large images are uploaded.

# Summary

On https://edge.mythictable.com/, when you attempt to create a campaign and use a image that's too image for the nginx 
(see issue #196) the uploading progress does not stop and you can't cancel or try a different image.

## Steps to reproduce

1. Login at edge
1. Create new Campaign
1. Choose a VERY large image

## What is the current *bug* behavior?

Uploading progress never stops. 

## What is the expected *correct* behavior?

We should see an error message stating the file was too large.

## Relevant logs and/or screenshots

See #196 

## Possible fixes

Even fixing #196 will not fix this issue.  

- [ ] The upload needs to be cancelable
- [ ] The error much be displayed
- [ ] And afterwards, a new image must be able to be selected

## Cause (Fill out after fix)
<!-- This must be filled out before the Bug can be closed.  
This is used in our post mordems to understand where we can make improvements. -->

Chose one or more:
- [ ] Work was rushed
- [ ] Plan Incomplete
- [ ] Insufficient Tests
- [ ] Missed in Review

Story points: 1.0
[Bug] Nginx File size upload issue

# Summary

Uploading a character or map on https://edge.mythictable.com/ sometimes causes an error and the file is not uploaded.

## Steps to reproduce

1. Login https://edge.mythictable.com/ 
1. Enter campaign
1. Hit the add button in characters.
1. Choose a large file

## What is the current *bug* behavior?

Nothing seems to happen. 

## What is the expected *correct* behavior?

We should be able to access much larger files. And if we do reach this limit we should notify the user.

## Relevant logs and/or screenshots

```
CampaignEdit.vue:190
POST https://edge.mythictable.com/api/files?path=campaign 413

CampaignEdit.vue:220 Error: Request failed with status code 413
    at t.exports (chunk-vendors.904544a6.js:17)
    at t.exports (chunk-vendors.904544a6.js:62)
```

## Possible fixes

Try setting the `client_max_body_size`

- http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size

## Cause (Fill out after fix)
<!-- This must be filled out before the Bug can be closed.  
This is used in our post mordems to understand where we can make improvements. -->

Chose one or more:
- [ ] Work was rushed
- [ ] Plan Incomplete
- [ ] Insufficient Tests
- [ ] Missed in Review

Story points: 1.0
[Polish] Adjust Balance of Character Editor

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

## Current State

The Character Editor is very left-panel heavy. We need to adjust the balance of controls and inputs so that it is balanced. 


## How should it look/feel?
It should have most of the controls in the much larger right panel, with basic adjustments available on the left. 

How to Fix it?
Move the colour and frame style options over to the right panel, placed below the Description field. 
Using the grid style buttons from the Scene Editor, show previews of different frames



<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0
[Polish] Adjust text centering

<!-- Title suggestion: [Polish] Name of improvement -->
<!-- Polish tasks track work to improve the look, feel and usability of existing features -->

# Description

After the new font went in, a lot of the vertical centering has been adjusted, items are no longer properly centered. This is most noticeable in the headers of the widget. 

## Current State

![image](/uploads/a5bbff5a006b22e98acb73ac13957051/image.png)



<!-- A note on weights
0 is trivial. Does not involve and 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 requies a number of moving parts
8 is for a signifcant amount of work but should with perhaps some unkowns or external dependencies
Anything higher than 8 should be broken up into smaller more distinct stories.
-->

Story points: 2.0