Closed Bug 727657 Opened 13 years ago Closed 13 years ago

[Launch Persona ID] 5 pages on mozilla.org in One Mozilla theme

Categories

(www.mozilla.org :: General, defect)

Product:
www.mozilla.org
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: christine.brodigan, Assigned: jlong)

References

(
URL
)

Details

Steven, This is going to disrupt things a bit, please bear with us, we need to launch 3 pages on mozilla.org for the MWC Mozilla Persona announcement. The good news, is that these should go into the One Mozilla themes that you're already working on :-) We will be migrating these as P1 over to Bedrock. Pages: http://mozilla.org/persona http://mozilla.org/persona/about http://mozilla.org/persona/developer-faq Here are the PSDs for the first two: About http://cl.ly/0M172y190y470k16133G Dev FAQ http://cl.ly/2V1k2N450I2A0E3h1g0A Deadline: 1.7 milestone (yikes!) If you need extra help, please let us know. I've cc'd wenzel & malexis for backup resourcing.
The 1.7 milestone isn't realistic for these pages. We're still working on finalizing the overall one-mozilla theme (Sandstone), and having it solid enough to build out three pages, one of which we don't even have yet, for release this coming Tuesday isn't possible, unless maybe we drop everything else we're working on. Depending on priorities, we could push everything else (*everything*) and do our best for this. Please advice (don't mean to sound grumpy, just want to make sure expectations are realistic).
Home page PSD has landed: http://cl.ly/2Z0f1V0F3R361J1R2u2T Steven, this is for three pages: Pages: http://mozilla.org/persona http://mozilla.org/persona/about http://mozilla.org/persona/developer-faq Here are the PSDs: Home http://cl.ly/2Z0f1V0F3R361J1R2u2T About http://cl.ly/0M172y190y470k16133G Dev FAQ http://cl.ly/2V1k2N450I2A0E3h1g0A Monday is a holiday for en-US, but we will be back in action on Tuesday, and excited to review. QA needs these mid-day Wednesday for a release on Thursday. We are anticipating more time needed for QA, since the templates have never been tested before.
This is well under way. Will have pages to show today. The landing page has "Privacy Policy" and "Terms of Service" links at the bottom, do we have URLs for those?
Apologies, yes: Privacy Policy: http://mozilla.org/persona/privacy-policy ---> pull copy from https://browserid.org/privacy http://mozilla.org/persona/terms-of-service https://browserid.org/tos ------ We will do a hard string freeze, shortly after the page are staged, but when staging them could you use this updated copy? Own Your Data Many sign-in systems carry your profile data with them; some even share that info with other sites and social networks. We believe you should control how your personal information is shared, so with Persona ID you only need to provide your email address to get started. Easy for Publishers Persona ID makes things easy for site owners, too. Enabling it on your site only takes a few lines of code and helps build good relationships by providing users with a trusted sign-in option. It’s a win-win!
Summary: [Launch Persona ID] 3 pages on mozilla.org in One Mozilla theme → [Launch Persona ID] 5 pages on mozilla.org in One Mozilla theme
thanks guys, this looks great! nice job winnowing the copy.
The following links on the http://www-dev.allizom.org/b/en-US/persona/about/ page are 404's http://www-dev.allizom.org/en-US/persona/ http://www-dev.allizom.org/en-US/persona/developer-faq/ The Privacy Policy and Terms of Service links do not link to any page The link to Ben Adida's blog post is also blank
The privacy and tos pages are now setup (may take a few minutes for stage site to update. What's the URL for the link on the /developer-faq/ page in this line: "Ben Adida, one of our engineers, describes this here."
Uff, sorry Steven, all the links are in the etherpad, in haste, I didn't remember to bring them over here: http://identity.mozilla.com/post/7669886219/how-browserid-differs-from-openid Other links can be found on this etherpad: https://etherpad.mozilla.org/mozilla-org-persona-pages Thank you for flagging.
Looking good ... some quick fixes: Intro Page: -- Under Try it Yourself Open photo should be OpenPhoto (no space) About Page: -- (headline) Do we caps Identity? If so, change to caps on Intro page also. -- (developers) Build user trust and confidence, providing? doesn't sound right -- (developers) I think the sentence may need invers-ing. Sounds now like users are thinking of passwords and managing their sign-in program. Can we say: Developers don't need to manage their own sign-in program and implement a separate email verification process. And they don't need to ask users to remember another password. In a single step... Also, move the Check our developer site line to the bottom after show your users... DEVELOPER FAQ page: None of us think the download from Github makes sense. Why download a FAQ? and if we offer that, why so prominent? can we make it a button at the end, or a "download" and "print" option with smaller buttons? -- Add link to FAQ on getpersonas. Say for more information on our naming, please see http://blog.mozilla.com/addons/2012/02/02/renaming-personas/ LINKS: At one point we had some reference links to other blogs, etc. Did I miss them somewhere? Or did we kill them? they were: References: User Sovereignty for our Data Lizard Wrangling, Mitchell Baker, January 13, 2012 http://blog.lizardwrangler.com/2012/01/13/user-sovereignty-for-our-data/ Mozilla to Offer New User-Centric Services in 2012 Mozilla Privacy Blog, Ben Adida, January 13, 2012 https://blog.mozilla.com/privacy/2012/01/13/mozilla-to-offer-new-user-centric-services-in-2012/ Mozilla Identity Team blog http://identity.mozilla.com/ If needed, we can add them next week, though they are good references!
Hi, I know maybe I should open a new bug but due the publication is going to be today, is it possible to localize these pages before launching? Where can we find them on svn?
All changes from Comment #9 have been done except for the github Download button. I presume that is a link to the github repository where you can download the source code for the Persona project? I've added the github link to the button. If this is correct, perhaps it should stay?
(In reply to esuter from comment #9) > About Page: > -- (developers) Build user trust and confidence, providing? doesn't sound > right Let's make this "Build user trust and confidence by providing an alternate login that protects their privacy and does not exploit profit from stored data." > -- (developers) I think the sentence may need invers-ing. Sounds now like > users are thinking of passwords and managing their sign-in program. > > Can we say: Developers don't need to manage their own sign-in program and > implement a separate email verification process. And they don't need to ask > users to remember another password. In a single step... Small tweak here: Developers don’t need to manage their own sign-in program and implement a separate email verification process — and they don’t need to ask users to remember another password. Also, on the main page, under the image, the S in "sign in" shouldn't be capitalized. Thanks!
Matej's changes from comment #12 are done.
(In reply to Matej Novak [:matej] from comment #12) > (In reply to esuter from comment #9) > > About Page: > > -- (developers) Build user trust and confidence, providing? doesn't sound > > right > > Let's make this "Build user trust and confidence by providing an alternate > login that protects their privacy and does not exploit profit from stored > data." > > > -- (developers) I think the sentence may need invers-ing. Sounds now like > > users are thinking of passwords and managing their sign-in program. > > > > Can we say: Developers don't need to manage their own sign-in program and > > implement a separate email verification process. And they don't need to ask > > users to remember another password. In a single step... > > Small tweak here: > > Developers don’t need to manage their own sign-in program and implement a > separate email verification process — and they don’t need to ask users to > remember another password. > > > Also, on the main page, under the image, the S in "sign in" shouldn't be > capitalized. > > Thanks! All looks good, thanks for the tweaks. emily
hi -- a few more tweak from Dan Mills... http://www-dev.allizom.org/b/en-US/persona/ "Persona ID allows you to sign in to sites with a single, consistent email address of your choosing." This implies that a person is always tied to a single email address and cannot add multiple addresses to their account. Is the sentence trying to imply that there is only a single email address used everywhere? Is it implying that there are only email addresses used so that usernames are consistent? "Persona ID allows you to sign in to sites using an email address you choose." .... "We believe you should control how your personal information is shared, so with Persona ID you only need to provide your email address to get started." I understand how the first and second half of these sentences tie together, but for the initial read I though "Why tell me about getting started in the same sentence as telling me I control my data?" Could we hint at coming services and users retaining control? I'm really at a loss on how to improve the clarity of this. TRY THIS: "We believe you should control how your personal information is shared. With Persona ID, get started with just your email address; add your profile data later, when and where __you__ think it's appropriate.
Small suggestion to that second copy block: We believe you should control how your personal information is shared. Persona ID lets you get started with just your email address; you can add your profile data later, when and where __you__ think it's appropriate. Also, I've seen it written "PersonaID" before, but on this site it's "Persona ID." Just want to clarify which one is correct.
(In reply to Rubén Martín [:Nukeador] from comment #10) > Hi, > > I know maybe I should open a new bug but due the publication is going to be > today, is it possible to localize these pages before launching? Where can we > find them on svn? Rubén, we won't be localizing this landing page until the content is more mature. This page is a temporary page to help us launch the new Persona product at Mobile World Congress. Stay tuned though, we'll move towards a refined experience that will go through localization later in April/May.
(In reply to Matej Novak [:matej] from comment #16) > Small suggestion to that second copy block: > > We believe you should control how your personal information is shared. > Persona ID lets you get started with just your email address; you can add > your profile data later, when and where __you__ think it's appropriate. > > Also, I've seen it written "PersonaID" before, but on this site it's > "Persona ID." Just want to clarify which one is correct. hi -- It should be Persona ID I think, first because it looks like a Personal+typo otherwise, second because there will be other Persona features, so they would have a space.
Hi -- I still think the download button on the developer page FAQ is awkward... downloading the FAQ or the code? Can we change it to "View the code"? and make the button smaller? it is distracting to me, wouldn't mind to get rid of it altogether, we already have a link to Github on the earlier page, no?
The text updates in the earlier comments have been made, and I've removed the 'download' button from the dev-faq page. There is a link to the project on the About page.
The OpenPhoto link should be: http://current.openphoto.me/ The current link (openphoto.me) doesn't actually use Persona ID!
(In reply to Dan Mills [:thunder] from comment #22) > The OpenPhoto link should be: http://current.openphoto.me/ Fixed.
Pages are live! http://www.mozilla.org/en-US/persona/ http://www.mozilla.org/en-US/persona/about/ http://www.mozilla.org/en-US/persona/developer-faq/ http://www.mozilla.org/en-US/persona/terms-of-service/ http://www.mozilla.org/en-US/persona/privacy-policy/ Closing as resolved. Please file new bugs under websites: www.mozilla.org
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Hey guys. Am reopening this b/c it looks like Dan's comment #22 never made it into the final live site. Can we push this fix first thing in the morning? Thanks!
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
James, the commit with the John is referencing is: https://github.com/mozilla/bedrock/commit/6dba1c025dbbb273b95df518737f6b9ea5cc83f0#apps/persona/templates/persona/persona.html
Assignee: steven → jlong
OS: Mac OS X → All
Hardware: x86 → All
This will be pushed live along with a few other fixes later today or first thing tomorrow.
Checking back in on this...will this be pushed today? I know Dan is anxious to see this edit go live before MWC this weekend.
(In reply to John Slater from comment #28) > Checking back in on this...will this be pushed today? I know Dan is anxious > to see this edit go live before MWC this weekend. Just pinged Jason on IRC to see if he's able to push.
John, this has been pushed, correction from comment 28 is live. Closing resolved/fix. Thank you: Steven, Emily, Raymond, Dan, and Jason!
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Seconding what Chrissie said - thanks all!
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.