User Story: as a user, I want to know what to do when I end up on the search page for the first time. I have no idea what my FundBoard is for, or even that it exists, I would like that explained to me.
User Story: as a user, I want any explanation component to be something I can close and not see again unless I take action to see it.
Functional Requirements
As part of this issue we'll create an AppState table in Back4App, to be used in the future for any elements of the applications state we want to save and restore each time the user logs in.
[ ] Design the UX for this component.
[ ] Add a component to Search.js that will unfold at the top of the screen.
[ ] It should have a close button that will save the name of the component to the Seen list in Back4App.
[ ] When the close button is clicked, an event should trigger that will cause a saga to add this component to the Closed list in the AppState table.
[ ] Add a saga to retrieve and save the AppState, which will include a Closed list, a list of which instructional components a user has closed.
[ ] The saga should to retrieve the AppState should be triggered on a retrieve action, and also on a log in action (we could just have login fire a retrieve action, but I think it's cleaner for the saga to watch for both separately).
ie: there should be a watcher for APPSTATE_REQUESTED and a watcher for USER_LOGIN_SUCCEEDED, both of which trigger the workAppStateGet function.
[ ] Add a redux reducer file and the required actions for tracking the retrieval of and writing to the AppState.
[ ] Add a table (class) to Back4App named AppState, each row will be tied to a user and will be used to track various app state parameters.
[ ] Add a cloud function for retrieving and saving the user's own AppState.
[ ] Add code to App.js to retrieve the AppState data if the user is logged in when the app loads.
User Story: as a user, I want to know what to do when I end up on the search page for the first time. I have no idea what my FundBoard is for, or even that it exists, I would like that explained to me.
User Story: as a user, I want any explanation component to be something I can close and not see again unless I take action to see it.
Functional Requirements
As part of this issue we'll create an AppState table in Back4App, to be used in the future for any elements of the applications state we want to save and restore each time the user logs in.