Closed toolness closed 10 years ago
Hi Atul, thanks for working on this.
Of course, happy to chat in more detail.
:+1: nice treatment of the user flow here.
considering what @jvallera said in her comment, I wonder if an easy fix might be to have the button be adjusted to say "request more information" or "request Hive member application".
Thanks for the replies!
In hindsight, I'm now realizing "membership applications" was a very bad way to put it... Basically, it seems like there are two ways users can create accounts on the Hive Directory and then feel a bit lost:
I guess that this PR is really trying to address group 1. We know of a number of such individuals in NYC in this situation: people who create accounts, aren't auto-vouched, and are then totally confused because they still don't see much on the site even though they're logged in. Eventually these people manually contact a Hive staff member (I suspect a number just give up before doing even this) and they fix it, after a clumsy exchange involving asking for usernames and such.
So, this PR is really meant to smooth out that interaction, rather than introducing brand new individuals to the Hive, for which I agree that just pointing them to the city's Hive website is a good idea.
What if we renamed this action from "apply for membership" to something else, like "request access to the directory", or just "ask for assistance"? We could first divert total newbies to a Hive city's website, ensuring that the only people who fill out the form are ones who we probably already know, but who for one reason or another don't have the access they ought to have.
Ok, in 376ad9d I changed the wording to be about applying for full access to the directory rather than membership. I also ran it by @jvallera and she's cool with it.
I will merge this PR and file a separate bug about directing complete newbies to the Hive organization's website for more information.
NOTE: The original title of this issue was "add support for membership applications" but that has changed.
As #31 mentions, users who haven't been vouched-for have as little access to the site as anonymous users. The move to a multi-city directory (see #27) further complicates matters: because there's no way to affiliate non-vouched users with a Hive city, staff have no idea how to make sense of them.
This PR adds support for membership applications, whereby users are guided through a basic application process, and relevant staff are notified of new applications.
User Flow
When a user who isn't already vouched-for visits the directory's home page, the following alert will always appear at the top of the page:
Upon clicking the link they will be taken to
/accounts/apply/
, which looks like this:Note that if the site is a multi-city install (i.e. the Hive Global Directory), the city field won't be auto-populated, and the user will be forced to choose from a list of all Hive cities.
All fields on this page are required. Once successfully submitted, the user will be redirected to the directory's home page with the following alert at top:
At this point, the fact that the user has filled out the application form is recorded in their user session, so they will not be alerted to fill out the application form again unless they log out and log back in (or log in from another device, etc).
Meanwhile, an email will have been sent out to either all staff in the selected Hive city or all superusers (if no staff exists in the Hive city). The email will look something like this:
Out Of Scope
Technical Considerations
I didn't want to have to bust a database migration, or deal with managing application models, so I just had the application form send out an email. If we really need to store the application in the DB, we can bust a migration for that later, but hopefully we won't need to.
Things Left To Be Done