You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On every save, the entire resume needs to be sent to the database, rather than just the new change. This is less efficient. To this end, the changes could only be sent to the database occasionally, rather than on each change. If the updates are frequent enough the user cannot lose much data. Plus a warning should then be sent if the user tries to leave the site and there are still unsaved changes. Finally, there should then be a button that allows you to save manually with a little confirmation text so you're sure your work is saved.
The text was updated successfully, but these errors were encountered:
CeesJol
changed the title
Restructure resumes from DB to JSON
Save resume data less frequently
Dec 12, 2020
On every save, the entire resume needs to be sent to the database, rather than just the new change. This is less efficient. To this end, the changes could only be sent to the database occasionally, rather than on each change. If the updates are frequent enough the user cannot lose much data. Plus a warning should then be sent if the user tries to leave the site and there are still unsaved changes. Finally, there should then be a button that allows you to save manually with a little confirmation text so you're sure your work is saved.
The text was updated successfully, but these errors were encountered: