Before You Begin Warning Content

hackforla / expunge-assist

Expunge Assist is a free digital tool specifically designed to aid Californians with arrest and conviction histories in clearing their criminal records.

https://expungeassist.org

39 stars 17 forks source link

Before You Begin Warning Content #1140

Open sydneywalcoff opened 7 months ago

sydneywalcoff commented 7 months ago

Dependency

[ ] #1287

Overview

If you use browser navigation like (refresh, forward and backward) while in the letter generator, the app forgets all your previous answers. And because it uses your previous answers to determine the flow and eventually to form the letter, the app breaks and shows a blank white page.

We should a) warn users not to use browser navigation like (refresh, forward and backward) while in the letter generator before they start b) if a user does refresh, we should show a little Oops reminder (similar to the https://github.com/hackforla/expunge-assist/issues/1136, but smaller) reminding the user to use browser navigation

Action Items

[ ] update content on Before you begin
[ ] notify design of content change
[ ] add Before you begin content to #1143 and
- [ ] remove dependency label
- [ ] add 'ready for dev lead' label

Resources/Notes

sydneywalcoff commented 7 months ago

@SamHyler @emmathrash if you think design should be included, feel free to rope them in, but I think this might be okay to just update the content and let them know of the change.

cc @anitadesigns @jyehllow let me know your thoughts as well

github-actions[bot] commented 5 months ago

Hey @SamHyler, @emmathrash! Thanks again for taking this issue.

Time for an update! Please comment the following update:
**Progress:** What's the status of the project? What have you done and what still needs to be done?
**Estimated Time to Completion (ETC):** When do you estimate to be finished?
**Blockers:** Anything preventing you from finishing?

Thanks again!

SamHyler commented 5 months ago

Ok @sydneywalcoff @emmathrash @CBx3000 I'm seeing a series of user warning messages needed. That's great! I suggest Content has a discussion about how to approach warning messages in general, and then do each of these issues, as they are related. So decisions about which pages/other space and why any messaging should appear and how the warning messages relate to each other is needed.

I'm pushing all these issues over into the backlog. Might be good to have a parent/epic/newname issue to nestle all warning/error prevention messaging so that we can talk strategy in the parent/epic/newname issue and then assign out all the other issues?