BLUEBUTTON-934 New User Self-Identification

[johnfrenchxyz]

Note: Styles for this PR are dependent on pulling down this progress from the CSS repo:

CMSgov/bluebutton-css#27

There is some more cleanup and tweaks I probably want to do on my side, but I wanted to open this up for collaboration if that would be most productive. Not sure exactly how we want to proceed, but we can talk about it here.

[johnfrenchxyz]

Here's one thing I might need help with:

I want to change the way we are handling contextual messages. You'll see in the PR that I commented out the div at the top where we used to include messages.html. I think what I might want to do is just put that if messages around the gradient-messages-container and put the message text inside like those sample messages on the login page.

Is that a good course of action there?

[johnfrenchxyz]

Another thing I need help with:

On the signup form:

• Can we move Frist name and Last Name to be first in the form?
• Can we remove the messages under the inputs?
• Can we add the select box to the actual generated form and create tag for the users?

[dtisza1]

I just moved the email to be the third field on the signup form, and removed the help texts.

[dtisza1]

Here's one thing I might need help with:

I want to change the way we are handling contextual messages. You'll see in the PR that I commented out the div at the top where we used to include messages.html. I think what I might want to do is just put that if messages around the gradient-messages-container and put the message text inside like those sample messages on the login page.

Is that a good course of action there?

I like the way those look on the login page! That idea sounds good to me. And possibly move that in to the "include/messages.html" template when ready for all of them to be presented that way.

Here is a list of templates including that:
./apps/accounts/templates/account-settings.html
./apps/accounts/templates/registration/password_forgot_reset_confirm_form.html
./apps/accounts/templates/registration/password_forgot_form.html
./apps/accounts/templates/registration/password_forgot_reset_complete.html
./apps/accounts/templates/registration/passwd_change_form.html
./apps/accounts/templates/registration/password_forgot_reset_done.html
./apps/home/templates/authenticated-home.html
./apps/dot_ext/templates/endorsements/base.html
./apps/dot_ext/templates/oauth2_provider/base.html
./templates/generic/bootstrapform.html
./templates/generic/split60_50.html

[dtisza1]

The generic/bootstrapform.html template was being used by both signup and mfa views. I removed that template and split it in to two new templates under apps/accounts/templates/registration called signup.html and mfa.html.

[whytheplatypus]

can this be done directly. Possibly with a ModelChoiceField or a MultipleModelChoiceField with a different widget?

[dtisza1]

TY! This is nicer. I changed it to use ModelChoiceField .