User:Bwinton/Account Provisioner Todos

• (Done!) Polish the Check Account screen some more.
  • (Done!) Adding keyboard navigation, i.e. enter to go to the next step.
  • (Done!) Making sure the buttons are always in the correct (visual) state.
  • (Done!) Handle multiple domains in the checked addresses.
• (Done!) Polish the integrated Account Wizard.
  • (Done!) Add the "Back to Provisioner" link.
  • (Done!) Make sure everything in it still works.
• Style the Submit Info screen.
  • (Partially done…) Basically we need to add styles to it.
  • We might also want to split it up into >1 screen.
  • We might also also want to break the code out into a different page.
    • Maybe use an iframe or something.
• Handle successful and unsuccessful cases for Submit Info.
  • (Done!) Create a mock web service for this.
  • Success:
    • (Done!) Get a config from somewhere,
    • (Done!!!!) and feed it to the Account Wizard.
    • Handle any errors that might result from that. (Bad password?)
  • Failure:
    • (Done!) Display errors, and let the user re-submit.
• Handle Transitions between Provisioner and Wizard.
  • (Done!) Keep track of where we are in the Provisioner.
  • I think we'll need to re-start the Wizard every time.

Stuff we need an API for:

• The Submit Info screen.
  • We can do a bunch of work on styling the mockup.
  • But it might not be useful, depending on the API.
    • Maybe they have an HTML page which we'll need to put in an iframe.
  • The integration with the actual API goes in this bucket, too.
  • More polish/interaction design once we know what info they need.
• We might also need to re-work the other screens.
  • i.e. if they can't tell us what similar usernames are available.
  • Or if they offer "me@<personalized domain>.com".
• Other stuff.
  • Yeah, I really don't know exactly what the API will require.
  • So this is kinda hard to predict.  ;)