-
Notifications
You must be signed in to change notification settings - Fork 153
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
[Fellowships Mini Site] Draft and plan "Application closed content" #1135
Comments
This is happening soon. Do we have a plan yet? |
We touched base with @jessevondoom earlier this week. He was going to check to see if we could replace the "apply" button with an email capture. The plan is not to change any of the main body text (except to take out the call for applications reminder in the middle of the page). Can we:
|
I think we should keep "Be a Fellow" as that encourages folks to read the
rest of the page (or else they may not see the opportunity at the end to
show their interest
…On Thu, Apr 19, 2018 at 4:20 PM, Taís de Souza Lessa < ***@***.***> wrote:
Embedding email field would be the best choice if possible :). Also we
should change the icon ***@***.*** <https://github.com/alanmoo> let me know
when you plan to work on that and I can pair with an engineer).
Are we changing the "Apply Now
<https://foundation.mozilla.org/fellowships/apply/>" page as well to the
proposed mockup posted on this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1135 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHwt8sr2Jxq4QPBNQkB80IPHxic-pwP-ks5tqRvYgaJpZM4Sae1Q>
.
|
Even if we can't get the email grab embed up, can we flip the button to
unlink from the application and to say "applications are closed" by Mon
please? Thank you.
On Fri, Apr 20, 2018 at 12:57 PM, Amy Schapiro <[email protected]>
wrote:
… I think we should keep "Be a Fellow" as that encourages folks to read the
rest of the page (or else they may not see the opportunity at the end to
show their interest
On Thu, Apr 19, 2018 at 4:20 PM, Taís de Souza Lessa <
***@***.***> wrote:
> Embedding email field would be the best choice if possible :). Also we
> should change the icon ***@***.*** <https://github.com/alanmoo> let me
> know when you plan to work on that and I can pair with an engineer).
>
> Are we changing the "Apply Now
> <https://foundation.mozilla.org/fellowships/apply/>" page as well to the
> proposed mockup posted on this issue?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1135 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AHwt8sr2Jxq4QPBNQkB80IPHxic-pwP-ks5tqRvYgaJpZM4Sae1Q>
> .
>
|
#1441 Will unlink the application. |
@community-impact and @alanmoo: considering conversation I had with Alan today on what's possible for this page and also what I read on this thread, here are my suggestions. We could either add the e-mail address or a button that links to a Google Form, as proposed by Amy. I feel the button to Google form is a better option because the data can then be stored in a spreadsheet for the Fellowships team rather then spread in emails (up to Amy to decide, though). Here is the user flow for the 2 options - scroll to see option 2: InVision link Screens for option 1: Overview Page + Apply Page Screens for option 2: Overview Page + Apply Page Questions @auremoser any thoughts here are welcomed! adding you to the loop :). |
Thanks Tais. I'd prefer option #2. I'd recommend changing "be in the loop"
to "Get more info" to reduce any possible confusion for international
candidates with what be "in the loop" means.
If you do approve the button option, please let me know and I can send you
a form
…On Mon, Apr 23, 2018 at 2:14 PM, Taís de Souza Lessa < ***@***.***> wrote:
@community-impact <https://github.com/community-impact> and @alanmoo
<https://github.com/alanmoo>: considering conversation I had with Alan
today on what's possible for this page and also what I read on this thread,
here are my suggestions.
We could either add the e-mail address or a button that links to a Google
Form, as proposed by Amy. I feel the button to Google form is a better
option because the data can then be stored in a spreadsheet for the
Fellowships team rather then spread in emails (up to Amy to decide,
though). Here is the user flow for the 2 options - scroll to see option 2: InVision
link
<https://mozilla.invisionapp.com/share/BAGJFYP3CN5#/293064829_User-Flow-Applications-Closed>
*Screens for option 1:* Overview Page
<https://mozilla.invisionapp.com/share/BAGJFYP3CN5#/293064310_Applications_CLOSED_-_V3-FellowshipsUI_-_Overviewv1>
+ Apply Page
<https://mozilla.invisionapp.com/share/BAGJFYP3CN5#/293064309_Applications_CLOSED_-_V3-FellowshipsUI_-_Be_A_Fellowv1>
*Screens for option 2:* Overview Page
<https://mozilla.invisionapp.com/share/BAGJFYP3CN5#/293064311_Applications_CLOSED_-_V3-FellowshipsUI_-_Overviewv2>
+ Apply Page
<https://mozilla.invisionapp.com/share/BAGJFYP3CN5#/293064308_Applications_CLOSED_-_V3-FellowshipsUI_-_Be_A_Fellow-V2>
*Questions*
*For Alan:* are those implementation options okay and fairly easy to
implement? Any thoughts?
*For Amy:* if both options are feasible (to be confirmed with Alan),
please let me know which one do you prefer and also could you please take a
look at the copy and do some tweaks? I added a few words on your suggested
copy to adjust it to the contexts of email and button, please take a look
and feel free to make improvements (copy is not my strength).
Here is the copy I am talking about:
[image: image]
<https://user-images.githubusercontent.com/22157921/39153592-73d6a354-4700-11e8-93f7-d47239ade79f.png>
[image: image]
<https://user-images.githubusercontent.com/22157921/39153600-7b15b3f8-4700-11e8-9002-df1b7c0909b3.png>
@auremoser <https://github.com/auremoser> any thoughts here are welcomed!
adding you to the loop :).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1135 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHwt8mXOSFG3abghNNQSn8elkoLSu9krks5trkQjgaJpZM4Sae1Q>
.
|
👍 I like the option 2 version for the Apply Page. I worry that giving people dates will restrict us or might be another thing we could forget to update next year. Currently, text is:
I might edit the text to say something like the following:
"Sign up" or "Get more info" are fine too. I like the jazziness fo "stay in the loop" but understand that it might not be intuitive. |
I like Aurelia's recommendation, with the button saying "Get more info"
…On Mon, Apr 23, 2018 at 3:01 PM, Aurelia Moser ***@***.***> wrote:
👍 I like the option 2 version for the Apply Page
<https://mozilla.invisionapp.com/share/BAGJFYP3CN5#/screens/293064308_Applications_CLOSED_-_V3-FellowshipsUI_-_Be_A_Fellow-V2>
.
I worry that giving people dates will restrict us or might be another
thing we could forget to update next year.
Currently, text is:
Applications are currently closed. Applications for the 2018-2019 cycle:
click on the button and fill in the form. We will send you info when
applications are open <button>Be in the Loop</button>
I might edit the text to say something like the following:
Applications are currently closed. Interested in the subsequent
application cycle? Please click the button at right, and fill out the form.
We will send you info when applications re-open! <button>Stay in the Loop
</button>
"Sign up" or "Get more info" are fine too. I like the jazziness fo "stay
in the loop" but understand that it might not be intuitive.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1135 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHwt8vtW2YXIMWpvdpH9-L8A1UNCuvtVks5trk9JgaJpZM4Sae1Q>
.
|
Either of those items are pretty straightforward, but I’m curious if dumping visitors to a google form is the best way of getting them into the funnel for next year- seems like that’s the kind of thing the CRM is perfectly designed for. @stephaniemcv @desiree-mofo might have thoughts |
Yes, the long-term vision is to get these interested folks into the CRM. This type of email capture is an interesting challenge as it's very specific to limited messaging about application cycle notification and not a mass marketing/promotional email relationship. This is an issue on docket to address when we begin the Fluxx+Salesforce integration and Fellowship program implementation into Salesforce. In the short-term the google form is probably going to be the best bet. |
Thanks for the feedback here, all! 🎉 Based on it, here are the comps: @auremoser @community-impact please let me know if those are good to go so I can create an implementation ticket to engineers. Also, could you please create a Google Form with the fields you want and give me access to it once it is done? Then I can customize it. Important:
|
Looks good to me, and good catch on the "at right" deletion! |
Looks good, thought we should change the "apply to be a fellow" menu label as well until applications are open again - @KevZawacki what do you think? Perhaps "How to get involved?" |
Also here is the link to the form I just created https://docs.google.com/forms/d/e/1FAIpQLSdTUqJ9Z4xdcVr4IMzd9UESqm7XwcpVdrIXDeeFNIHUc_vhvQ/viewform |
@community-impact 👍 Or simply "Get Involved" |
@community-impact here is the mockup with "Get Involved" as a menu label: Overview Page |
@community-impact I added some custom images to the form. In this way, the transition between site and form is smoother and the visual identity is preserved. |
I think the "Get Involved" menu and URL changes looks good, as do the
changes you made to the form.
…On Wed, Apr 25, 2018 at 1:40 PM, Taís de Souza Lessa < ***@***.***> wrote:
@community-impact <https://github.com/community-impact> I added some
custom images to the form. In this way, the transition between site and
form is smoother and the visual identity is preserved.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1135 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHwt8itUuNHMrIEu_ixILYlhxBsnHHnAks5tsN9GgaJpZM4Sae1Q>
.
|
Cool! Here is the implementation ticket, to be done by engineers: #1457. Closing this ticket. Thanks all! |
Issue
Once our applications close, we should have a plan in place to:
InVision mockups for those stages:
Item 1
Item 2
@jessevondoom @xmatthewx @community-impact - I am keeping this issue open as a reminder for us :)
The text was updated successfully, but these errors were encountered: