break up the UI for project creation into logical steps

[JohnRDOrazio]

In the current example from PR #24, a minimum amount of user info (project role and email address) is requested to get the project started, and this is mixed in on the same screen space as some basic information for the Wedding Ceremony. Then in a separate space, but on the same screen, we start defining the wedding party.

I think it would be a better user experience to divide this up into steps, such that the user shouldn't have to scroll down the screen with a huge long form to fill out.

FIRST STEP: minimum user info (project role and email address) is requested ONLY IF the user is not logged in; if logged in we will already have this information and we can go directly to Step 2

SECOND STEP: Basic info about the Wedding Ceremony (type of ceremony, date, church, city, celebrant)

THIRD STEP: Define the wedding party (Bride, Groom, Best Man, Maid of Honor, Bridesmaids, Groomsmen, Parents, etc.)

Then from the FOURTH STEP on, we will have a number of steps to choose the different parts of the ceremony.

This also makes sense from a Model point of view, because while STEP 1 has to do mostly with the Users model, STEP 2 has to do only with the Projects model, and step 3 has to do only with the WeddingPartyMembers model. This way our view is broken up into smaller views which are more closely linked with the models, making for a cleaner user experience...

[JohnRDOrazio]

Maybe a bit off topic, but isn't this just a really neat UI / UX? 😄 (wait about 15 seconds before navigating away from the page 😉 )