settings

[elimelt]

start brainstorming any preferences that you want to have associated with a user.

we will be storing settings as key-value pairs; each key will be a "type" that identifies the setting, and each value will be a piece of data that describes the user's preference for that setting.

[karhu1]

So far we have a basic layout made for the settings page:

Next steps:

• Create a modular setting component that can take in a message and a type of menu (switch, drop down, input, etc.) that will determine its value. Each setting should fit a key and value format to be able to be stored in the database.
• Redesign to be able to work when we add more and more setting tabs.
• Create animations to make interactivity better. (Research react-transition-group library)

The react-transition-group seems to be exactly what we want to achieve with our routing transition effects, so starting research on it early will definitely be beneficial!

[karhu1]

Progress Update:

• Finished modular styling for setting components.
• Learned and implemented smaller components for easy insertion of bootstrap elements into a setting component such as a switch, dropdown, and range.
• Started work on a mapper function that will create the individual setting components inside of SettingsMenu based off of a JS object with instructions.

Still needs to be done:

• Connecting the settings into some working piece of state that updates the visuals and functionality of the page.
• Finish the mapper.
• Make a clean looking scroll feature for the settings menu.