672669 - [/features] Streamline Firefox product info

Status: RESOLVED WONTFIX

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

Description

[Laura Forrest]

We currently have overlapping and at times repetitive site content within our Firefox product pages on Mozilla.com. Let's streamline this content down to the bare minimum in order to help users find the information they're looking for faster and easier. 

Proposed changes:

1. Combine the Features, Security, and Performance pages (streamline the content on the Security & Performance pages and move remaining content to Features)
2. Take a hard look at the Features page and remove product content that has been commoditized or is otherwise no longer valid or crucial
3. Keep looking (hard) at Features page and remove any unnecessary copy, and add additional graphics where helpful. Make sure page is showing, not telling.

This may make a good tracking bug to help us first IA as the above touches multiple pages. 

Laura Mesa, John Slater, CB - anything to add before we get going?

Comment 1

[John Slater]

I love the idea behind this and am glad you filed the bug. Having said that, I'm still not totally clear on what the proposed changes mean, exactly, or what the site would look like afterward.

My other quick thoughts:
- do we have data to support these particular choices?
- as we consolidate, it would be ideal if we could repurpose existing blocks of content rather than doing it in a way that requires a lot of rewrites. I realize that may be unavoidable in some cases, but that would save a lot of work (esp for Matej & the localizers).

Comment 2

[Pascal Chevrel:pascalc]

FTR, for locales we only translated the Features page on mozilla.com (about 30 translations) and we are already redirecting /security/ and /performance/ to the security and performance sections of the features page. So this change is good from a l10n POV.

The features page is however extremely long to translate and that's discouraging for many localizers, I think it would be good also to be able to separate the section in subfiles that we could then include together or separately, this way the content could be updated in a modular way I think (and I could assign the maintenance of the different sections to different localizers for the bigger teams). Having these subsections in separate files would also allow creating pages like performance/ or security/ automatically and keep them synced with the main features page if needed.

Comment 3

[Laura Mesa [:lmesa] [:lvmesa]]

I'm currently in the process of writing up a proposal that will hopefully redefine the launch process, with web assets being a key part of that. I don't necessarily have data to support all the changes I want to make, so that's definitely something we should consider before acting.

Comment 4

[Laura Forrest]

(In reply to comment #3)
> I'm currently in the process of writing up a proposal that will hopefully
> redefine the launch process, with web assets being a key part of that. 

Great - once we have those details I think the next actions on this bug in terms of content changes will be more clear, as John aptly wonders in Comment 1. 

> don't necessarily have data to support all the changes I want to make, so
> that's definitely something we should consider before acting.

I'd be happy to take a look at this and email around an overview so the data can help guide these decisions.

Comment 5

[Laura Forrest]

Chrissie kindly volunteered to take this project from here.

Comment 6

[mcbmoz]

Laura,

Would you like to huddle and come up with a few different layout possibilities to help reorganize this information?

Or, do you have next steps I can be helpful with on this bug?

~cb

Comment 7

[Laura Mesa [:lmesa] [:lvmesa]]

Chrissie--

Thanks for this. I'd like to get positioning squared away before we work on copy and what features to keep etc, but no reason why we can't go ahead and talk about layout. Feel free to book me tomorrow or week after next.