Closed Bug 708025 Opened 14 years ago Closed 14 years ago

[Mozilla Spaces] Design + Copy for Launch Site

Categories

(Marketing :: Copy, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: christine.brodigan, Assigned: matej)

References

Details

Attachments

(4 files)

Opening this bug to gather and polish launch content for Mozilla Spaces landing page. Assigning to Amie. Needed: Mozilla Spaces statement about the project, site, purpose Office phone Office address Office email/contact information Mountain View, California, USA San Francisco, California, USA Toronto, Ontario, Canada Vancouver, British Columbia, Canada Berlin, Germany London, United Kingdom Paris, France Auckland, New Zealand Beijing, China Tokyo, Japan Taipei, Taiwan Remote or Satellite
Thanks Chrissie. Would be great to attache the wireframe here, so that we can track copy/content by the different blocks, by number.
Blocks: 706561
Hey guys. Just wanted to say that I think much of the copy content can actually be added in the webdev process. It makes more sense than for Lee to update the design for each location. So, I suggest that he does a template for the hover state, and then we have the copy content per locale added in webdev (location names, address, etc). Don't think Matej needs to do any editing for content like address, phone#, etc. Here are the different content pieces I see, and thoughts on copy/design. Please review and let me know your thoughts, Amie. et al: >HEADER: (#1) "Welcome to Mozilla Spaces" Is this final? >LOCATIONS: (#2) Have the list per CB's comment. If you have a special blurb per locale (as it shows in the wireframe), please list those out so Matej can take a look. This piece will go straight to implementation vs. design updates. >SUB-HEAD/ABOUT: (#3) I think this piece could possibly work well underneath the header in section #1. Depends on how big the map is, the fold, and how much copy we'll have for the "about" section. Amie, please draft your desired blurb so Matej can edit/polish. >Section #4 :) missing/skipped! woops. >EMAIL SIGN UP: (#5) Seems like we'll need a short blurb for email signups, right? >FOOTER: (#6) What links are we placing here? I suggest putting the social media bits near each other vs. on opposite sides of the page.
Attaching the first mockup for this page. I created the map styles consistent to current Community maps on Mozilla.org site (ie: http://www.mozilla.org/contribute/local/europe.html) All content is FPO.
Alternate version - About Mozilla Spaces Statement below global map, as in CB's original wireframe
Looks awesome. Thanks Lee. I like both versions, though I personally prefer the first one... I think it would be nice to share ea bit about the project at the top before leading into the map (since it consumes much of the page). Few nits: * I'd suggest changing the color of those little tick marks / flags, since green is also used on the community map and we want to use a diff. color to denote Spaces. * I'd probably remove the "about spaces" header, since we have the header and the copy would just be sub-head about Spaces. we don't need to restate what that blurb is :) Otherwise, Looks great to me and I think it works well as a phase 1 bare boned announcement page to launch in Q4. THANKS LEE.
> * I'd suggest changing the color of those little tick marks / flags, since > green is also used on the community map and we want to use a diff. color to > denote Spaces. Thanks, Tara. Good catch on the colors of the location pins. From Monique's source file, she had FPO'd Mozilla Spaces with the green pins so I picked up from that. But looking at the Mozilla.org site, we're using both orange and green for Sites and Offices respectively http://cl.ly/1Z1E01271U0l3g3o0k0J I'll make the Mozilla Spaces a new color.
Adding property addresses for hover states for launch: Mountain View 650 Castro Street Suite 300 Mountain View, CA, 94041-2021 USA Auckland Level 7 5 Short St Newmarket Auckland 1023 New Zealand Beijing Mozilla Online Ltd. International Club Office Tower 800A 21 Jian Guo Men Wai Avenue Chaoyang District, Beijing 100020 China Paris 28 boulevard Poissonnière 75009 Paris, France San Francisco 2 Harrison St San Francisco CA 94105 Tokyo Kojimachi GN Yasuda Bldg., 4F 3-6-5 Kojimachi, Chiyoda-ku Tokyo, 102-0083, Japan Toronto 366 Adelaide St W, Suite 500 Toronto, Ontario Canada, M5V 1R9 Vancouver 128 West Hastings Street. Suite 210 Vancouver BC V6B 1G8
Updated with slight tweaks for consistency: Mountain View 650 Castro Street Suite 300 Mountain View, California 94041-2021 USA Auckland Level 7 5 Short Street Newmarket Auckland 1023 New Zealand Beijing Mozilla Online Ltd. International Club Office Tower 800A 21 Jian Guo Men Wai Avenue Chaoyang District, Beijing 100020 China Paris 28 boulevard Poissonnière 75009 Paris France San Francisco 2 Harrison Street San Francisco, California 94105 USA Tokyo Kojimachi GN Yasuda Bldg., 4F 3-6-5 Kojimachi, Chiyoda-ku Tokyo, 102-0083 Japan Toronto 366 Adelaide Street West Suite 500 Toronto, Ontario M5V 1R9 Canada Vancouver 128 West Hastings Street Suite 210 Vancouver, British Columbia V6B 1G8 Canada
Thanks Lee! I think you said you'd keep them the same color per your convo with Boswell, right? Either way, thanks for the great design. Everything looks good, I'm going to close out the design bug. The copy can catch up later and go straight to webdev.
That's correct - we're going to stick with the green pins, and I believe David will rename "Mozilla Offices" to "Mozilla Spaces". Here's the PSD: http://intothefuzz.com/leetom/Mozilla%20Spaces/Web/mozspaces_landing.psd
(Thanks Lee) All: quick update: * Talked to Amie, Matej, and Lee. * Amie would like to have more content on the page before going live. * New content is basically added copy. * This copy will be: - single line mission statement at the top, below the header. - slightly beefier blurb below the map "about" the Spaces program. - additional copy / bullet point format qualifying Spaces and what to expect Impact of the content is expected to be minimal (from a design / webdev perspective). it'll just expand that section (what used to be #3) to accommodate the added copy. And Lee may need to adjust the mockup to accommodate the new copy, and suggest bullet point styling. * Matej is to craft the copy today/tomorrow. * Lee will then take a look and update the mockup if needed. * We close and move to webdev. ------------- Amie would also like to add some links to "get involved" etc. She's listing those out, but the plan is to insert these in simple navigation format / in the footer. ------------- Amie, please let me know if the above is not correct. As noted on the call, we really need to have the content finalized asap - by end of day tomorrow if not sooner so that we can update the design if needed and stay on track to push this to production on Monday. The scope we discussed seemed reasonable to me, so I don't want to go beyond that at this stage. But I think having the additional content you mentioned will be great.
Thanks, Tara. The above is correct, and captures what we discussed on the call. The content is finished, I am re-working the content on the copy etherpad to organize + map better to the wire frames. Matej will then take one more pass today/tomorrow and we'll be good to go from a copy perspective. I will also add the url's for the footer navigation to the etherpad. Thanks all, for your hard work. The site is looking awesome thus far!
Summary: [Mozilla Spaces] Copy Bug for Launch Content → [Mozilla Spaces] Design + Copy for Launch Site
Amie, could you please post the etherpad if/when you are done? Matej, let us know how things are going. I doubt you've had a chance to look at the copy yet, but wanted to make sure you've at least had a chance to look at the drafted copy Amie added so we can discuss as needed.
The etherpad with copy is the same as the one listed in the creative brief. I made modifications there yesterday, the content is complete. Re-posting here for those following along: https://etherpad.mozilla.org/moz-spaces-copy Spoke with Matej this morning and he will review + edit today. I've flagged a few things for him based on the meeting he and I had yesterday.
I've got the etherpad edited and looking good. Have a look and let me know what you think.
Thanks Amie and Matej. Lee will take it form here and weave this into the design layout to see how things shake out. It's a bit more copy than I was anticipating, but I'm sure we can make it work. It's value-add copy so it'll only make the page better in the end. Stay tuned...
Attaching mockup with new content here. What do you think?
love it. Great work !! Done to me, Amie, et al ?
(In reply to Tara from comment #19) > love it. Great work !! > > Done to me, Amie, et al ? Wow, what a wonderful page! +1 to Tara's comment 19
Absolutely fabulous! Awesome work - thanks to all! Lets send it on over to web dev... :-)
I think the only thing we're missing is contact info (name + email) for each space, but we can add that in implementation. Nice work, everyone. Go team... uh, let's say global!
Ok. WOHOO! Now, next steps: * Design / Copy - Done. Will close this bug. * Need to file implementation bug, if not already filed. * Please cc me, matej and lee on the implementation bug as well so we can chime in as needed. Otherwise, looking to CB, MikeA, Amie and others to move this forward from here! * Amie, please post link to PSD file and post to implementation bug. * Amie, please post/share etherpad of final copy content with webdev on implementation bug. They can update/add the copy in implementation, as Matej mentioned. * Amie, please send a fancy bottle of red wine to me, matej, and lee tom :) * Thanks all.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
just fyi, some of the phone numbers you have don't actually work yet (San Francisco's 415 DID for instance).
We won't be putting phone numbers on the contact page. It will be an email contact for the Q4 launch, so each hover menu has a consistent contact field. That's the contact information I'm adding to the copy etherpad and sending over to webdev. In Q1 we can add in phone numbers where applicable, and when they are reliable.
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: FIXED → ---
Assignee: atyrrel → Mnovak
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: