Closed Bug 663467 Opened 13 years ago Closed 13 years ago

[Rapid Release] Channel Page - Redesign to fit new channel branding

Categories

(Marketing :: Design, task)

Product:
Marketing
Component:
Design
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: gjimenez, Assigned: tshahian)

References

(
URL
)

Details

hi tara, 

target completion date for this project is by end of july but wanted to get the conversation going here. 
looking for recommendation on how we can make this page aligned to the new channel branding (wordmarks, dark background for aurora?) 

i would also like to add a bit more details  differentiating aurora and beta and copy on what they can expect in each channel and instructions on how they can provide feedback. we talk about providing feedback in the page but not really giving instructions on how to do it. 

im not sure if all that would fit in this one page or whether each channel should have their own page. ideally i'd like to keep it here if there's a nice way to execute that without cluttering the page. 

we can brainstorm a bit more on this but would like to kickstart the process 

thanks!
Blocks: 663470
Thanks Grace.  cc-ing Ty, I'd like him to work on this with Sean's guidance. 

I think one way we could approach is to design the page so that you have the ability to collapse data.  That way we have a quick dashboard presenting all the channels, but then there's a way to click for more information on each without having to send folks to an entirely new page.  Basically different states of the same pod, tabs, or something similar.
URL: http://www.mozilla.com/en-US/firefox/...
I wonder if there's an opportunity to do some A/B testing on this. I think the collapsing data solution Tara suggests in comment 1 could be really useful and elegant, but if we're trying to get more users on Aurora, would there be any value in giving Aurora its own page? I think that would make it feel more unique from Beta, too. That would leave Beta and Final Release together on one page, which I still think makes sense.

My biggest concern with the channels page is that I'm not sure it's an intuitive place for people to go (ie. I heard a lot of people in the early days of Aurora assuming they could find it at aurora.mozilla.org, before we had that redirecting).

I think they could still work on the same page, but as part of this process, we should probably also be thinking about how best to drive people to these channels, be it on one page or several.
This seems like it's getting pretty complicated. I agree with A/B testing if we have the resources to make it work. This would also be a good opportunity to pull in one of the UX designers from webdev if they have free cycles.

Before we get too far ahead of ourselves, though, do we know for sure that this page isn't working? Would be good to check the data to learn where the problems/successes are before we start changing too much.
(In reply to comment #3)
> This seems like it's getting pretty complicated. I agree with A/B testing if
> we have the resources to make it work. This would also be a good opportunity
> to pull in one of the UX designers from webdev if they have free cycles.
> 
> Before we get too far ahead of ourselves, though, do we know for sure that
> this page isn't working? Would be good to check the data to learn where the
> problems/successes are before we start changing too much.

From the site analytics perspective this page seems healthy. It's hard to get exact conversion numbers but it looks like around 65% of people end up downloading one of these versions. About 2% go to the homepage and 1.5% go to the features page presumably seeking more info. 

It seems like the need here is to add more product features for the early adopters who want it. To keep this page, and the content on moz.com to a manageable amount of pages I suggest adding some sort of progressive info UI to accompany this, as Tara recommends, or have a simple tabbed structure within the same URL. 

It really depends on the amount of additional info/graphics needed.
Good info, thanks Laura. Grace, let's discuss - I'd like to get a better sense of what the goals are and how we can achieve them without blowing everything up.
Let me know how I can help here.  Otherwise, I'll wait for "word" from someone on next steps.   Thanks.
Hey Grace, this isn't urgent, right? I don't see any deadlines on this bug and it seems like there are still some outstanding issues for discussion.  I don't think you and Slater had a chance to follow up on this.  If you don't mind, lets hold off until next week when Slater is back so we can talk in person and figure out next steps.
Hey Grace, fair to say we can close this ?
Ping?  I'd like to close this.
we actually have new updates on new channel redesign. can we just keep this one? or would be more than happy to close this and reopen one?
Well, if it's an update (and not a redesign) we should open a new bug, please. That would be a different conversation, and it just keeps us better organized that way.
it's a redesign request. 
would be more than happy to close this and restart. 

thanks!
oh, sorry, did't read that right.  why don't you just ping me separately and let me know what you need, and we can figure out the bugs.  To me, it's always nice to close out old threads and start fresh.
Closing.  I think it's just cleaner to start fresh here for the new request :)  Thanks Grace.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.