prettier-mvp-onboarding-flow-notes.md

• style confirm-account-page to look like screen 2

• style group-setup-page to look like screen 3

• add email field to confirm-account-page

• confirm-account-page expects email in url params so it can autopopulate email field

• add optional name field to confirm-account-page, below password field

• in invite-new-admin-to-create-group flow, user lands on confirm-account-page with 'lets go' button that brings them to group-page

• in mvp-admin-onboarding flow, no confirmation_token needed for screen 2

• in mvp-admin-onboarding flow, no emails sent to new admin (maybe in the future though)

• for this ticket, omitting the demo link and everything below it on the landing page

• omitting the 'already have an account? sign in here' btn from screen 2

• for this ticket, commenting out 'you can change stuff later' text on screen 3

• for this ticket, omit menu button in screens 1-3

• when this ticket is done, need to have discussion about whether to include the landing page in production now, or when we release public beta.

• whenever we do deploy the landing page to production, need to have conversation about removing the invite-new-admin-to-create-group flow from the app

• eventually derek wants to use google analytics to redirect to different versions of the landing page, to collect stats on which one works best.

• two flows for group creation

  • flow 1: new cobudget admin sets up group via invite-new-admin-to-create-group flow or mvp-admin-onboarding flow
  • flow 2: existing cobudget admin/user creates group from within the app

• we'll have two group setup pages -- one for each flow

• if existing user tries to create group via mvp-admin-onboarding flow

  • redirected to login-page
  • after successful login, redirected to flow 2 group page

• logged in user should never see the front page

• when user logs out, redirected to landing page

• separating help cards and example project into a separate ticket