codeforpdx / supportsystem Goto Github PK

Create the form that a Provider fills out in order to log in to the site

Acceptance Criteria:

• Upon clicking "log in", the provider is able to enter their username/email (TODO: clarify which, it should only require one or the other) and password into two corresponding, labeled text fields
• Submit button correctly sends data to the back end to ensure auth
• [Possibly a stretch goal/optional] Upon successful auth check, the provider is redirected to the correct "logged-in" home page

Via "Provider View" profile page. Deletion flow, get user confirmation before deletion of profile, remove from database

Grid/list view of all verified providers

• Profile picture to render
• - about me section

Is your feature request related to a problem? Please describe.
Add the Database diagram to the repo

Describe the solution you'd like
download and export the database diagram created on 7/12
create a folder called database_info add the files to it
reference the folder in the Readme under the heading Database Design Schematics. (or whatever you would like)

Is your feature request related to a problem? Please describe.
Connect the wireframes to the project

Describe the solution you'd like
Export the current wireframes and/or create a link to the wireframes.
Put the link in the ReadMe file under the headings Wireframe.

Every word that provider writes in profile can be indexed -- matching keywords.

• Autocomplete functionality to help with spelling mistakesAdditional context

Add any other context or screenshots about the feature request here.

Create Fake Provider Accounts to test rendering + endpoints
This will be created in a google sheets file and then transferred into actual database via script

• at least 10 providers
• test cases with min and max selections for each category

Landing Page implementing "components" made

• Mission Statement
• Search Bar + Filter Fx
• Login/Signup
• Provider Button?

When patient clicks on provider profile this is what they see.
--- Acceptance Criteria ---

• Profile picture
• Pronouns
• About
• Practice Type
• Address
• Accessibility
• Certifications (if applicable)
• Accepting new clients ribbon
• Provider About Section
• Website Button
• Call Me Button
• Email Me Button
• Provider Identity Section (see data schema for more details)
• Community experience (see data schema for more details)

This is the form that will pop up should the provider choose to finish filling out their profile details immediately after signing up for an account. There will be a 'skip' button that will take the user to their incomplete profile should they want to postpone filling out profile details for another time.

Create registration form that will add a provider to the database and gives prompts to fill out.

Acceptance Criteria:

• Registration form has text inputs for each required field (see schema for required fields)
• Submission button exists and pressing it sends data correctly to the database
• Progress bar at the bottom of the page correctly shows user's progress through the sign-up process

Upon clicking the 'edit' button(s) there will be a pop up of a form w the fields that are already completed filled in and blanks for the fields not filled in so that the provider can edit their profile details.

This is the view that the ONLY the provider can see when looking at their unpublished/published profile. It will look the same as the view a potential patient can see with the following caveats:

• There is an option to 'edit' their profile which will take them to a form to edit details that are on their profile.
• Status bar to see how much of profile is completed before going public.

User/provider functionality to log out

Acceptance Criteria:

• Upon log-out, user is redirected to front/splash page, which shows the option to log in
• Upon log-out, user is unable to access pages/functionality that is forbidden to logged-out users
• Upon log-out, if a user tries to access (either by clicking a "back" button or other UI component) pages/functionality that is forbidden to logged-out users, they are redirected to the log-in/sign-up page/modal