738544 - Update design for Privacy Home

Status: RESOLVED FIXED

(Marketing :: Design, task)

Description

[Jishnu Menon :jishnu]

Attachment: Draft Privacy Policy Text

Two designs needed:

    1 - http://mozilla.org/privacy landing page
    2 - design for http://mozilla.org/privacy/policies/product-name template (we'll drop in relevant content as it's available). First policy is for Fx.


Specific Requests

1. Help with layout of page for the following functionality: A summary at the top of the page, a list of feature specific disclosures at the bottom and a table of contents.
2. Help with responsive design - needs to work on mobile (as this is also the Mobile Fx policy)
2. Initial copy in word form attached - may be modified as to content but not likely as to form

Comment 1

[John Slater]

Thanks. Can you give us some more details about when this needs to go live?

Beyond that, let us know who needs to be involved from your end...we can set up a quick kickoff meeting next week to review the various next steps needed to get this going.

Comment 2

[Tom Lowenthal]

Attachment: Updated version of policy text.

I've attached an updated version of the text. Expect to see some more tweaks as we refine it, but nothing that should change the design constraints.

A kickoff meeting that sets out clearly what we need to deliver, what we can expect, and level-sets the requirements would be most appreciated; the sooner, the better. Jishnu and I are the two working on this update from out end. We should both be at every meeting. However, Jishnu is in charge of this project and I'm out of the office for the next week, so he's more important to have there. For the next week or so, I'm on European time, and busy during the day. Something in the 3-5p Pacific range is preferable.

We'd like to get this done as quickly as possible, preferably sooner. It was intended to be a Q1 goal. We've been trying to get the website implementation of this project started since December, but previously met with logistical and communication difficulties.

Thanks!

Comment 3

[Jishnu Menon :jishnu]

Thanks Tom.

Hi John,

I'm your point of contact in legal/policy for this project and will keep Tom in the loop. Just to clarify - this is the same project we emailed about earlier. Here's a recap of the project - please let me know if you think we still need a kickoff or other meeting and, if so, can we make that happen Monday or Tuesday?:

There are several parts:
1. Firefox privacy policy and privacy policy template - this is where most of the work will be
2. Some minor updates to privacy home (http://www.mozilla.org/en-US/privacy/)
3. Other privacy policies - once we get Firefox up, it will be easier to roll out others on the Firefox template

We can roll out changes as we design them.

Timing: Based on what WebDev and your team had said about your end of quarter, we expected it to slip into Q2. However, WebDev changed and committed to getting it up as soon as they have the design, so the design work is blocking on timing. I know we only just met with Tara last week to let her know about the design and just updated the bug yesterday. Can you let us know, based on your team's workload, when would be reasonable to finish design (I know some of this will be affected through our comments as the design involves)? That would help us understand when webdev gets it and when it goes live.

From our perspective, this was a Q1 goal but it sounds like some miscommunication about who needed to work on design only got us to the right person (Tara) week before last - definitely not anyone's fault. 

Summary: 

- from our perspective, it's an ASAP type project and a Q1 goal
- from webdev's perspective, they can push with an estimate of about 10 hours of work for the Fx policy and possibly much less for each additional one which they will commit to as soon as the design is ready
- we're looking to you and Tara to give us an estimate of how long this type of project typically takes from a design perspective

Involved parties: 

Privacy: Jishnu (project lead) / Tom (contributor)
Design: John and Tara
WebDev: Mike and someone he delegates

Does this help?

Thanks
Jishnu

Comment 4

[Tara (musingt)]

Hey guys

It seems like Slater and Alex had a discussion last week and Alex is speaking with webdev to see if they can handle this bug in the short term to update the page with new copy... and we'll roll this page up into the larger redesign efforts if it needs more visual polish in Q2.  

So. lets wait and see what Alex/Webdev says.

Comment 5

[John Slater]

Any updates here?

Comment 6

[Jishnu Menon :jishnu]

Hi All,

Here's the project flow and status:

A. Re-designed page for mozilla.org/privacy
========================================
Status: #1
Subtasks
1. Tara: Create new design based on conversation with privacy, ETA: ?
2. Alex/Jishnu/Tara/Tom: Review/iterate on design. 
3. Mike: Implement new design
4. Alex/Jishnu/Tara/Mike/Tom: Review/iterate on implementation. 

B. Re-designed template for privacy policies
=========================================
Status: #1
Subtasks
1. Tara: Create new design based on conversation with privacy, ETA: ?
2. Alex/Jishnu/Tara/Tom: Review/iterate on design. 
3. Mike: Implement new design
4. Alex/Jishnu/Tara/Mike/Tom: Review/iterate on implementation. 

C. Posting privacy policies
========================
Firefox to be done first. Thunderbird and websites to follow initially, others gradually be moved, pending re-writes.
Status: Blocked by A and F.
1. Mike: Implement design from A with additional policies
2. Alex/Jishnu/Tara/Mike/Tom: Review/iterate on implementation. 

D. Additional Descriptive content for Support pages
========================
Status: In progress.
1. Tom: Write description of Cookies & LSOs
2. Tom: Write explanation of changing search providers
3. Mike: Cause pages to be posted on SUMO

E. Other Tasks
===========
Status: In progress
1. Mike: Place all previous privacy policies at unique, dated URIs
2. Mike: Have hand-written RSS feed of previous and the current privacy policy
3. Mike: Make mozilla.org/privacy/policies/$PRODUCTNAME redirect to current policy pages for *all* policies
4. Jishnu: arrange for metrics to post descriptions of telemetry, test pilot, MDP

F. Privacy Policy Content
=========================
Status: In progress
1. Tom: Send Jishnu one-paragraph description of DNT to privacy policy
2. Tom: Send Jishnu one-paragraph description of Snippets
3. Jishnu: Edit master privacy policy with content, post master to governance. Once through governance, provide Mike with master draft.

Comment 7

[Jishnu Menon :jishnu]

Ping on this.

Comment 8

[Tara (musingt)]

Hi there.  Lee Tom is on board and going to be taking this on.  He's clearing his plate of a few other things but we spoke last week and he's going to follow up with any questions he might have.  We're on it.   Thanks for the ping.

Comment 9

[Tara (musingt)]

Hey guys, just adding a few points of clarification here (please let me know if something doesn't sound right):

* Lee is focusing on the Privacy Home.  As discussed, finding the sweet spot between the previous Privacy Home (that he redesigned roughly a year ago) and the new version that Webdev kindly hacked together on short notice.  Basically creating a template for content that organizes the information in a digestible way and is aligned with the new look 'n feel of our web properties.

* The individual Privacy Pages are not in scope for this bug (re:comment #2).  The content there is for the Firefox Privacy Page, which isn't what Lee is working on right now.  We'll create a template for the Privacy Home, and then work on a template for the privacy pages (which is a related but different project - and bug). With that in mind, I'd like to change the name of this bug to align with that.  Otherwise the bug might become hairy and confusing to follow.

Hope that helps. 
Meanwhile, Lee is hacking away and will post something as soon as he can.

Comment 10

[Jishnu Menon :jishnu]

Hi Tara,

We can open a new bug for the

Comment 11

[Lee Tom]

Attachment: Firefox Privacy Home - 01

Hi all,
Here's a stab of wrangling our Privacy content and displaying it in a digestable way, as Tara mentioned. Here are some high-level ideas/goals that this mockup is based on:

Hero (page title and feature slides)
- If there are Privacy-related Add-ons, Firefox features, or relevant stories in the news etc. this could be a helpful tool to put it front and center. It may take some level of curating, so if it seems more sustainable to display an introductory paragraph, we can do that too.

Privacy Policy Links
- I don't see these links on the dev/staging page, but I'm aware we have specific policy pages for many of our websites. Maybe users can have access to these links if they're in a column that slides to the top of the page, no matter what section they're on (persistent) 

Main Section Navigation
- In my mockup, each section can be accessed by an anchor-tag. Unfortunately, the page is getting very long with all of the content exposed and stacked. We can use a simple "Back to top" link, or perhaps the navigation bar scrolls down the page to the top of any section selected (persistent with the side-nav policy links), so the user is not having to bounce up and down. 

Other Approaches...
- Tumblr's privacy page uses a persistent side-nav list to access every section of the page at all times: http://www.tumblr.com/policy/en/terms_of_service

- Twitter and Tumblr use "tips" or call-outs with informal language to help users scan and digest sections easier. I think this is a very helpful tool and might be an opportunity to inject a bit of friendly, brand voice onto the page.
https://twitter.com/privacy

Comment 12

[John Slater]

Good stuff, thanks Lee. I really like the idea of keeping the nav at the side or top (or both) consistent as you scroll down...I think that would make the page much more usable and help people find the right content more easily.

Privacy folks, what do you think?

Comment 13

[Tom Lowenthal]

This mockup is spectacular. I see the concern about the maintainability of the hero, but I rather like it as a way to get out contemporary content quickly. I think that having the stick to the top of the screen when you're about to scroll past it would be lovely.

Good thoughts on the Twitter and Tumblr sites. Those would make great additions to the privacy policy designs [bug 753404].

Comment 14

[Tara (musingt)]

Thanks Tom (and Lee).

Tom, how would you like to proceed?  Are there other folks that need to review this and share feedback? will you share with your team and roll up collective feedback? or did you need to get together for a quick in-person chat to review the design and discuss feedback?  Please let me and Lee know.  

Thanks

Comment 15

[Jishnu Menon :jishnu]

Hi Tara and Lee,

Fantastic job on this - I really like it! Sorry for the delay in responding - I was in DC at the end of the last week. Next steps - I think we're ready to implement this. Could we move into having Schalk or someone else on Mike's team framing it? I'm redrafting language for each section and will send that over to the implementer.

Thanks
Jishnu

Comment 16

[Mike Alexis [:malexis]]

Created implementation bug#755055

Jishnu: please add final copy and any details, requirements, special instructions for implementation

Lee: please add PSDs when ready

Comment 17

[Lee Tom]

Here's the PSD:

http://cl.ly/1X1P0d2H3e200x20130r