Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Communicating unsaved changes on FAQ page #1896

Open
namigoeku opened this issue Oct 10, 2024 · 0 comments
Open

Communicating unsaved changes on FAQ page #1896

namigoeku opened this issue Oct 10, 2024 · 0 comments
Labels
level: medium p-feature: FAQ screen /faq pbv: dev All engineering issues priority: SHOULD HAVE ready for prioritization Issues that are ready to be prioritized by product role: front-end Front End Developer size: 1pt Can be done in 4-6 hours
Milestone

Comments

@namigoeku
Copy link
Member

namigoeku commented Oct 10, 2024

Overview

FAQ Page: When attempting to navigate away from the page, there should be a warning indicating unsaved changes.

Action Items

  • This can be accomplished by using the modal previously created by devs on the projects page. The modal's verbiage should say something like "Unsaved Changes: Are you sure you want to leave the page?", along with "Save"/"Stay" and "Discard Changes" CTA buttons.
  • Would devs prefer "Save" or "Stay"? "Save" should automatically save the progress, whereas "Stay" indicates the user will remain on the page to continue their progress.

Image

FAQ Page
image

Example solution
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level: medium p-feature: FAQ screen /faq pbv: dev All engineering issues priority: SHOULD HAVE ready for prioritization Issues that are ready to be prioritized by product role: front-end Front End Developer size: 1pt Can be done in 4-6 hours
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

2 participants