If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Build UI for guided landing page experience

RESOLVED FIXED

Status

Webmaker
webmaker.org
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: OpenMatt, Assigned: akirose)

Tracking

Details

(Whiteboard: [teachcta] [landingpages] [july25])

Attachments

(2 attachments)

Comment hidden (empty)
(Reporter)

Updated

3 years ago
Assignee: nobody → aki
(Assignee)

Updated

3 years ago
Blocks: 1038395
(Assignee)

Comment 1

3 years ago
Created attachment 8458721 [details] [review]
https://github.com/mozilla/webmaker-landing-pages/pull/17
Attachment #8458721 - Flags: review?(cade)

Updated

3 years ago
Attachment #8458721 - Flags: review?(cade) → review+

Comment 2

3 years ago
Commits pushed to master at https://github.com/mozilla/webmaker-landing-pages

https://github.com/mozilla/webmaker-landing-pages/commit/5844f18bd6c8f6d1d390c0196ae1c3025a15097c
Bug 1038682 - Build UI for guided landing page experience

https://github.com/mozilla/webmaker-landing-pages/commit/00e5c6ed4596b42f9c7c9bca7808d8837abd0804
Merge pull request #17 from gesa/1038682/guided-landing-pages

Bug 1038682 - Build UI for guided landing page experience
(Assignee)

Comment 3

3 years ago
Now all I have to do is write the js to direct users to the appropriate make landing page experience to close this bug out!
Status: NEW → ASSIGNED
(Assignee)

Comment 4

3 years ago
Created attachment 8458821 [details] [review]
https://github.com/mozilla/webmaker-landing-pages/pull/19
(Assignee)

Updated

3 years ago
Attachment #8458821 - Flags: review?(kate)
(Assignee)

Comment 5

3 years ago
I think 5 fields might be too many. I've been filling this form out a lot to test it, and I keep getting COMPLETELY stumped at "reasons".

For context:
[Your name] and [a friend's name] got together one day at [place] to learn about [something on the web] because [reasons]. Making and learning about the web is awesome because [why?].

I really, really think we should drop "because reasons" to increase conversions. If we want to test it, the smaller percentage should get the greater quantity of fields.

Additionally, the more I'm playing with this, the more I realise that people are facing this form with zero context of what they're about to do. That makes "to learn [something about the web]" a really confusing field. Is there a way we can make that a little more intuitive? (I keep thinking about that UX bible "Don't Make Me Think!" http://www.amazon.ca/Dont-Make-Me-Think-Usability/dp/0321344758/ref=sr_1_1?s=books&ie=UTF8&qid=1405895098&sr=1-1 and how much that field makes me stop to think about what I'm doing, instead of just doing.)
Flags: needinfo?(matt)
(Reporter)

Comment 6

3 years ago
* If we kick this back for re-write and re-design, we'll miss deadline. Thinking.
Flags: needinfo?(matt)
(Reporter)

Updated

3 years ago
Flags: needinfo?(brett)
(Reporter)

Comment 7

3 years ago
* Hey, Aki. These are both great points. 

* Here's my proposal: ship as is. Then tweak and optimize based on our first week of results. 

* Michelle and I did some unscientific testing of the madlib with others, and they didn't seem to get stuck on [reasons] the same way. 
("because: HTML is easier than you think. because: creating on the web is awesome. because: animated GIFs rule.") 

* You may be totally right. But we made a commitment to do QA and testing today. If we re-write, we'll miss that deadline. Let's ship rather than making this a blocker. Then we can examine the early data that comes in and see where we need to optimize. 

* Your other point about not having enough guidance about what comes next is also excellent. We could probably solve that with one line of well-chosen copy -- let's address that in the next iteration as well.
Flags: needinfo?(aki)
Agreed, we need to make sure we have full coverage of all the technical steps we need to QA today.  We can adjust the copy as we run the funnel and have tests results.
Flags: needinfo?(brett)
(Assignee)

Comment 9

3 years ago
FYI, this is done save one bug in the code. I'm having some issues with the BSD API. I've been working on this literally all weekend, have now enlisted friends from OFA for a little back channel muscle.
Flags: needinfo?(aki)

Comment 10

3 years ago
Also see if you can find JP or Bobby on Twitter. They are both skilled at BSD bugs.
I'm fine shipping this to test, but I think we may have gotten carried away with madlibs. The madlib is just a tool to get info, it's not supposed to be en exercise in and of itself. We definitely should try something drastically simpler:

*[Your name] and [a friend's name] got together one day to learn about the web. 

Everything else is not actually useful, right? We're asking them to fill in information we have no use for, so it's worth eliminating as much as we can. At least to see if that helps CTR.
(In reply to Aki Rose Braun [:akirose] from comment #9)
> FYI, this is done save one bug in the code. I'm having some issues with the
> BSD API. I've been working on this literally all weekend, have now enlisted
> friends from OFA for a little back channel muscle.

Aki agree with Geoffrey, you might save yourself some time by pinging Bobby directly, he's wrestled with BSD forms quite a bit.
(Assignee)

Comment 13

3 years ago
Yeah that's the conclusion I came to while I was working with the madlibs this weekend as well. I'd rather ship a simpler mad lib (no additional dev time required, no additional copywriting required—we just remove some copy) and test the more complex stuff. The more complex stuff is already built so we can test right away. The most important thing is getting people using Thimble, right? Let's get everything out of the way and let them just do that!
Comment on attachment 8458821 [details] [review]
https://github.com/mozilla/webmaker-landing-pages/pull/19

R+ 1 teensy nit
Attachment #8458821 - Flags: review?(kate) → review+

Comment 15

3 years ago
Commits pushed to master at https://github.com/mozilla/webmaker-landing-pages

https://github.com/mozilla/webmaker-landing-pages/commit/ca4155e6b9bd6f593a9e0ba8a407572a9c61c6d6
Fixes Bug 1038682 - Build UI for guided landing page experience

https://github.com/mozilla/webmaker-landing-pages/commit/444d6154a5c20ef947ccf288d78f5e96fbee19f1
Merge pull request #19 from gesa/1038682/guided-javascript

Fixes Bug 1038682 - Build UI for guided landing page experience

Updated

3 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.