Refactor: sprint to begin new user journey about parabol HOT 11 CLOSED

I am wondering @mattkrick if you'd like to take the lead on this?

from parabol.

Proposing a slight change to this:
let's replace /me/:id with /me. The id is just state, they're only ever going to visit a single /me/:id, and not only does this clean up urls, but it makes it super easy for UX.

User story: "Hey Jordan, where do I go to see my dashboard?" Jordan copies his url & pastes it. "Here you go Terry: http://localhost:3000/me". "We love Action!". THE END.

from parabol.

Much of this is not at all required for this mission, but I wanted to scratch it out here.

To summarize, we are moving toward the following locations:

1. A "public" site that houses our landing page, Pricing, FAQ, etc. handing off of / and a few other routes.
2. A /welcome route. When a team leader creates an account, they are redirected here. A team is created for them, and they are able to invite their team members here. Once the process is done, they are redirected to /team/:id.
3. A /team/:id route, houses the team dashboard (and will eventually pop a toast 🍞 ) if there is an active meeting in progress
4. A /me/:id route, that allows a user to access their personal dashboard
5. A /me/:id/profile route to edit a user's own profile

Following this mission we'll need to implement the journey for folks who've been invited by their team leader to join the team. I imagine, routes-wise, this is how that'll work:

1. Email is sent to invitee containing link to /welcome/invitee?token=d3adb33f
2. User will create an account, and /welcome/invitee will validate token, join the CachedUser to the team, redirect them to /me/:id/profile?source=welcome&nextAction=team/:id.
3. When complete, it will redirect the user to their /team/:id dashboard

from parabol.

@jordanh most definitely! i'll dig in on my flight tomorrow & shoot ya back any clarification questions tomorrow night.

from parabol.

@jordanh @ackernaut
Let's chat CachedUser and UserProfile.

• Two different tables? We'll need both on the initial user query, so maybe just 1?
• What fields should UserProfile have?
• Should we store them in the same place in cashay?

from parabol.

I separated them only so it was clear what was being stored in Auth0.

That still makes sense to me, but if you want to change it, it won't break my heart!

Jordan
@jrhusney(http://twitter.com/jrhusney)/612.227.5673(tel:612.227.5673)

On Jun 15, 2016, 18:21 -0700, Matt [email protected], wrote:

@jordanh(https://github.com/jordanh)@ackernaut(https://github.com/ackernaut)
Let's chatCachedUserandUserProfile.

Two different tables? We'll need both on the initial user query, so many just 1?
What fields shouldUserProfilehave?
Should we store them in the same place in cashay?

—
You are receiving this because you were mentioned.
Reply to this email directly,view it on GitHub(#63 (comment)), ormute the thread(https://github.com/notifications/unsubscribe/AAGSWOeYUBAxR-6XtuajvrkAxw95mNTNks5qMKUegaJpZM4IyAYq).

from parabol.

Nono, I'm up for anything, I just need to design UserProfile and TeamMember before I can move forward.
We'll need something like a createdTeam or payerAccount, but those will probably reside on TeamMember since they're team specific. You haven't by chance scratched out a rough draft relational schema, have you? 😄

from parabol.

Not beyond:
https://docs.google.com/document/d/1KyHMvagyepPoGrfa38LWNIbcBfRzCfaILSLkQa9D2Ng/edit#heading=h.qwhnypti21k8

from parabol.

Awesome!

from parabol.

After #71, #73, I think we're good to close this, ya?

from parabol.

Ja!

from parabol.