search

ushahidi / platform

Ushahidi Platform API version 3+
http://ushahidi.com
Other
684 stars 506 forks source link

Feature: Collection Industry info upon Signup #1034

Closed caharding closed 8 years ago

caharding commented 8 years ago

When someone signs up for a deployment we need to ask them:

1) Name of org if different from deployment name 2) Size of org by employees (drop down of 1-10, 10-50, 50-100, 100-250, 250-500, 500-1000, 1000+) 3) What are you using Ushahidi for? (Choose multiple by clicking CTRL) Advocacy Human Rights Humanitarian & Crisis Response First Responders Election Monitoring International Development Government Community Organizing Media and Journalism Environmental Monitoring Research Service Delivery Education Anti-Corruption & Transparency Philanthropy Marketing Other (order alphabetically)

snilsmitchell commented 8 years ago

Should we have an "Other" field as well?

caharding commented 8 years ago

Yes

jshorland commented 8 years ago

Before scoping:

Based on answers:

jshorland commented 8 years ago

Scope from nat:

When someone signs up for a deployment we need to ask them:

1) Name of org if different from deployment name 2) Size of org by employees (drop down of 1-10, 10-50, 50-100, 100-250, 250-500, 500-1000, 1000+) 3) What are you using Ushahidi for? (Choose multiple by clicking CTRL) Advocacy Human Rights Humanitarian & Crisis Response First Responders Election Monitoring International Development Government Community Organizing Media and Journalism Environmental Monitoring Research Service Delivery Education Anti-Corruption & Transparency Philanthropy Marketing Other

(Need to organize these alphabetically)

rjmackay commented 8 years ago

Q: Does this need to happen on sign up? or Should it happen after they've created a deployment? ie. should we prioritize more info from users, or reduced friction during sign up?

jshorland commented 8 years ago

I think it should happen on sign up, as we probably need it to be required to actually get people to fill it out. I don’t see 3 additional questions as too much of a blocker, given our sign up process is crazy simple and short as it is.

On Jun 19, 2016, at 8:52 PM, Robbie Mackay notifications@github.com wrote:

Q: Does this need to happen on sign up? or Should it happen after they've created a deployment? ie. should we prioritize more info from users, or reduced friction during sign up?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/ushahidi/platform/issues/1034#issuecomment-227045442, or mute the thread https://github.com/notifications/unsubscribe/ADE1GAkv_W4kpX2N3c11xmb-57agiUY6ks5qNg59gaJpZM4ILN5Q.

caharding commented 8 years ago

Agree with Jess this is the most important info we can get for sales

On Mon, Jun 20, 2016 at 8:02 AM, Jess Shorland notifications@github.com wrote:

I think it should happen on sign up, as we probably need it to be required to actually get people to fill it out. I don’t see 3 additional questions as too much of a blocker, given our sign up process is crazy simple and short as it is.

On Jun 19, 2016, at 8:52 PM, Robbie Mackay notifications@github.com wrote:

Q: Does this need to happen on sign up? or Should it happen after they've created a deployment? ie. should we prioritize more info from users, or reduced friction during sign up?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub < https://github.com/ushahidi/platform/issues/1034#issuecomment-227045442>, or mute the thread < https://github.com/notifications/unsubscribe/ADE1GAkv_W4kpX2N3c11xmb-57agiUY6ks5qNg59gaJpZM4ILN5Q .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ushahidi/platform/issues/1034#issuecomment-227169014, or mute the thread https://github.com/notifications/unsubscribe/ABizaU7dAazq408ANlWfnzkLwK4C67usks5qNquMgaJpZM4ILN5Q .

Charlie Harding Product Director

rjmackay commented 8 years ago

@jshorland double checking. I think we agreed this should happen at the end of the tour?

jshorland commented 8 years ago

Correct.

Jess Shorland Product manager jess@ushahidi.com

On Jul 3, 2016, at 7:00 PM, Robbie Mackay notifications@github.com wrote:

@jshorland https://github.com/jshorland double checking. I think we agreed this should happen at the end of the tour?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ushahidi/platform/issues/1034#issuecomment-230190703, or mute the thread https://github.com/notifications/unsubscribe/ADE1GEvh8Sn2XRWaFqS2M-60fD7CifTPks5qSGklgaJpZM4ILN5Q.

caharding commented 8 years ago

This is Brandon's call

On Sunday, July 3, 2016, Robbie Mackay notifications@github.com wrote:

@jshorland https://github.com/jshorland double checking. I think we agreed this should happen at the end of the tour?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ushahidi/platform/issues/1034#issuecomment-230190703, or mute the thread https://github.com/notifications/unsubscribe/ABizaeiF5oBl10NrBNbVhD4F1b08v2AOks5qSGkmgaJpZM4ILN5Q .

Charlie Harding Product Director

rjmackay commented 8 years ago

I think we need to park this in favour of fixing bugs for paying users.

jshorland commented 8 years ago

agreed 100%

On Jul 21, 2016, at 2:54 PM, Robbie Mackay notifications@github.com wrote:

I think we need to park this in favour of fixing bugs for paying users.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ushahidi/platform/issues/1034#issuecomment-234396031, or mute the thread https://github.com/notifications/unsubscribe-auth/ADE1GO_tMR41GE-l4OwMBOWvkAMxjDtwks5qX-qfgaJpZM4ILN5Q.

zhalloran commented 8 years ago

@caharding @rjmackay @jshorland @brandonrosage Where will this occur in the process. I've seen mention of it being inserted before the deployment is spun up, and after the tour. Should probably just be included as part of the signup process if we want to make sure everyone is presented with a prompt for this info.

caharding commented 8 years ago

Def part of the sign up process

On Tue, Sep 6, 2016 at 2:48 PM, Zack Halloran notifications@github.com wrote:

@caharding https://github.com/caharding @rjmackay https://github.com/rjmackay @jshorland https://github.com/jshorland @brandonrosage https://github.com/brandonrosage Where will this occur in the process. I've seen mention of it being inserted before the deployment is spun up, and after the tour. Should probably just be included as part of the signup process if we want to make sure everyone is presented with a prompt for this info.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ushahidi/platform/issues/1034#issuecomment-245106938, or mute the thread https://github.com/notifications/unsubscribe-auth/ABizaQTITa2_RF3QcHFFr6GWhl5C0z6Oks5qnd_LgaJpZM4ILN5Q .

Charlie Harding Product Director

zhalloran commented 8 years ago

@brandonrosage Do you have any screens for this?

rjmackay commented 8 years ago

.. ok I'm going to move this all the way back to Design so it gets a proper spec. Rather than waste @zhalloran's time

brandonrosage commented 8 years ago

The solution for this -- within the "Create deployment" flow and layout -- is staged in the dotcom pattern library:

caharding commented 8 years ago

Can you show people that they are on step X/3 to show that it won't take long to go through the whole process?

On Mon, Sep 12, 2016 at 9:42 AM, Brandon Rosage notifications@github.com wrote:

The solution for this -- within the "Create deployment" flow and layout -- is staged in the dotcom pattern library:

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ushahidi/platform/issues/1034#issuecomment-246409217, or mute the thread https://github.com/notifications/unsubscribe-auth/ABizaSINBO_n_0bWCY-QzKsObMN76P0xks5qpYDdgaJpZM4ILN5Q .

Charlie Harding Product Director

jshorland commented 8 years ago

+1

On Sep 12, 2016, at 10:42 AM, Charlie notifications@github.com wrote:

Can you show people that they are on step X/3 to show that it won't take long to go through the whole process?

On Mon, Sep 12, 2016 at 9:42 AM, Brandon Rosage notifications@github.com wrote:

The solution for this -- within the "Create deployment" flow and layout -- is staged in the dotcom pattern library:

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ushahidi/platform/issues/1034#issuecomment-246409217, or mute the thread https://github.com/notifications/unsubscribe-auth/ABizaSINBO_n_0bWCY-QzKsObMN76P0xks5qpYDdgaJpZM4ILN5Q .

Charlie Harding Product Director — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ushahidi/platform/issues/1034#issuecomment-246429724, or mute the thread https://github.com/notifications/unsubscribe-auth/ADE1GAA9X9PnQooBTYqGfu_tDVRLSqxRks5qpY8UgaJpZM4ILN5Q.

rjmackay commented 8 years ago

There's some broken styling in Chrome on step 2 https://www.dropbox.com/s/uysyoev81ymos30/Screenshot%202016-09-13%2009.28.55.png?dl=0

brandonrosage commented 8 years ago

I've pushed a revision to the "Create new deployment" layout that addresses the need for an indicator for how many steps are in the form, as well as the multi-select control bug.

The solution for the visual progress indicator borrows from the same pattern we use in the client: The "stepper."

Step 1

There is an accordion.js file that supports the interaction here, which listens to which accordion/stepper item a trigger is intended to activate and whether or not that target item is disabled.

There are two types of triggers demonstrated in the layout:

  1. Headings, which select their respective stepper item.
  2. Buttons within the form, which select the stepper item dictated by their data-accordion-trigger attribute.

The demo layout is also attempting to illustrate a couple of different states:

The accordion.js script responds to the presence or absence of the disabled attribute on stepper items and buttons. So the app should add or remove the attribute as it validates the various forms.

On a related note, this pattern is slated to be used for CSV import, which is a three-step process.

@jshorland: Let me know if you see any problems with this approach. @zack: Let me know if you have any questions about the logic or interactions here.

zhalloran commented 8 years ago

@brandonrosage Quick question: The second screen suggests that the organization info is required, but I'm pretty sure that's not the case. Anybody have thoughts on this? @jshorland @caharding?

brandonrosage commented 8 years ago

If it's not required, I'll add a "Skip this step" button alongside "Continue" in the layout.

zhalloran commented 8 years ago

I'm going ahead with the assumption that the org information is not required.

zhalloran commented 8 years ago

@rjmackay FYI, I'm building this with a separate organization model on the backend, but adding the creation to the deployment controller for the time being. We can discuss this approach on Tuesday. It should be mostly done by then.

jshorland commented 8 years ago

Creating deployment worked. Form sign up functional and matches patterns. Log in successful after creation.

small feedback:

screen capture on 2016-10-25 at 20-47-14

zhalloran commented 8 years ago

@jshorland That's great feedback, and something that we can easily implement in the template. I'll throw an error message in there tonight before I sign off and anyone else can tweak it if they want.

jshorland commented 8 years ago

Should also be a title for "email" box, and email instructions to the right side are not centered horizontally with the box.

jshorland commented 8 years ago

@rjmackay the only thing left on this are titles for email and password fields. See video above. The password error message is working well.

jshorland commented 8 years ago

BOOM. PASSES QA.