Closed Bug 959403 Opened 10 years ago Closed 9 years ago

Data Privacy Day Landing Page Build

Categories

(www.mozilla.org :: Pages & Content, defect)

Development/Staging
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lizzn, Assigned: craigcook)

References

()

Details

(Whiteboard: [kb=1247242] )

Creative Brief: https://docs.google.com/a/mozilla.com/document/d/14rSJWE8fpuP2--edaJvwLiNG4h33jgw5SuKUsJ_Jvog/edit?usp=sharing

Background/objectives: 
We've decided to implement a lovely, simple landing page that highlights and links to the 6 areas of privacy we'd like to cover. The landing page will serve many purposes: there will be one unified message (Mozilla Stands for Privacy), one unified CTA, a main KPI of Mozilla's overall Privacy Day engagement, a page to use for subsequent Privacy Days/other Privacy-related campaigns (ie. Ponemon 2014 announcement) AND a template for similar landing pages to use during other campaigns.

Layout:

HEADER: Mozilla Stands for Privacy 

HERO IMAGE: See Bug 959373. Modeled on last year's image: (https://blog.mozilla.org/files/2013/01/most-trusted-privacy-2012.jpg) + Lightbeam web image (http://www.mozilla.org/en-US/lightbeam/)
See Bug 959373

OVERVIEW PARAGRAPH: "With every product Mozilla creates, we put privacy first and foremost. It's in our DNA/in our Manifesto."

BODY: 6 boxes (maybe 2x3) with Header, 1-2 lines of descriptive copy, link/CTA

1. Learn about Mozilla’s Privacy Principles (http://www.mozilla.org/en-US/privacy/)

2. Turn on DNT  (http://www.mozilla.org/en-US/dnt/)

3. “Track the trackers” using Lightbeam (http://www.mozilla.org/en-US/lightbeam/)

4. Use Privacy add-ons in Firefox (https://addons.mozilla.org/en-US/firefox/extensions/privacy-security/)

5. Webmaker - Learn privacy basic practices by remixing the web (https://laura.makes.org/thimble/privacy-and-security-teaching-kit)

6. PR blog post - (Harvey) - Support USA Freedom Act (tentative)
Privacy Day is Jan. 28, so this site will need to be live by 01/27.
Assignee: nobody → jmontano
(In reply to Lizz Noonan from comment #1)
> Privacy Day is Jan. 28, so this site will need to be live by 01/27.

Will this live under mozilla.org/privacyday/ or another url? Will this be localized?
(In reply to raymond [:retornam] (needinfo? me) from comment #2)
> (In reply to Lizz Noonan from comment #1)
> > Privacy Day is Jan. 28, so this site will need to be live by 01/27.
> 
> Will this live under mozilla.org/privacyday/ or another url? Will this be
> localized?

I was thinking either mozilla.org/privacyday or mozilla.org/privacy/privacyday...something like that. Definitely open to suggestions, though!

When speaking with stakeholders yesterday, we are thinking there will not be time to localize, so most likely it won't be. However, there is a possibility it will be in PT-BR and ES. I will update the bug when I know if that will be the case or not.
Blocks: 960158
My recommendation:

www.mozilla.org/privacyday/

or

www.mozilla.org/privacy/day/

Lizz: Will we be redirecting people to this page via any print material that they would have to type in the URL?
Assignee: jmontano → malexis
Whiteboard: [kb=1247242]
(In reply to Chris More [:cmore] from comment #4)
> My recommendation:
> 
> www.mozilla.org/privacyday/
> 
> or
> 
> www.mozilla.org/privacy/day/
> 
> Lizz: Will we be redirecting people to this page via any print material that
> they would have to type in the URL?

No, not that I know of! I think all the communication about the page will be through digital channels.
Depends on: 959377
Depends on: 957095
Here's the PSD files for the site: https://www.dropbox.com/s/w7rjm9imnhu5go9/PrivacyDay_website_v4.psd

And for the hero image: https://www.dropbox.com/s/nvkd7q0sei8wxrq/PrivacyDay_heroGraphic_2x.psd

Here's a reference guide: https://bug957095.bugzilla.mozilla.org/attachment.cgi?id=8363331

There's one more person reviewing the copy, so if she has any changes, I'll let you know tomorrow morning. LMK if there's any questions, etc. 

Thanks!
Lizz
(In reply to Lizz Noonan from comment #3)
> When speaking with stakeholders yesterday, we are thinking there will not be
> time to localize, so most likely it won't be. However, there is a
> possibility it will be in PT-BR and ES. I will update the bug when I know if
> that will be the case or not.

Why aren't l10n-drivers consulted on the possibility to have that content localized and the list of locales we should target?
Assignee: malexis → craigcook.bugz
(In reply to Pascal Chevrel:pascalc from comment #7)
> (In reply to Lizz Noonan from comment #3)
> > When speaking with stakeholders yesterday, we are thinking there will not be
> > time to localize, so most likely it won't be. However, there is a
> > possibility it will be in PT-BR and ES. I will update the bug when I know if
> > that will be the case or not.
> 
> Why aren't l10n-drivers consulted on the possibility to have that content
> localized and the list of locales we should target?

Pascal, we will be localizing this page, shooting for early to mid-February. I will be filing a localization bug later today. However, there was not enough time to localize this page before Privacy Day next Tuesday.
Hi Craig! The hero image files I posted above are missing an element. Please use this file instead: http://cl.ly/3O2S0x170f1b
Is the text in the PSD the final approved copy or is there a separate canonical copy deck I should refer to?
(In reply to Craig Cook (:craigcook) from comment #10)
> Is the text in the PSD the final approved copy or is there a separate
> canonical copy deck I should refer to?

I think it's the same, but JIC, here's the copy deck: https://docs.google.com/document/d/1iz3dv7_5yqiJOSjckK0hicZYW95D7IzS2hO21sqBVvQ/edit?usp=sharing
Hi Craig!

I have two changes that came up today I'm hoping you can make. Please LMK if there's any issues with these requests. 

I've changed it in the copy deck as well, but could you have the DNT link drive to https://support.mozilla.org/en-US/kb/how-do-i-turn-do-not-track-feature?redirectlocale=en-US&redirectslug=how-do-i-stop-websites-tracking-me

The other one is a little more involved but hopefully it's doable without too much extra leg work. 

Under the main headline, where it says, "EXPLORE OUR PRIVACY PRINCIPLES"...would it be possible to have that display for Firefox users and then when someone visits the page from another browser, there would be the "Download Firefox" button (second button in left column on http://www.mozilla.org/en-US/styleguide/websites/sandstone/buttons/) instead?
(In reply to Lizz Noonan from comment #12)
 
Updating the DNT link is easy. Detecting the browser and showing a download button is a little trickier but it should be doable. For the moment let's assume we can do it and I'll let you know if we hit a snag.
(In reply to Craig Cook (:craigcook) from comment #13)


YAY! Thanks a million times over! There will be many happy people coming from this button placement :)
Hi Craig - since this page is going to live and be used beyond Privacy Day, could we please make the live URL www.mozilla.org/privacy/action/? Thanks!
(In reply to Lizz Noonan from comment #15)
> Hi Craig - since this page is going to live and be used beyond Privacy Day,
> could we please make the live URL www.mozilla.org/privacy/action/? Thanks!

Just realized that the way I wrote it above looks wrong with the ?, should be www.mozilla.org/privacy/action/
Lizz-

I spoke with Cmore and Holly, and could we do mozilla.org/privacy/you ?

Thx,
Jen
(In reply to Jennifer Bertsch [:jbertsch] from comment #17)
> Lizz-
> 
> I spoke with Cmore and Holly, and could we do mozilla.org/privacy/you ?
> 
> Thx,
> Jen

I like the /privacy/you/ idea as the page is everything we do privacy-wise for "you". The "you" will be each set of eye balls looking at the page. :)
(In reply to Chris More [:cmore] from comment #18)
> (In reply to Jennifer Bertsch [:jbertsch] from comment #17)
> > Lizz-
> > 
> > I spoke with Cmore and Holly, and could we do mozilla.org/privacy/you ?
> > 
> > Thx,
> > Jen
> 
> I like the /privacy/you/ idea as the page is everything we do privacy-wise
> for "you". The "you" will be each set of eye balls looking at the page. :)

I checked with Stacy and she's cool with that. /privacy/you/ it is!
(In reply to Lizz Noonan from comment #19)
> (In reply to Chris More [:cmore] from comment #18)
> > (In reply to Jennifer Bertsch [:jbertsch] from comment #17)
> > > Lizz-
> > > 
> > > I spoke with Cmore and Holly, and could we do mozilla.org/privacy/you ?
> > > 
> > > Thx,
> > > Jen
> > 
> > I like the /privacy/you/ idea as the page is everything we do privacy-wise
> > for "you". The "you" will be each set of eye balls looking at the page. :)
> 
> I checked with Stacy and she's cool with that. /privacy/you/ it is!

woo hoo!

craig: the url will be /privacy/you/

thx!
Blocks: 962880
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/e25a1b55df2d31a7869fbb267584c7997b49d7c5
Fix bug 959403 - add Privacy Day landing page

Also remove the l10n call in tabzilla in the base templates.

https://github.com/mozilla/bedrock/commit/6dcced97810998ca3006a56c997f6c890b394407
Merge pull request #1623 from craigcook/bug-959403-privacy-day-landing-page

Fix bug 959403 - add Privacy Day landing page
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Commit pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/9ab1e99ba1fe9cf0969348dfe10309ac8b340f63
Bug 959403 - reverting to original DNT copy pending legal review
And now, prod: https://www.mozilla.org/en-US/privacy/you/
Status: RESOLVED → VERIFIED
OS: Mac OS X → All
Hardware: x86 → All
We're expecting revised copy for this today. 

Stacy please add when ready.

We don't normally do pushes after 2pm PST so we can target to have the page updated early PST tomorrow (Thurs).
Status: VERIFIED → REOPENED
Flags: needinfo?(smartin)
Resolution: FIXED → ---
Hi all - Thank you for all of your help with this!  Copy revisions are now in Bug 964445.
Flags: needinfo?(smartin)
Status: REOPENED → RESOLVED
Closed: 10 years ago9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.