Users should be able to save a post in process and continue writing it later.
The quickest way to get this to work would be to leverage localStorage (or a similar mechanism) to save the post, then ask whether the saved post should be reloaded if one is detected. The limitation would ofc be that you wouldn't be able to transfer the post to another device, but it could still be a good way of quickly prototyping the functionality/UI without having to add a whole backend layer to it.
To think about: what happens if you save a post that's replying to another contrib? Should we allow to reload the text in a different context?
Users should be able to save a post in process and continue writing it later.
The quickest way to get this to work would be to leverage
localStorage(or a similar mechanism) to save the post, then ask whether the saved post should be reloaded if one is detected. The limitation would ofc be that you wouldn't be able to transfer the post to another device, but it could still be a good way of quickly prototyping the functionality/UI without having to add a whole backend layer to it.To think about: what happens if you save a post that's replying to another contrib? Should we allow to reload the text in a different context?