Currently does not work well for re-sized windows, and I haven't even tested it on other devices. Particularly, fix:

1. Transparent black background does not resize correctly
2. Response positions itself fine on desktop, but probably not so much on mobile. Make the term sections overflow correctly and map the response so that it is above the appropriate section.

Everything is just in one large file right now - you can split this up to make it easier to maintain.

You missed a category! all the affinities are currently listed under "body parts".

The terms are currently hard-coded as HTML on the front page under the search bar - instead, we want these sections to populate using the JSON data. This ensures that any future changes to the message library (like for the upcoming DLC) only need to be changed in one place, terms.json. It also reduces the percentage of our codebase that is HTML; github is currently listing this project to be mostly HTML because of these massive divs, when really this is predominantly a javascript project.

Personalize these and make them more specific to your webpage.

Page is responsive in the browser but looks bad on mobile devices - change the layout to work on smaller screens.

Not technically a bug since we never wrote the code for this feature, but the search bar should work like any other search bar on the internet. Just add functions to navigate and highlight the search results with the arrow keys, and fix the function for the Enter key so that it uses the currently highlighted result instead of the first one.

Code is messy - fix yo shit foo!

Two known examples:

1. Lord is listed under Enemies and People
2. Skill is listed under Actions and Things

In the search bar, clicking on one or the other should return their corresponding key - instead, it only returns the first matching key (Lord always returns Enemies, Skill always returns Actions).

While the current implementation works, it's not technically correct. Please fix this!

The search icon currently selects the first options on the autocomplete drop-down rather than searching for the text in the input box. The enter button does the same thing.

Just make it use what is in the input box, and if nothing matches, say so in the answer box.

When the user selects a term, it should highlight the appropriate category. The border color should change, the particular term should highlight, and the entire term section should pulse yellow (start out high, fade away over 0.5-1 second).

Names are ambiguous or unclear - just rename variable and functions to make your code more readable.