1099408 - Create a unique graphic to reveal in the 'disruptive' EOY thank you page

Status: RESOLVED INCOMPLETE

(Webmaker Graveyard :: Communications, defect)

Description

[Matthew Willse [:mattheww]]

It will be used like this: http://codepen.io/okfuture/full/KwKQmo

Things to consider:
 - vector: we have limited kb. should be flat colors and simple geometry so we can draw it as svg vectors. 
 - text: should look good with fairly readable names as white or black on it.  
 - visual noise: logo and search and snippet text shouldn't collide. 
 - proportions: should match typical screen proportions. it can bet set to either be cropped or scaled to fit resized browser. JPG 1024x768 is fine for testing.

Comment 1

[Andrea Wood [:andreawood]]

On this specifically -- the "reveal" happens after a person clicks -- so would it be safe to say we could dedicate this page 100% to revealing names, and we don't need text or "donate" button at this point because they've already interacted / donated? Or, could we have a "share" CTA here?

Comment 2

[Matthew Willse [:mattheww]]

I designed this as an alternate view before clicking donate. But, if I understand you correctly, yes ... we could do something similar to this as a post donation thing with a share button.

Comment 3

[Andrea Wood [:andreawood]]

oh i see! I think the UX should be combined, so the final sequence is: You've got mail! Envelope drops > Click envelope/interact/Donate > Reveal names + share 

The "share" code for snippet already exists, if you saw the Firefox "Choose Independent" snippet it was 100% built for share. That might make things easier?

Comment 4

[hannah:hkane]

What's the status of this one?

Comment 5

[Matthew Willse [:mattheww]]

Cassie learned about the revised plan for this yesterday (thanks & share page as described in Bug 1101152). I'm sure she will cook up something nice, but it's a lower priority than the Message snippet.

Comment 6

[Chris DeCairos (:cade)]

As we move to deprecate the Webmaker Product from Bugzilla, I'm going to close down this issue, which hasn't seen activity in a very long time. 

If more work is required here, please re-file this in an appropriate Product/Component/Github Issue.