Overhaul: Ditch json dump in favor of GraphQL and abstract to support multiple shows #33
Description
This is a huge effort, but after falling in love with the show Letterkenny, I also want to support more shows here.
It's already pretty generic in data, just not in the backend. So, this would be a large scale project, but not a total rewrite.
Backend
This is where I really want things to change. Right now it's a single json file that's actually downloaded to the front end and then filtered. That's nasty as fuck, and I don't like it. It's way too excessive for most users, I suspect.
I'd like to improve this by serving content behind a GraphQL interface. Long term, I'd like this to be behind an AWS Lambda function querying DynamoDB tables and returning results to answer GraphQL queries. Short term, I'd port that json file to a lambda function which responds to GraphQL queries.
This allows us to be generic in data handling, so we can use a consistent schema for queries across any devices (web, mobile apps, tvos, etc) while downloading less data in total.
Web Frontend
This website's pretty ugly these days. I liked it then, but it hasn't aged well, users have had some complaints over the years. I don't know what I'd really change it to, other than I would use GraphQL to query for data instead of json and use CSS grid for layout.
Other Frontends
With the use of GraphQL (do you see what I'm getting at yet? This is a big deal), we could very easily port this frontend to other applications, such as mobile via react native, apple tv, command line... Lots of potential here.