Change backend to database

[rmccreath]

Is your feature request related to a problem? Please describe.
Currently, all data is hosted on a JSON file which is stored alongside everything else on GitHub. This makes for a slimline application and has been useful for proof-of-concept and MVP. However, for the proper expansion of functionality and maintenance going forward, a change to the back-end is necessary. Currently, every change to the data requires the web app to be rebuilt and hosted anew, this isn't unusual in static web apps, however, this product needs to move toward a dynamic status rather than static.

Describe the solution you'd like

• Host web app on PHS webserver (the process has already started with PHS webmaster)
• Develop (relational) database backend with accompanying API and testing.

Describe alternatives you've considered
The use of alternatives, such as a CMS system, pre-built application, and other back-end architectures have all been considered but every solution brings different constraints. External solutions would mean completely redesigning the product, losing out on specific functionality that has been created, and would likely not integrate as well with our varying requirements. As the data structure for this product will remain the same, a relational database seems the most suitable and simple to apply.