Implement a Quest page where the user can see the list of available quests
[x] Set up a route
[x] Consider master/detail setup, something along the lines of
/quest/
pulls up the list of quests, possibly in card form
/quest/:questId
shows the details for that quest
[x] Where it is feasible/sensible, re-use Kames's components or the functions they use to e.g. read the JSON
Implement a Quest page where the user can see the list of available quests
[x] Set up a route
[x] Consider master/detail setup, something along the lines of /quest/ pulls up the list of quests, possibly in card form /quest/:questId shows the details for that quest
[x] Where it is feasible/sensible, re-use Kames's components or the functions they use to e.g. read the JSON