The link can literally encode the answer in the URL, which you can just hide the raw url it in the emails’s HTML. (Fox examples, put it as base64 chars in query parameters)
Then you can host a (static) webpage that renders the text. This lets you host any users text w/o an interactive site. No live database, no ops burden, etc.
If you wanted to get fancy (which users of such a product probably would probably want) throw in “success/failure” links so your users can report the results and get changed frequency of spaced repetitions based on their success rate.
The link can literally encode the answer in the URL, which you can just hide the raw url it in the emails’s HTML. (Fox examples, put it as base64 chars in query parameters)
Then you can host a (static) webpage that renders the text. This lets you host any users text w/o an interactive site. No live database, no ops burden, etc.
If you wanted to get fancy (which users of such a product probably would probably want) throw in “success/failure” links so your users can report the results and get changed frequency of spaced repetitions based on their success rate.