648002 - Redesign Nightly.Mozilla.Org

Status: RESOLVED FIXED

(Websites :: Other, defect, P2)

Description

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

For phase 2, redesign page to fit general Mozilla Firefox site design

Also for phase 2, add link to Channel selection page (www.mozilla.com/firefox/channel)

Comment 1

[Tara (musingt)]

Thanks Laura.  Could you also add the deadline to hand off design files please?  Thanks.

Comment 2

[David Boswell]

In addition to updating the look of this site, I think it makes sense to add some content about what people can do with the nightly after installing it (running tests, filing bugs, etc.).

This information about what to do with the nightly was previously presented to people after they installed and started things with the Minefield start page at

http://www.mozilla.org/projects/minefield/

I believe this page has been replaced in the nightlies with the about:home page so we need to provide this information to users somewhere else and it makes sense to provide at least some of it on nightly.mozilla.org.

I just talked to Laura Mesa about this and she thought it made sense too.  If people agree, we can create some content to add to the site.  Maybe it would be as simple as 'After downloading the nightly, learn more about how you can test things to make the next version of Firefox better' with a link to a page with all the details.

Comment 3

[Tara (musingt)]

Hey guys

Lets sync up in person to go over what you're thinking in terms of the redesign.  Is this more of a light update with new skin? or restructuring the layout and adding more copy/content.  Would be great to catch up in person and figure out those details. Also, if you can let me know the design handoff date that would be helpful in terms of planning.... thanks.

Comment 4

[David Boswell]

I'm happy to talk about this in person.  I can't speak for Laura, but from previous discussions it seems like the scope of this might be:

* Reskin the site to fit in more with the the Firefox product site.

* Revisit content to make sure we're providing the right information (this might just be a minor addition with a link to testing information).

* Add an application picker (like in the top right part of AMO) to allow mobile, Thunderbird and others have a nightly download page on the site (see bug 627075 for example).

Comment 5

[Tara (musingt)]

Thanks David.  Could either you or Laura set something up for us to chat in person early next week?  This all makes sense, but would be great to just walk through it real quickly in person.  Thanks.

Comment 6

[David Boswell]

Sure.  I just set something up.

Comment 7

[Robert Sayre]

(In reply to comment #4)
> I'm happy to talk about this in person.  I can't speak for Laura, but from
> previous discussions it seems like the scope of this might be:
> 
> * Reskin the site to fit in more with the the Firefox product site.
> 
> * Revisit content to make sure we're providing the right information (this
> might just be a minor addition with a link to testing information).
> 
> * Add an application picker (like in the top right part of AMO) to allow
> mobile, Thunderbird and others have a nightly download page on the site (see
> bug 627075 for example).

I don't agree with these at all (I made the nightly.mozilla.org site).

They might be OK, but I asked about reskinning this page to match the Nightly branding without changing much else. The reason for this limited scope is that I'd rather have decisions about other content on the page be data-driven. Once the blocking bug 646943 is fixed, we'll be in a position to evaluate the impact of each change on the download funnel. Then I think adding information, reskinning, and an application picker might be fine ideas.

Comment 8

[David Boswell]

It would be great to talk through all of this together.  Robert, it looks like you're out all next week though?

> They might be OK, but I asked about reskinning this page to match the Nightly
> branding without changing much else.

That's fine with me.

> The reason for this limited scope is that
> I'd rather have decisions about other content on the page be data-driven.

That sounds fine too.  We can get WebTrends tracking up right now if we wanted.  If you copy the WebTrends block from the bottom of any www.mozilla.org page and add it to the nightly.mozilla.org page I can set this up in WebTrends.  It's the block between

<!-- START OF SmartSource Data Collector TAG -->
<!-- END OF SmartSource Data Collector TAG -->

Comment 9

[Tara (musingt)]

Hey guys

per our discussion, lets just do a quick mockup of what the redesigned version of this page would look like, and then figure out the best way to move forward.  Here's what we discussed:

* Nightly logo + header
* Short blurb explaining the page
* The different channels
* Two additional links, one to the new release channels page, and another (can you remind me what that one was?)
* below the fold: three blocks of content pulled from the FR page:  Getting Started, Useful Add-ons, and Other resources.
* We'll have the mozilla tab in the upper right
* We'll swap out the background with the new one.

Simple / crisp design.  A light update.  Nothing drastic.  Meanwhile we can pull data for the current page and see what insights we gain from that.

I'm going to ask Lee to help with this.

Comment 10

[Tara (musingt)]

Oh, and a channel picker.

Comment 11

[David Boswell]

I agree that having a mockup to look at and give feedback on is a good next step that can be done in parallel with gathering stats about usage of the current site.

> * Two additional links, one to the new release channels page, and another (can
> you remind me what that one was?)

IIRC, the other link was to the FTP server where people can find other versions of the nightly.

> The different channels

I think this is referencing the download links for the different versions of the nightly instead of references to Aurora, Beta, etc.  We had also talked about seeing if making those links look more clickable made sense (perhaps by styling them link buttons).

> Oh, and a channel picker.

To clarify, this would be an application picker to allow other apps (such as Fennec) to host nightly download pages on the site.

Comment 12

[Tara (musingt)]

Thanks for the clarification!  all sounds good.

Comment 13

[Robert Sayre]

(In reply to comment #9)
> Hey guys
> 
> per our discussion

I'm concerned that there's some confusion about the purpose of this site. Its purpose is to get more users on the nightly channel. That's it. It is not a destination site with tons of options on the homepage--it is supposed to be the end of the line. So, any change that decreases its effectiveness at driving downloads should be rejected. Let's not use subjective arguments here, just a/b test a change and see what happens.



>  Here's what we discussed:
> 
> * Nightly logo + header
> * Short blurb explaining the page

Already there, so OK.

> * The different channels

Not OK. This is not the purpose of this page. This page is for developers.

> * Two additional links, one to the new release channels page, and another (can
> you remind me what that one was?)

Sounds like this could be behind the "more stuff" link.

> * below the fold: three blocks of content pulled from the FR page:  Getting
> Started, Useful Add-ons, and Other resources.

Same here.

> Application picker 

Again, not the purpose of this page. The purpose of this page is to drive downloads of the Nightly app. Users looking for some other applications are better served by other pages with the same small number of options.

Comment 14

[David Boswell]

> I'm concerned that there's some confusion about the purpose of this site. Its
> purpose is to get more users on the nightly channel. That's it. It is not a
> destination site with tons of options on the homepage--it is supposed to be 
> the end of the line.

We want people to do something with the nightlies (test them, fix bugs in them, etc.) beyond just downloading them, so I think it is helpful to think of this page as one of the steps in getting people to contribute to Mozilla through this channel.

Having some information about what to do with the nightly after downloading it is useful, especially now with the recent change to the nightly start page that used to show information about how people could test the nightly and instead now shows about:home.

There still is a nightly First Run page that has this information, but it only shows up on first run compared to the old Minefield page that showed up on each start-up.

I see the questions people have about how to get involved with Mozilla that are coming through the Get Involved pages on mozilla.org and it is not at all clear to people what to do with nightlies.  Adding some context to the download page about what the nightlies are for can help address this.

> Let's not use subjective arguments here, just a/b
> test a change and see what happens.

That sounds great.  As mentioned in comment #8, I can get that set up as soon as the WebTrends tag is added to the page.

>> * The different channels
>
> Not OK. This is not the purpose of this page. This page is for developers.

I don't think this is what Tara meant in her comments.  I believe this is referencing the download links.  We thought it might increase click through rate to have those links appear more clickable by making them into buttons.

> Again, not the purpose of this page. The purpose of this page is to drive
> downloads of the Nightly app. Users looking for some other applications are
> better served by other pages with the same small number of options.

What we are suggesting here is taken directly from the information architecture of the AMO site.  The AMO site is a shared resource for different Mozilla projects to serve add-ons.  Other Mozilla projects, like Fennec, want to use the nightly site as well and this would allow them to do that.

We can talk with the AMO team to get their thoughts about how distracting that application picker is and we can also mock things up to see how distracting that would be in this case.

Comment 15

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

(In reply to comment #13)
> (In reply to comment #9)
> > Hey guys
> > 
> > per our discussion
> 
> I'm concerned that there's some confusion about the purpose of this site. Its
> purpose is to get more users on the nightly channel. That's it. It is not a
> destination site with tons of options on the homepage--it is supposed to be the
> end of the line. So, any change that decreases its effectiveness at driving
> downloads should be rejected. Let's not use subjective arguments here, just a/b
> test a change and see what happens.

Rob, who else has access to nightly.mozilla.org code? We want to add the tagging in comment 8 but can't seem to find anyone who has access. 

We also will go ahead with the design of the page as Tara detailed, serving some people the old page and some people the new design.  We'll make a decision on how to proceed depending on the results of that test. 

> 
> 
> 
> >  Here's what we discussed:
> > 
> > * Nightly logo + header
> > * Short blurb explaining the page
> 
> Already there, so OK.

We have the old moz.com template and the current Firefox logo.  We need to update this page with the new moz.com template and new nightly logo regardless of how the a/b tests go.

I also agree wuth all of boswell's comments in comment 14.

Comment 16

[Tara (musingt)]

(In reply to comment #14)

> >> * The different channels
> >
> > Not OK. This is not the purpose of this page. This page is for developers.
> 
> I don't think this is what Tara meant in her comments.  I believe this is
> referencing the download links.  We thought it might increase click through
> rate to have those links appear more clickable by making them into buttons.


Correct, sorry about that.  By "channels", I simply meant the 5 download links currently there. we'll follow up with a mockup asap.  I think having a visual of what we're describing will help the discussion quite a bit.  The intention isn't to clutter up the page at all, but to add a few additional pieces of information to give more context, and for a better experience overall - which, of course, we can test as we go.

Comment 17

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

After further discussion with creative about resources, we've decided that this project is not a high priority for now and may be revisited.  

Rob, please feel free to add tracking code from comment 8 to the page so we can have that data to analyze when we revisit this.

Comment 18

[Robert Sayre]

I don't think it's a good idea to do WONTFiX this bug, since we do actually need to fix the page. The layout has gotten all broken, and the logos are wrong. We also need to get web trends running in the bug this one depends on. However, the page doesn't have to look great, so I'll just do it myself.

Comment 19

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

Rob, let's wait until you return to discuss what needs to happen face to face before you get going on the design so we can see how we can help--just to clarify, we definitely want to take this on, but this isn't the highest priority project we have right now.

Comment 20

[John Slater]

(In reply to comment #19)
> Rob, let's wait until you return to discuss what needs to happen face to face
> before you get going on the design so we can see how we can help--just to
> clarify, we definitely want to take this on, but this isn't the highest
> priority project we have right now.

+1

Comment 21

[Robert Sayre]

Sounds good.

Comment 22

[Grace Jimenez :grace]

hi rob. please let know in what size would you need the logos? do you just want the logos by itself or with the wordmark (see attachment)

Comment 23

[Grace Jimenez :grace]

Attachment: beta logo with wordmark

Comment 24

[Grace Jimenez :grace]

Attachment: aurora logo

Comment 25

[John Slater]

(In reply to comment #22)
> hi rob. please let know in what size would you need the logos? do you just want
> the logos by itself or with the wordmark (see attachment)

Just so I'm clear - the plan is still what Laura said in comment #19, right? Talking it over before deciding what to do next, that is. Just want to make sure that we're not asking or expecting Rob to do any front end work here...would much rather figure things out as a group and then follow the usual process.

Comment 26

[Grace Jimenez :grace]

hi slater. i shouldve provided an update first. 

Phase 1 - update logos 
Phase 2 - update background and make the page prettier ;)  

From my understanding, Rob is the only one who has access to the site and would update the phase 1 and phase 2 proposal. we still need to sync up and talk about phase 2, where we need to provide the design to Rob to update.

Rob, are you able to provide the access to us and get webdev to help us update the page? If not, are we good with the proposal mentioned above?

thanks!

Comment 27

[Grace Jimenez :grace]

hi john, if you can please provide the nightly logo for the page that would be great. Rob will update the page once we have the logo. thanks!

Comment 28

[David Boswell]

Re comment #27, you can use the logo used on the Nightly first run page if you want.

http://www.mozilla.org/images/projects/nightly_logo.jpg

Comment 29

[John Slater]

Thanks DBos. Rob, will the file in comment #28 work for you?

Comment 30

[Sean Martell]

If you need a biiiig one: http://mozilla.seanmartell.com/engagement/fx-nightly-800x800.png

:)

Comment 31

[Robert Sayre]

(In reply to comment #29)
> Thanks DBos. Rob, will the file in comment #28 work for you?

Yup, thanks.

Comment 32

[Tara (musingt)]

Hey guys,  just catching up on bugs (and also had a quick chat with Robert).  What's the next step here?  Anything that we (meaning I/creative team) need to do to keep things moving?  Please let me know.

Comment 33

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

Grace will follow up here.

Comment 34

[Grace Jimenez :grace]

Hi Tara, 

There are 2 phases for this bug. 

Phase 1: Rob will update page with the nightly logo provided in comment 30.

Phase 2: Design Update using the current mozilla.com background (stay tuned. finalizing design details)

thanks.

Comment 35

[Grace Jimenez :grace]

Hi Rob, 

Any updates on timing for phase 1 completion?

From our conversation last week, you mentioned that you will help us out with adding mobile builds as well. 

Adding details here regarding  adding mobile in nightly.mozilla.org: 
Add a mobile button on top of the desktop nightly.mozilla.org page similar to the button in this page: http://www.mozilla.com/en-US/mobile/home/
The mobile button will link to a new nightly.mozilla.org page dedicated for mobile. This page will have the fennec logo. (see attachment) and the fennec builds (link provided below)
builds listed in this URL: http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mobile-trunk/
Fennec for Android: http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android-r7/fennec-6.0a1.multi.eabi-arm.apk
Wiki on Fennec Nightly Builds (for your reference): https://wiki.mozilla.org/Mobile/Platforms/Android#Download_Fennec_Nightly_Builds

thanks!

Comment 36

[Grace Jimenez :grace]

Attachment: Fennec Logo

Comment 37

[John Slater]

When did we decide to use the Fennec logo here? I thought that one had been retired completely.

Comment 38

[Grace Jimenez :grace]

this was the logo provided by caitlin. unless we have a new one?

Comment 39

[Tara (musingt)]

Shouldn't the nightly for mobile be the same logo as the one for desktop, with a distinction that it's "mobile"? similar to how we do it with other channels?  Just a thought.  I don't think using the Fennec logo is the right thing here... I too thought that we had retired that mark.

Comment 40

[Caitlin Looney]

Fennec nightly builds are called and visually branded as Fennec. This has been the case since day 1. "Fennec" represents the ongoing development project whereas "Firefox" is the official product name. 

I think we can discuss a nightly brand change for mobile to align with desktop on every front, but I'd like to discuss this with Thomas as our nightly testers are familiar with Fennec. 

What's the logo for desktop nightly?

Comment 41

[Tara (musingt)]

Desktop nightly: https://bug646896.bugzilla.mozilla.org/attachment.cgi?id=525604
Though the wordmark is likely to change.  That's the logo.

Comment 42

[Caitlin Looney]

I personally think this would be wise to do (as we'd like to use same Aurora branding eventually too), but will need to discuss this with Thomas. I am not sure what the product implications will be for changing this (and when we can actually make this change), but I think it would be smart to make the change now before their is more large scale effort to grow this channel. Thanks for bringing this to my attention.

Comment 43

[Caitlin Looney]

Doesn't sound like changing the logo would be too difficult (Thomas is looking into it). We'll need to discuss this with RelEng about changing the package name -- we currently call it Fennec. Stay tuned.

Comment 44

[Mark Finkle (:mfinkle) (use needinfo?)]

Does this mean we would be changing the name of the mobile nightly from 'Fennec' to 'Nightly'? I'm not sure that would be a good thing. We have a lot of name recognition with 'Fennec' and zero with 'Nightly'

I worry about the confusion this would create.

Also, have we decided to promote the mobile 'Aurora' builds?

Comment 45

[Caitlin Looney]

Hey Mark,

We've decided to not promote aurora until we have enough folks on nightly/beta to garner a fourth channel. (I do have questions on the best way to capture interested folks, however.)

As far as Fennec goes, we should discuss this, but we currently only have 160 on nightly, 60 of which are Mozillians. We have a goal of building this channel to 20k by end of year, so if we do want to align with desktop (and adopt nightly and aurora messaging and branding) we should do so now before we put efforts around growing our lists.

Comment 46

[John Slater]

Sorry to weigh in late here, but from a brand perspective we should have the mobile product act as much like the desktop product as possible. In this case, that means having a similar icon set throughout...we've already made the call that mobile and desktop should both use the regular Firefox icon (since they are both Firefox), so it follows that they should have the same nightly logo as well.

I have a lot of personal attachment to the Fennec logo, but now that we've reached this stage with the product it's time to graduate to the full Firefox treatment.

Comment 47

[Grace Jimenez :grace]

Hi Rob, 

Just a follow up from our conversation today, can you please provide an update on the timing? Do you think it would be possible to have it by end of week? thanks!

Comment 48

[Robert Sayre]

Attachment: screenshot

the firefox logo had a fade built into the old site them, so I just took the old background out. we have to change it anyway.

also cleaned up the order of the builds (they got messed up when we got rid of OSX-64 builds)

Comment 49

[Robert Sayre]

Attachment: temporarily update the nightly.mozilla.org site with new branding

Comment 50

[Tara (musingt)]

Thanks Rob.  Would it be too much for us to squeeze in the subtle blue line texture into the background here?  Feels a touch too plain to me.  Would love to add that in if we can, I can send you the PSD or PNG file.  Sorry if it's out of scope for this bug. Let me know

Comment 51

[Robert Sayre]

(In reply to comment #50)
> Thanks Rob.  Would it be too much for us to squeeze in the subtle blue line
> texture into the background here?  Feels a touch too plain to me.  Would
> love to add that in if we can, I can send you the PSD or PNG file.  Sorry if
> it's out of scope for this bug. Let me know

That's fine. I'll need nightly art that can layer over it, right? The one I have has a white background.

Comment 52

[Tara (musingt)]

I see. You need a transparent PNG of the logo, I thought you had that, sorry.  Let me look into it.

Comment 53

[Tara (musingt)]

Hi, I'm back:

* Here is the link to the nightly PNG: http://mozilla.seanmartell.com/engagement/fx-nightly-800x800.png

* Attached is the background blue.

* Also, could you update the font so it's Georgia?  I believe the font you're using here is outdated (from the old mozilla.com)

Thanks.

Comment 54

[Tara (musingt)]

Attachment: blue gradient background.

Comment 55

[Michael Morgan [:morgamic]]

Comment on attachment 532484 [details] [diff] [review]
temporarily update the nightly.mozilla.org site with new branding

WFM!

Comment 56

[tofumatt [:tofumatt]]

Attachment: Patch file for change with new bg/logo/layout based on sayrer's patch

Patch file for sayrer to commit; I'm waiting on commit access.

Comment 57

[tofumatt [:tofumatt]]

Attachment: nightly logo to replace firefox.png

Comment 58

[Robert Sayre]

Comment on attachment 534011 [details] [diff] [review]
Patch file for change with new bg/logo/layout based on sayrer's patch

I pushed this with a few tweaks that Matt and I went over.

Comment 59

[Robert Sayre]

Filed bug 658605 for deployment. Let' s close this messy thread and do other work elsewhere. RESOLVED FIXED. :)

Comment 60

[Tara (musingt)]

Thanks guys!  appreciate the edits.  We'll tackle further polish and edits in the Phase II bug.

Comment 61

[Grace Jimenez :grace]

hi matthew, we also needed to add the mobile builds to the nightly.mozilla.org page. would you be able to assist us with that? 

http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mobile-trunk/

Comment 62

[Grace Jimenez :grace]

also adding laura forrest and mike alexis

Comment 63

[tofumatt [:tofumatt]]

I'm happy to help out with the Nightly page some more. Did you want all of those builds added? I'd love to have icons for each one to least keep the look of the platform download sections consistent (at least until this page gets redesigned to fit the dark, Nightly branding).

Do we have icons for this kind of stuff already? I could maybe cook something up, but I'm no pixel artist; best leave that kind of stuff to the pros :-)

Please let me know about Android and Maemo icons; I can get to work on updating the pull script/page to include these builds.

Comment 64

[Grace Jimenez :grace]

Attachment: Mobile Builds and Icons

Comment 65

[Grace Jimenez :grace]

Attachment: nightly.mozilla.org with mobile builds

the layout should stay the same as the current page, but if we can please create a section for mobile that would be great! thanks Matthew!

Comment 66

[Damon Sicore (:damons)]

When will this be done?

Comment 67

[tofumatt [:tofumatt]]

I'm currently finishing up some work on Firefox Input 4.1 release which is due to push tomorrow. I'll get to it after that. I'm going to say _very_ conservatively Tuesday, if that's OK. If I can get to it before then I certainly will.

Would that be cool with everyone?

Comment 68

[Grace Jimenez :grace]

(In reply to comment #67)
> I'm currently finishing up some work on Firefox Input 4.1 release which is
> due to push tomorrow. I'll get to it after that. I'm going to say _very_
> conservatively Tuesday, if that's OK. If I can get to it before then I
> certainly will.
> 
> Would that be cool with everyone?

Thanks Matthew! Tuesday should be fine. But soon is always good of course ;) let me know if you need any additional info. thanks!

Comment 69

[tofumatt [:tofumatt]]

Hi all:

I had to redo the scraper script a bit to get this working the way we wanted. It should allow us to be a bit more flexible with the way we setup pages, though it would up being a bit more verbose...

It's up at https://gist.github.com/0d22ab43994e5f536acb. Would someone mind giving it a quick review? I want to make sure what I did won't mess anything up, though it produces output similar to the old scrape.py.

The output it produces:

http://files.kicksass.ca/nightly/index.html
http://files.kicksass.ca/nightly/mobile.html
http://files.kicksass.ca/nightly/js-preview.html

Comment 70

[Robert Sayre]

r=sayrer fwiw.

It looks like this will work fine. It probably doesn't go far enough, though. The next steps should be getting analytics on the links, and creating a mobile view. I had planned to use CSS media queries to make the Android build focused for smaller screens. The other option is doing UA sniffing to present the most appropriate option as the main choice, but that's quite a complexity increase. Up to you. :)

Comment 71

[Grace Jimenez :grace]

(In reply to comment #69)
> Hi all:
> 
> I had to redo the scraper script a bit to get this working the way we
> wanted. It should allow us to be a bit more flexible with the way we setup
> pages, though it would up being a bit more verbose...
> 
> It's up at https://gist.github.com/0d22ab43994e5f536acb. Would someone mind
> giving it a quick review? I want to make sure what I did won't mess anything
> up, though it produces output similar to the old scrape.py.
> 
> The output it produces:
> 
> http://files.kicksass.ca/nightly/index.html
- can we change "other nightly builds" to "Mobile Nightly Builds" 
- either move "Firefox JS Preview Builds" on top of the "Mobile Nightly Builds" section or just take it out? I'm not clear what the goal is with the JS Preview Build link?


> http://files.kicksass.ca/nightly/mobile.html
- can we create a section here. 
"Mobile Nightly Builds"
Android
Maemo

"Mobile Nightly Builds in Desktop"
Windows 
Mac 
Linux

> http://files.kicksass.ca/nightly/js-preview.html

thanks!

Comment 72

[Grace Jimenez :grace]

(In reply to comment #70)
> r=sayrer fwiw.
> 
> It looks like this will work fine. It probably doesn't go far enough,
> though. The next steps should be getting analytics on the links, and
> creating a mobile view. I had planned to use CSS media queries to make the
> Android build focused for smaller screens. The other option is doing UA
> sniffing to present the most appropriate option as the main choice, but
> that's quite a complexity increase. Up to you. :)

thanks rob. we still have to do phase 2 of this page which is to redesign this page to fit nightly branding. this is our temporary solution to provide a nightly page for mobile. we also have a bug open to design and develop a mobile friendly nightly page: bug 663227

Comment 73

[tofumatt [:tofumatt]]

Hi Grace,

I don't want to let the mobile builds slip anymore so if this is to your liking I'll push it live:

http://files.kicksass.ca/nightly-with-mobile/index.html
http://files.kicksass.ca/nightly-with-mobile/mobile.html

I'll look into adding some analytics to the page, as we discussed on IRC. I'd like to have this stuff live before that though, so if those pages look good I'll put them live today.

Comment 74

[Caitlin Looney]

These look good. Let's get these puppies live! Thank you.

Comment 75

[Grace Jimenez :grace]

hi matt. i know you are still waiting for your account to push this page. let me know if this can go out today or if you need help pushing it live. thanks matt!!!

Comment 76

[tofumatt [:tofumatt]]

Attachment: Android Icon for mobile-patch.diff

Comment 77

[tofumatt [:tofumatt]]

Attachment: Maemo Icon for mobile-patch.diff

Comment 78

[tofumatt [:tofumatt]]

Attachment: Diff on my changes for the nightly scraper/css

Comment 79

[tofumatt [:tofumatt]]

I'm still talking to IT to make sure I can push to the repo. If any of the devs on this thread know what level access I need to push to hg.mozilla.org/webtools/nightly/ that would be handy.

I've attached a diff of my changes and the image files needed as well. If any of the devs with access can push this up that'd be awesome.

I'm tofumatt on IRC if you have any questions.

Comment 80

[Grace Jimenez :grace]

thanks matt. morgamic or mike alexis can you help? thanks!

Comment 81

[tofumatt [:tofumatt]]

Commit access granted; code is pushed to hg. Thanks for your patience on this one, all!

http://hg.mozilla.org/webtools/nightly/rev/945826c08d46

I'm marking this as resolved, but I understand there's more to work on (see sayrer's comment above). I'd love to help out, but let's file separate bugs for new ideas related to nightly.mozilla.org, if that's cool with everyone.

Comment 82

[Grace Jimenez :grace]

hi matt. for some reason, im still not seeing nightly.mozilla.org updated?

Comment 83

[tofumatt [:tofumatt]]

Hey Grace,

Sorry, it slipped my mind that a separate deploy request is required. I submitted one and things should be pushed when IT gets to it. My bad!

Comment 84

[Grace Jimenez :grace]

(In reply to comment #83)
> Hey Grace,
> 
> Sorry, it slipped my mind that a separate deploy request is required. I
> submitted one and things should be pushed when IT gets to it. My bad!

thanks. please keep me posted when it goes live.

Comment 85

[Grace Jimenez :grace]

still not working :(

Comment 86

[Grace Jimenez :grace]

still not updated =(

Comment 87

[:Gavin Sharp [email: [e-mail]]]

Bug 665690 is the deployment bug. It's not FIXED yet.

Comment 88

[tofumatt [:tofumatt]]

Updated; new site is live!

Comment 89

[Grace Jimenez :grace]

(In reply to comment #88)
> Updated; new site is live!

looks great! thanks matt!

Comment 90

[raymond [:retornam] (inactive)]

verified fixed http://nightly.mozilla.org/

Comment 91

[John Slater]

Hey guys. I hate to say it, but it looks like there are some inconsistencies between the mockup and the live site that we should fix before resolving this bug:

1) the wordmark is done in live text vs using the actual logo file. very important to maintain consistency with our brand marks here.
2) differences in the styling of the boxes in the main area
3) the page stretches out beyond the constraints set in the template 
4) the footer seems to have been rebuilt rather than using the existing one, and there are some inconsistencies there as well.
5) background on the live site seems darker

Sean threw together the two pages for a side-by-side comparison here: http://cl.ly/2l3j0l3B0o3B3X2B1T3v/o (Ty's mockup on the left, live site on the right)

When do you think we can get this updated?

Thanks-

Comment 92

[John Slater]

Oh, also, Ty's mockup uses a different wordmark, but the best one to use is the one from this bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=682175

(We made a slight change to the font and size of the existing one.)

Comment 93

[tofumatt [:tofumatt]]

I'm currently at DjangoCon and then the All-Hands. I won't be able to tackle these differences in the immediate future, but I can speak to a few things now:

1. The wordmark is using the fonts in the mockup so far as I can tell. Could we verify exactly which fonts and what sizes they ought be in this bug? I can certainly change those if I can get the new fonts.

2. This should be an easy-ish fix. Thanks for that.

3. I'm sorry, but I'm not sure what you mean by this. Is the page wider than you'd like or longer than you'd like?

4. The footer I used is part of webdev's mozilla header/footer templates that we are using across mozilla.org sites. The links/structure inside should be common across all of our mozilla sites. There may be differences from the mockup but if those footer links ought be different, they should be changed across mozilla.org sites and we should bring that up as a separate issue with webdev.

If that's the case I'd be more than happy to change the footer links upstream and apply those changes here as well.

5. It seems the nightly background is a bit lower on the live site compared to the mockup. I can fix that one easily. That's likely what's causing things to look so dark.

Like I said, it may take me well over a week to find the time to do this as I'm currently travelling and such, but thanks for letting me know about these issues.

Comment 94

[Sean Martell]

Hey hey, responses:

1. The wordmark should not be live text. It should be the graphic with registered mark. "Firefox Nightly" is a wordmark we have made specifically and should be a PNG.

2. awesome.

3. the header stretches to the full width of the browser window. It should have a max width similar to the mozilla.org/firefox templates.

4. The footer isn't the same as mozilla.org/firefox, which is our main site. The blues are not the same, the newsletter section is different (link vs form box), and the fonts/spacing are off. Also, it has some odd dark vertical lines on either side of it in the lighter blue area.

5. awesome.

Thanks!

Comment 95

[Sean Martell]

any word on this getting updated?  Still not resolved at http://nightly.mozilla.org/

Comment 96

[John Slater]

(In reply to Sean Martell from comment #95)
> any word on this getting updated?  Still not resolved at
> http://nightly.mozilla.org/

+1000

Comment 97

[tofumatt [:tofumatt]]

Hey Sean and John,

I'm working on packaging this up for Tuesday right now. Sorry for the delay; what time I wasn't away this month I've been spending on the Mozillians directory project; now that it's shipped I can get to this. Most of the issues have been addressed in my development version.

I'm getting the footer link situation sorted; most of the layout/branding issues I have fixed.

I'll update the bug when things are updated. By the way: thanks for your clarifications Sean; they helped out a lot. I appreciate your eye for detail!

Comment 98

[tofumatt [:tofumatt]]

Hey Sean,

Alright, I think I've got everything right. I'd like you to take a look at it before I commit my changes and push it live, but I think I've addressed all your points...

EXCEPT: The newsletter form on mozilla.org has some special JS stuff that I'll talk to my fellow webdevs about cribbing but for now will link to the newsletter page, if that's alright. But I'll bring up cribbing that HTML/JS from them; it's just a bit odd to do with the minified/random JS on mozilla.org.

Comment 99

[Laura Forrest]

(In reply to Matthew Riley MacPherson [:tofumatt] from comment #98)
> Hey Sean,
> 
> Alright, I think I've got everything right. I'd like you to take a look at
> it before I commit my changes and push it live, but I think I've addressed
> all your points...
> 
> EXCEPT: The newsletter form on mozilla.org has some special JS stuff that
> I'll talk to my fellow webdevs about cribbing but for now will link to the
> newsletter page, if that's alright. But I'll bring up cribbing that HTML/JS
> from them; it's just a bit odd to do with the minified/random JS on
> mozilla.org.

Thanks Matthew! James Long should be able to answer all your newsletter questions, he's been doing a lot of work on that lately.

Comment 100

[tofumatt [:tofumatt]]

Yeah, he was my likely contact point. I'll ping him about it, but no reason to let all these other fixes go until we get that sorted.

Comment 101

[Sean Martell]

+1 here!  Thanks!

Comment 102

[tofumatt [:tofumatt]]

Awesome; committed in https://github.com/mozilla/nocturnal/commit/88c5d8f87567fb0d065574f488cd92385b842684

I'll file an IT bug to push!