Bugfixes for 1.0 and immediate updates

Content

[1] Added new event: workshop student panel
[2] Fixed typo on homepage: "invovled"
[3] Changed colors of slide button

Technical

[3] Hacky inline style solution implemented so will want to look at the coloring system for buttons - which is the overriding style issue.

Start of change tracking

Start of tracking changes

Starting to add releases to track updates and have a better understanding of release notes.

The codebase went over a significant refactoring to make the site more maintainable for the future. Since then, there's been a host of small changes so the tracking of patch changes will start now at the current state. These notes will be divided into three main sections: the first being content related updates - i.e. config changes, description updates, etc. This section will not have any technical depth and is meant for those who are not involved with the website to easily digest and understand the changes that were made. The second will be technical updates - these will be likely describe some content changes that had some level of technical depth and provide reasoning for the changes and lastly, architectural updates - these will be large scale changes that require significant amounts of code refactoring, usually to facilitate smoother content updates in the future.

Update structure/format

The updates are prefixed by a number in no particular order but they are used to help match which updates are which at every level. (Content update [2] will be the same or a related issue to Architectural update [2] - the difference is talking about it on a different level)You can find examples of what to expect below:

Content Updates

[1] Updated several board member's descriptions
[2] Updated some PT and other redirect links: see architectural updates below
[3] Can see event descriptions for past events now
[4] Updated new event: Game night 4/13

Technical Updates

[2] Added a link to PT signup on PT page with deadline
[3] Opted to show event descriptions for past events because potential new members might not know what the workshops at our club entails. This way, they can see what past events were about and really understand what the club does.

Architectural Updates

[2] Removed redirect system of making fetch call to "data" github repo and instead replaced it with inline redirects in the App component. Not sure if we want to switch to a config system later on - it really depends on how complex the redirection ends up being - but for now, the current system is fine.