One of the troubles with essays and retention is that you don't remember what you've read. One of the problems is that the questions you create are best coming from yourself. The barrier seems to high to allow users to create their own questions. Set questions and set answers seems like a good first step.
Technical Requirements
User perspective
React will be able to handle interactivity
User activated questions on scrolling
Question up on screen as user scrolls down the page
Buttons for easy, medium, hard or don't remember so to click it triggers the answer to appear on the screen.
Consider the algorithm used for spaced repetition to incorporate (Anki uses SM-2)
Somewhere on the question (top right-hand corner) to outlay how many questions in total in the deck
End screen when finished deck
Button to review again
At the end of the essay, be able to export questions/answers to space repetition program of choice ?
Be able to toggle that functionality to force reader to remember (ie after a first read ?)
Data Persistence
Will need a way to store questions and answers on the page. If it was, maybe a couple of sections could perhaps get away with hard coding answers and questions. If we get to more than 10-15 questions on a page, I think a database table of question and answer might be more appropriate.
For now, seems like hard coding may be the way forward unless we come up again pain points.
One of the troubles with essays and retention is that you don't remember what you've read. One of the problems is that the questions you create are best coming from yourself. The barrier seems to high to allow users to create their own questions. Set questions and set answers seems like a good first step.
Technical Requirements
User perspective React will be able to handle interactivity
Data Persistence Will need a way to store questions and answers on the page. If it was, maybe a couple of sections could perhaps get away with hard coding answers and questions. If we get to more than 10-15 questions on a page, I think a database table of question and answer might be more appropriate.
For now, seems like hard coding may be the way forward unless we come up again pain points.