CodeForPhilly / CodeForPhilly/benefit-decision-toolkit

Automatically save/autosave the user's work in the form editor after every change

Open
#418 0 comments 1 reaction 1 assignee Claimed by @earth-walker View on GitHub
big lift
Dominant language
Java
Stars
15
Forks
5
Avg merge
1d 2h
Merged PRs (30d)
23

Description

I think that automatically saving the user's work in the form editor after every change they make would be a better workflow than clicking the save button to save their work.

I notice that in practice, most users click the save button after every change they make.

Not autosaving also allows for the possibility of accidentally losing work by closing the project before saving.

If we implement autosaving, we should also implement a versioning system where you can "save as" to create a version of the project and then continue working, then switch to the other version as needed. This will require some UX and technical thinking to develop.

@prestoncabe mentioned that this might require grouping the entire screener project into one object, which sounds like a good idea to me.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.