Right now a lot of out components were just thrown together quickly to get a working MVP. Because of this, we need to fix bugs/clean up the code so that things like colors are not hard coded
Acceptance Criteria
[ ] All colors used on our website should be using extendTheme from ChakraUI. Primary, secondary, accent, text, and background are specified.
Because a component may use different colors (Ex: the background for the key colors may be the accent color for one theme but the background color but slightly lighter for a different theme), specify the colors for Buttons, Keys, Input Caret.Cursor, and NavBar
Not sure if InputPhrase is needed case it will be the text color
[ ] Keyboard is fixed
Right now, when the screen size too big/wide, the input phrase clips with the Keyboard. Implement a fix so that this doesn't happen
Two possible solutions
Set hard width like wordle
Don't make the keyboard as big on wider screens (lessen the scaling)
[ ] Fix the layout of the website when the hint pops up
The space between the jumbled phrase and the hint looks unnatural
The text is also pretty small, don't make it too large though
[ ] Finalize design docs for all components
[ ] Allow input phrase to display punctuation
We don't allow users to type punctuation so the blank phrase (underscores) should show punctuation
The Carot(cursor) only skips spaces right now so it should also skip punctuation automatically
[ ] Web analytics: I don't know what this is so Danny write this
Example of the keyboard bug, the I had to make the window very small for this example because the phrase was pretty short. But for long phrases, this problem is more likely to occur
Example of what the blank phrase should look like with punctuation
Subtasks
None unless we want to split everything as their own subtask
Description
Right now a lot of out components were just thrown together quickly to get a working MVP. Because of this, we need to fix bugs/clean up the code so that things like colors are not hard coded
Acceptance Criteria
Dev Notes
Subtasks