FLOW & DESIGN: Registration flow

[catrobson]

Capture the ideal registration flow as a page flow we would like with the goal of each page noted. Then capture wireframes for any pages that we expect are new or changing.

Known requirements:

• Users must still sign in using the RHD website and register for an RHD account
• Users must still agree to the T&Cs
• Users must set up github with their account for OSIO
• We need to add users to a waitlist on OSO East
• We need to notify users of their status
• Ideally we should design something that scales to being able to choose free or paid tiers of OSIO that have different OSO provisioning behind them.
• We need to provision OSO space for users and then let them into OSIO upon provisioning

[catrobson]

There is a document where registration flow improvements are already starting to be captured here: https://docs.google.com/document/d/1iyTsTl2d8ffD9cGpvPBowusiPt5yulqqjdoiVKQkshI/edit?ts=59aedcd8

[catrobson]

Updated with flows given OpenShift and OSIO management discussions: https://redhat.invisionapp.com/share/C9DGY7QPQ

Reviewing on Tuesday with management team.

[catrobson]

Carry forward to next sprint.

[catrobson]

Captured latest agreed upon designs for Beta and GA here: https://redhat.invisionapp.com/share/C9DGY7QPQ#/258642248_Flow_Screen_-_OSIO_Beta_And_GA_Ideal_Flow Will open stories for specific page design work separately from this issue.