[FEATURE] - Create controller to fetch chapter data

[sabelo-n]

No description provided.

[michaeldera]

So what did we eventually decide on the model of the data. We go with name, id and content?

[sabelo-n]

I am thinking hostname/api/chapter/{chapterNumber}. Then have a map of chapter --> path that returns the path and read the file from disk. This can later on be enhanced to read from anywhere (eg network file system/ object store/ aws s3 etcetera etcetera). Pure HTML would be best then you can style it on the frontend based on the device screen size/ type. Angazi though :p

[michaeldera]

So when someone hits the endpoint we just return HTML, or some JSON so that we can pass stuff like the title as well?

[michaeldera]

So I added a boilerplate for the controller with a model I propose we use here #4 . I chose that because it fits in well with a schema.org model. I was thinking of using EFCore to model the database using a code-first approach. What do you think?