Project

General

Profile

Actions

Design/UX #20575

open

Registration and Login Redesign

Added by Colin McDonald 4 months ago. Updated 28 days ago.

Status:
New
Priority name:
Normal
Assignee:
Category name:
Registration
Target version:
Start date:
2024-06-11
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Deployment actions:

Description

I followed up with Sara after our Tuesday call about organizing the different items/screens she's been working on to improve the look and functionality of our registration and login flows.

I'm creating this parent ticket for the overall project, which we can use for general updates or things that come up without a clear home in the child tickets I'll create next.

I'll just add Sara and the dev team as watchers on the child tickets, but feel free to check back on this ticket if you want to see the other tickets and what's going on with them.


Subtasks 8 (8 open0 closed)

Design/UX #20465: Log In PageNewColin McDonald2024-06-11

Actions
Design/UX #20576: Signup pageNewSara Cannon2024-07-12

Actions
Design/UX #20577: Registration confirmation pageNewSara Cannon2024-07-12

Actions
Design/UX #20578: Registration confirmation emailNewSara Cannon2024-07-12

Actions
Design/UX #20579: Account activation page NewSara Cannon2024-07-12

Actions
Design/UX #20580: Account activation email(s)Testing RequiredSara Cannon2024-07-12

Actions
Design/UX #20581: Account activation confirmation pageNewSara Cannon2024-07-12

Actions
Design/UX #20582: Post-activation prompts Testing RequiredRaymond Hoh2024-07-12

Actions
Actions #1

Updated by Colin McDonald 4 months ago

By the way, my rough idea is that the child tickets will follow the same sequence that a new user will navigate to sign up, activate, login, etc, with a ticket corresponding to each step in the flow.

Actions #2

Updated by Colin McDonald 4 months ago

  • Tracker changed from Feature to Design/UX
Actions #3

Updated by Boone Gorges 28 days ago

This flow is ready for a test on cdev.

Sara, there were some ambiguities between the comps for the various landing pages. For consistency, I kept the same element width for the central content as what we do on the registration page. And I lined up the text in the "squiggle" header with the text in the main content area. If you feel like this ought to work differently - for example, to utilize more horizontal space and reduce line breaks in the headers - let's try to think about it holistically.

Actions

Also available in: Atom PDF