Create a coherent diesel/dashboard flow for new users

[mixonic]

• User creation and initial session open in diesel
• Redirect after creation to /organizations/new in dashboard
• After email verification, user is redirected into account/stack FTUX at diesel

[mixonic]

Screenshots for the account/stack FTUX that must be ported to diesel:

1. The session from dashboard must be passed off to diesel.
2. SSH Key
3. SSH Key error state
4. App handle
5. Database handle
6. Database handle and slider
7. Provisioning poller
8. Success page
9. User is directed to apps.index

[skylar-anderson]

@mixonic, proposed changes from our discussion:

1. Pricing page

• Separate development and production boxes on pricing page
• Specific plans langing pages (future)

2. Create account

• CTA to get help or contact us
• Move organization name to account creation screen

3. Create organization

• Remove entirely (yay)

4. Create app and database

• Summary of what apps and databases are
• "Create" first app and databases

5. Activation email

• Brief description of what aptible is

6. Dashboard first-time

• CTA to deploy app created in Step 4
  • Prompts for user to enter SSH Key. Brief instructions on how to get SSH key
  • Instructions on deploying via
• CTA to add people or roles

[mixonic]

The new flow, page by page, would be:

1. Pricing page
2. Create account (with org name). Should have an alternative path available to just submit a query asking for more information.
3. Create App & Create DB on one page. This should also explain what an app and db are conceptually.
4. Submit a credit card. This is the only part of the flow that will be on the Ruby dashboard codebase.
5. Complete the email verification
6. Provisioning poller & success page. Upon completion users should have an option to learn/complete deployment configuration, or to add people to their organization.

[mixonic]

I'm going to close this in favor of the details we are already going into on #51