Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Small improvements to current onboarding flow for new collectives #2330

Closed
xdamman opened this issue Aug 14, 2019 · 5 comments
Closed

Small improvements to current onboarding flow for new collectives #2330

xdamman opened this issue Aug 14, 2019 · 5 comments
Labels
discussion This issue is being discussed, and is not ready for implementation idea stale

Comments

@xdamman
Copy link
Contributor

xdamman commented Aug 14, 2019

opencollective.com/create

Quick short term fixes:

  • logo should be fixed (broken right now)
  • Default should be "Join Free", not "sign in"

  • ideally, we shouldn't let the user create an organization account at this point
  • FAQ should be contextual to create a collective, not to create an account (make an anonymous donation should go, we should add a question

  • this screen should go. Many people wonder what to choose here and it doesn't matter anyway.

  • Let's get rid of tags here. These can be added later.
  • We should add a field for the slug so that people know what is going to be the URL of their collective which will be the first thing they will have to share.

  • We shouldn't go straight to that screen. We should go to the collective page.

  • the empty collective page should have clear next steps such as "record a donation", "submit an expense" (but let's keep this for another issue since the collective page is being revamped right now). This also mean that the admin of any collective should be able to record a donation (aka "add funds").
@xdamman xdamman changed the title Onboarding flow Small improvements to current onboarding flow for new collectives Aug 14, 2019
@znarf
Copy link
Member

znarf commented Aug 14, 2019

@xdamman Can you use the new collective page as basis/screenshot?

@xdamman
Copy link
Contributor Author

xdamman commented Aug 14, 2019

The goal of this issue is to show the current flow as of today (and small improvements we can do to it). That's why I wrote for the last screenshot "let's keep this for another issue since the collective page is being revamped right now".

But for the record, here is the current look of the collective page right after creating a new collective:

@znarf
Copy link
Member

znarf commented Aug 14, 2019

Ok. In case you want any of these points to be worked on, let's make sure to create separate issues.

@alanna
Copy link
Contributor

alanna commented Aug 14, 2019

I agree with all these changes.

If they are creating an account for the first time here as well as creating a Collective, we should also have a platform newsletter opt-in check box.

This might be for a seperate issue but I'll comment here for now:

These changes make it clear how we need to work on the onboarding flow for self-hosting or applying to host once the Collective is created. I really like leaving that question until after the creation process is done, as suggested here.

Once they land on their Collective screen at the end, There can be action buttons in different places of the screen, like 'submit expense' 'create Update' 'create Event' 'edit description' 'update images' etc.

And also financial related stuff to get them into the host onboarding flow, such as "start accepting financial contributions" and if they click it send them into a flow for choosing or creating their Host. We could have greyed out versions of the financial contribution sections of the new Collective page so they can see what they are activating.

@znarf znarf added this to To Do in Create Collective Flow via automation Aug 27, 2019
@znarf znarf added idea discussion This issue is being discussed, and is not ready for implementation labels Aug 27, 2019
@stale
Copy link

stale bot commented Nov 25, 2019

This issue has been automatically marked as stale because it has not had recent activity. We want to keep it in our todo list but haven't had the time to address it yet.
Thank you for your contributions!

@stale stale bot added the stale label Nov 25, 2019
@sbinlondon sbinlondon moved this from To Do to Overview/Context in Create Collective Flow Feb 5, 2020
Create Collective Flow automation moved this from Overview/Context to Done Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion This issue is being discussed, and is not ready for implementation idea stale
Projects
No open projects
Development

No branches or pull requests

4 participants