Closed Bug 727876 Opened 12 years ago Closed 12 years ago

[Launch B2G] Implement 3 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: sgarrity)

References

(
URL
)

Details

Attachments

(1 file)

Feb 22 landing page mockup (Josh)
389.08 KB, image/jpeg
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 B2G Project 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/b2g
http://mozilla.org/b2g/about
http://mozilla.org/b2g/developer-faq

Deadline: 1.7 milestone (yikes!) 

If you need extra help, please let us know. I've cc'd wenzel & malexis for backup resourcing.
Assignee: nobody → steven
Target Milestone: --- → 1.7
PSDs for all three pages have landed:

http://cl.ly/1A2a392T3T0n151O222B

Note: there might be an image replacement needed

the image for texting shows a non-standard keyboard, a note has been sent to Josh Carpenter on the B2G team for an updated/new image. Josh is now added on this bug.
hi ... looking good!

Tweaks:

Intro. page: 

-- need space between the_development
-- caption 1, phone book: Sample screen menus -- all open for custom design
-- keyboard image swapped for qwerty keyboard
-- caption 2, keyboard/photos:  
Look for all your favorite apps, across your favorite devices

About page:
-- any graphics?
-- Under Open Accessible Standards:  
   "proposing Mozilla B2G" b2g is currently lower case
-- WAIT! There are 2 Open Accessible Standards.  First paragraph is text for Persona.  DELETE.  Use second paragraph

FAQ Page:
-- What size of team?  at end of first paragraph, delete "as well." redundant.
-- Last question, I am a web developer ... need space between deploy_my
-- Last answer, middle: "you may consider adding AN open web app... (says "a")
OK... consensus from the team is to have NO CAPTIONS on the images! 
hope you read this before you add the ones above. :-)

(In reply to esuter from comment #2)
> hi ... looking good!
> 
> Tweaks:
> 
> Intro. page: 
> 
> -- need space between the_development
> -- caption 1, phone book: Sample screen menus -- all open for custom design
> -- keyboard image swapped for qwerty keyboard
> -- caption 2, keyboard/photos:  
> Look for all your favorite apps, across your favorite devices
> 
> About page:
> -- any graphics?
> -- Under Open Accessible Standards:  
>    "proposing Mozilla B2G" b2g is currently lower case
> -- WAIT! There are 2 Open Accessible Standards.  First paragraph is text for
> Persona.  DELETE.  Use second paragraph
> 
> FAQ Page:
> -- What size of team?  at end of first paragraph, delete "as well."
> redundant.
> -- Last question, I am a web developer ... need space between deploy_my
> -- Last answer, middle: "you may consider adding AN open web app... (says
> "a")
Text updates from comments #2 and #3 have been made. Will need more direction for any image changes.
Emily, what's the plan for changing that keyboard graphic? Is Josh working on it?
Hi folks, I will provide updated graphics. Steven, are you handling the HTML/CSS? Can you provide a link to a WIP? I'd like to review so I can determine the right size and format of the replacements. Saving you the Photoshop work.
OK, so last look, there were captions still under the images (and in straight font).  Let's get rid of them entirely (are you waiting for the new images?)
(In reply to esuter from comment #7)
> OK, so last look, there were captions still under the images (and in
> straight font).  Let's get rid of them entirely (are you waiting for the new
> images?)

Those should be gone in a minute.

(In reply to Josh Carpenter from comment #6)
> Hi folks, I will provide updated graphics. Steven, are you handling the
> HTML/CSS? Can you provide a link to a WIP? I'd like to review so I can
> determine the right size and format of the replacements. Saving you the
> Photoshop work.

You can see the page in progress here: http://www-dev.allizom.org/b/en-US/b2g/
If you're working on those images, you can see them in context in the PhotoShop file in comment #1.
Hi everyone, I've updated Lee's original PSD with new graphics. It's uploading to CloudApp over our hotel's brutally slow connection. I'll update with the URL once it's complete.

In the interim, I've uploaded this mockup to show you what to expect.
Thanks Josh!
These updated images have been added to the page. Thanks.
Launched!

https://www.mozilla.org/en-US/b2g/
https://www.mozilla.org/en-US/b2g/about/
https://www.mozilla.org/en-US/b2g/faq/

Closing as resolved. 

For iterations, please open new bugs under websites: component: mozilla.org

We do releases every Tuesday.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Awesome, thanks everyone! 

Re: doing releases every Tuesday, can I interpret that as "we have until this time next week to make pre-MWC revisions"? We'll have more to add by then (other screens, etc), and I'd love to flesh this out a bit. Maybe give this paragraphs some breathing room while we're at it ;)
Hey guys. I hate to say this, but Chris Beard saw these pages for the first time today and wants to make some pretty major changes to the content before MWC.

I expect we'll have that figured out tomorrow, but in the meantime we need to pull these pages down again. Steven, can you take them offline first thing in the morning? 

Apologies - this was unexpected, but it's important.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This was launched without localized versions, but non-en-US users are redirected to /de/b2g, /pl/b2g/, /ru/b2g/ etc. getting 404s.

http://www.mozilla.org/pl/b2g/
It's my understanding that there shouldn't be any locale-specific versions of this page at all...it's meant as an informational page for MWC, with the "official" page (that will be localized) coming later.

Also, how soon can we pull this page down per comment #16?
If it's not going to be localized, http://www.mozilla.org/b2g/ should not redirect to non-existent localized versions. It currently does, so anybody who has e.g. German or Polish before en-US in their Accept-Language, gets a 404.
(In reply to Marek Stępień [:marcoos] from comment #19)
> If it's not going to be localized, http://www.mozilla.org/b2g/ should not
> redirect to non-existent localized versions. It currently does, so anybody
> who has e.g. German or Polish before en-US in their Accept-Language, gets a
> 404.

We are aware of the issue and we can quickly fix it. We are taking down the pages now, but when they are up later that will be fixed.
John, should we just kill the URLs or replace it will some kind of informal page?
Just killing the URLs is fine. We'll have new content that's hopefully should be pretty easy to implement soon.

Again, sorry about this, and thanks for the quick help.
and as Marek said in comment #17, these bedrock based pages will have to fall back to the en-US folder just like the current php site does:

http://www.mozilla.org/b2g/ -> locale detection

http://www.mozilla.org/pl/b2g/ -> page does not exist, ok, but do we have the page in English?

yes, direct user to -> http://www.mozilla.org/en-US/b2g/

Thanks
We are working on pulling down b2g and fixing the l10n redirect. Will be done very soon.
b2g page is taken down. Still fixing the l10n redirect.
l10n problem seems like it should have been caught in QA. James, is this affecting the other pages we launched yesterday or is it isolated to only the b2g group? (stephen?)
This bug happens on all pages on bedrock since they way it's currently set up, it only handles the en-US URLs. PHP doesn't redirect it because it doesn't know the bedrock pages exist.

I've been working with IT on this and we've implemented a quick fix. We will implement a more robust fix in bedrock in the near future.
For example, this URL now works:

https://www.mozilla.org/pt-BR/apps/
Assignee: steven → jlong
I assigned myself to this, but now that I think about it we're blocked on content edits so this is probably back to Steven.
Assignee: jlong → steven
(In reply to mcbmoz from comment #26)
> l10n problem seems like it should have been caught in QA. James, is this
> affecting the other pages we launched yesterday or is it isolated to only
> the b2g group? (stephen?)

If you had taken the time to check staging  before commenting you would have realized that it was working fine on staging.Mind you the setup on staging and production are different and you signed off on the pages yourself in comment #14. Also Stephen doesn't work on mozilla.org bugs so please address any further questions to me. Thank you
(In reply to James Long (:jlongster) from comment #29)
> I assigned myself to this, but now that I think about it we're blocked on
> content edits so this is probably back to Steven.

Thanks James, Steven back over to you, we'll have CBeard changes sometime before tomorrow. The release should happen tomorrow. Sorry I don't have more info than that at this time.
(In reply to raymond [:retornam] from comment #30)
> The setup on staging and production are different ...

I would QA everything on www-dev at this point, IT is working on freeing up servers  to get www.allizom.org working the same, but they are supply blocked. www-dev is our stage right now, and it's exactly the same setup as production.
(In reply to James Long (:jlongster) from comment #32)
> (In reply to raymond [:retornam] from comment #30)
> > The setup on staging and production are different ...
> 
> I would QA everything on www-dev at this point, IT is working on freeing up
> servers  to get www.allizom.org working the same, but they are supply
> blocked. www-dev is our stage right now, and it's exactly the same setup as
> production.

Good advice James. Thanks.
Hi all. Quick update on where things stand:
- we have new copy for all 3 B2G pages, which I'll include below. Lots of little tweaks, but nothing that materially changes the layouts or anything like that.
- Josh is working on new graphics for the landing page. Again, we'll be able to keep the existing layout and just swap the new ones for the old. Aiming to have these by EOD.
- shooting to get this page live again by EOD tomorrow. Thanks again to all for pitching in!

Here's the copy direction, courtesy of Patrick (for each mini-section, the first line is how things are now & the second line is how things should be):

http://www.mozilla.org/en-US/b2g/
--------------------------------

Headline:

"Introducing the Boot to Gecko Project"
to
"Bringing the Open Web to Mobile Devices"

i.
"We're making innovation more accessible and driving the development of new Web standards to bring the power of the Open Web platform to mobile devices."
should read
"We launched the Boot to Gecko project to make innovation more accessible...."

ii.
"Boot to Gecko is an implementation of new Web standards that brings the power of the open Web to mobile devices, "
should read
"The Boot to Gecko project is an implementation of new Web standards that aims to bring the power of the Open Web to mobile devices, "


iv.
"Today's proprietary mobile platforms are closely tied to specific devices and their development is tightly controlled by a single vendors."
-remove this paragraph.


v.
"Using HTML5 and B2G's standards-based APIs"
"Using HTML5 and the Mozilla-proposed standard APIs"

vi.
"Consumers who use devices with an open mobile platform can easily access and download their own content regardless of which operating system it uses."
"Consumers who use devices based on the Open Web platform can easily access and download their own content regardless of which operating system they use."


http://www.mozilla.org/en-US/b2g/about/
----------------------------------------

i.
"About Boot to Gecko"
"About the project"

ii.
"Boot to Gecko (B2G) is our open source, Web-based operating system for mobile devices. It is the framework for the Open Web device platform introduced at Mobile World Congress in February 2012.
"Launched in 2011, the Boot to Gecko project will fully enable the Web as the platform for mobile devices.  At Mobile World Congress in February 2012 we announced our initial development partners, and provided a demo of a prototype."


iii.
"The B2G architecture eliminates the need..."
"The project's proposed architecture eliminates the need..."

http://www.mozilla.org/en-US/b2g/faq/
--------------------------------

i.
"Boot to Gecko (B2G) is an implementation of new web standards that bring the power of the open web to mobile devices, unencumbered by the rules and restrictions of existing proprietary platforms."

The project is an implementation of new Web standards that bring the power of the Open Web to mobile devices, unencumbered by the rules and restrictions of existing proprietary platforms.

ii.
"What does B2G mean for your relationships with Apple, Google and Microsoft?"
"What does the project mean for your relationships with Apple, Google and Microsoft?"


iii.
"...while the B2G project ramps up."
"while the project ramps up."

iv.
"Do you see B2G as co-existing with other mobile OSes, or competing with them?

Ideally, the technology pioneered or refined in B2G will make its way into all mobile browsers, so that enhanced open Web applications can be great regardless of operating system or device. We look forward to working with other OS and browser developers on standards activities and even implementations."

"Do you see this project as competing with other mobile operating systems?"

We believe the Web is the platform. Ideally, the technology pioneered or refined in the Boot to Gecko project will make its way into all mobile browsers, so that enhanced Web applications can be great regardless of operating system or device. We look forward to working with other OS and browser developers on standards activities and even implementations."


v.
"Are OEMs interested in B2G?

Currently B2G is still a project without a firm product schedule. We are briefing silicon vendors (ODMs), OEMs and carriers on B2G, and we will announce a product schedule and launch partners once we reach that stage."

"Are OEMs interested in the project?

Currently Boot To Gecko is still a project without a firm product schedule. We are briefing silicon vendors (ODMs), OEMs and carriers, and we will announce a product schedule and launch partners once we reach that stage."


vi.
'We will port B2G to a reference platform once we have identified the ODM/OEM that will ship the first B2G device. "

"We will port to a reference platform once we have identified the ODM/OEM that will ship the first device based on the project."



vii.
"Is B2G just introducing yet another platform for devs to code for?

No, B2G is definitely not designed to be another platform. It's a project to extend what developers can do with the Web..."

"Is this going to be yet another platform for developers to code for?

No: the project is extending what developers can do with the Web..."


viii.
"We don't want B2G to lead to applications that only run atop B2G, or only run in Firefox. "
"We don't want this work to lead to applications that only run atop one platform, or only run in Firefox. "

ix.
"B2G is designed to build on the success of the Web,"
"The Boot to Gecko project is designed to build on the success of the Web"

x.
"What does B2G offer mobile users that HTML5 doesn't?

B2G offers mobile users all the power of HTML5, extended with device capabilities like Bluetooth and SMS, a richer capability model for interaction with the filesystem, and a way to tie native HTML5 apps together. The intent is very much that B2G lead to improved capabilities for the Web platform, not that it replace HTML5 or related tech in any way. Many of these new capabilities will also make sense in desktop browsers, and we look forward to seeing them there as well."

"What does the Boot to Gecko project offer mobile users that HTML5 doesn't?

The project offers mobile users all the power of HTML5, extended with device capabilities like Bluetooth and SMS, a richer capability model for interaction with the filesystem, and a way to tie native HTML5 apps together. The intent is to lead to improved capabilities for the Web platform, not to replace HTML5 or related technology in any way. Many of these new capabilities will also make sense in desktop browsers, and we look forward to seeing them there as well."


xi.
"I am a web developer. How do I deploy my web application to the B2G platform?"

"I am a web developer. How will I deploy my web application to this platform?"

xii.
"However, the install API is not complete yet on the B2G platform as of Jan 2012."
"However, the install API is not complete yet as of February 2012."
And here are the assets from Josh - one new hero image + detail images that are screenshot only (no phone illustration). I'm hoping this is an easy swap, but if you need anything else Josh is copied on this bug and can help.

http://cl.ly/0g2K2I0Q252k1p0Q2b1b

I think we're all set with the assets now...thanks!!
OK, thanks John. Steven will work on this tonight/tomorrow morning ET. James will coordinate the release for Friday with IT.

Can you let the stakeholders know that we are on track to push tomorrow.
Will do, thanks all.

One other note: once we get this staged, I'd like to send it around to the stakeholders to ensure it's exactly right before we push live. Would like to avoid another emergency pulldown situation! So, let me know when that's available and I'll circulate for a quick review.
All of these content and image updates are done.

For the main feature phone image on the landing page, I did a bit of photoshop hackery to put it on an angle like the original image - it fits into the area much more easily this way.

Now that the images are just plain screenshots rather than phone illustrations, they are just sharp rectangular images - doesn't look too bad, I don't think.

It might take a few minutes for the stage site to update, but when it does: 
http://www-dev.allizom.org/b/en-US/b2g/

I'll check for any updates/changes here on the bug tomorrow first thing in the (East Coast) morning.
OK, finally getting a look.  Some edits for clarification:

Opening paragraph is a run-in, mixed sentence... change to:

We launched the Boot to Gecko project to bring the power of the Open Web platform to mobile devices.  We're making innovation more accessible by driving the development of new Web standards.
(In reply to esuter from comment #39)
> OK, finally getting a look.  Some edits for clarification:

These edits have been applied.


And that edit in turn makes the third paragraph a repetition of the first two.

Place change:
"The Boot to Gecko project is an implementation of new Web standards that aims to bring the power of the Open Web to mobile devices, unencumbered by the rules and restrictions of existing proprietary platforms."

to:
"The project will produce an implementation of these new Web standards to free mobile platforms from the encumbrances of the rules and restrictions of existing proprietary platforms."

there are no more run-ins after that and the rest of the page looks great to me.  


Are the FAQ and About pages staged too?
(In reply to Patrick Finch from comment #41)
> And that edit in turn makes the third paragraph a repetition of the first
> two.

This change has been made too.

> Are the FAQ and About pages staged too?

Yes, the links between pages don't work on stage, because of a development quirk that requires a /b/ in the URLs. You can add the /b/ to any broken links, but here are the working URLs:

http://www-dev.allizom.org/b/en-US/b2g/about/
http://www-dev.allizom.org/b/en-US/b2g/faq/
small change on this page:

http://www-dev.allizom.org/b/en-US/b2g/about/

"As with all Mozilla projects, B2G is based entirely on open standards and the source code is open and accessible to all. Where open standards are missing (including telephony, SMS, camera, bluetooth, USB and NFC), we're working with standards bodies and other vendors to create them."

change to

"As with all Mozilla projects, the Boot to Gecko project is based entirely on open standards and the source code is open and accessible to all. Where open standards are missing (including telephony, SMS, camera, bluetooth, USB and NFC), we're working with standards bodies and other vendors to create them."


(i.e. swap B2G with "the Boot to Gecko project"
final suggested changes from me:

http://www-dev.allizom.org/b/en-US/b2g/faq/


1. 
Right Hand Nav Link, 

"B2G Project"

replace With 

"Boot to Gecko Project"

(same comment applies to http://www-dev.allizom.org/b/en-US/b2g/about/ )


2. 
"More than 20 engineers were working full-time on B2G-specific parts of the system (telephony, messaging, system-level phone integration). In addition to Mozilla contributors, engineers from carrier partners are working jointly with us on the project."

change to 

"More than 20 engineers were working full-time on specific parts of the system (telephony, messaging, system-level phone integration).  In addition, Mozilla contributors and engineers from carrier partners are working jointly with us on the project."

(remove B2G, and change second sentence for sense).


3.
"We are leaning heavily on the existing Gecko and Firefox mobile work and the team of hundreds of engineers building those products. 95% of the code in B2G is shared with Firefox."

change to
 
"We are also leaning heavily on the existing Gecko and Firefox mobile work and the team of hundreds of engineers building those products. 95% of the code in the Boot to Gecko project is shared with Firefox."


(insert "also" and replace B2G)



4.
"we don’t want a competitive advantage for Mozilla, we want a competitive advantage for the Web."

(sounds disingenuous) replace with 

"we don’t seek a competitive advantage for Mozilla, we seek a competitive advantage for the Web."
Adding Jason to coordinate the push with today. Also can be reached on IRC as "jason" and email jthomas@mozilla.com
This last round of text updates has been made.

Jason, can you ping me on irc (sgarrity) when you get online today?
final suggested edits from cbeard on 

http://www-dev.allizom.org/b/en-US/b2g/

ORIGINAL:
We launched the Boot to Gecko project to bring the power of the Open Web platform to mobile devices. We're making innovation more accessible by driving the development of new Web standards.

NEW:
We launched the Boot to Gecko project to enable the Open Web as a platform for mobile devices.  

ORIGINAL:
Developers no longer need to learn and develop against platform-specific native APIs. Using HTML5 and the Mozilla-proposed standard APIs, developers everywhere can create amazing experiences and apps that are accessible from any Web device.

NEW:
Using HTML5 and the new Mozilla-proposed standard APIs, developers everywhere will be able to create amazing experiences and apps. Developers will no longer need to learn and develop against platform-specific native APIs.


ORIGINAL:
OEMs and operators can provide content and services across their entire device portfolio, regardless of OS. They can customize user experiences, manage app distribution and retain customer attention, loyalty and billing relationships.

NEW:
OEMs and operators will be able to provide content and services across their entire device portfolio, regardless of OS. And they will be able to customize user experiences, manage app distribution and retain customer attention, loyalty and billing relationships.


ORIGINAL:
Consumers who use devices based on the Open Web platform can easily access and download their own content regardless of which operating system they use.

NEW:
Consumers who use devices based on the Open Web platform will be able to easily access and download their own content regardless of which operating system they use.
Ok, I now have the *final* changes to this page. Big thanks to Steven for riding on the roller coaster with us here.

Drum roll please...

- we'd like to use this as the new hero image (the underlying code shown is more accurate): http://cl.ly/3Q2U0d46470b0G2k1o09
- Patrick's text edits from comment #48 still apply, with one amendment to the first paragraph. It should now read:
"We launched the Boot to Gecko project to enable the Open Web as a platform for mobile devices. We're making innovation possible by driving the development of new Web standards."
- please do a general find & replace to swap the word "carriers" for "operators"
- in the Consumer Freedom section please change "operating system" to "OS"
- lastly, we need to add another section to the bottom of the page. The section can be modeled after the bottom content box on http://www.mozilla.org/en-US/persona/. The section should be titled "More Information" and should basically be a list of links. Those links include:
About the project (http://www-dev.allizom.org/b/en-US/b2g/about/)
FAQ (http://www-dev.allizom.org/b/en-US/b2g/faq/)
Brendan Eich on the Mobile Web API Evolution (http://brendaneich.com/2012/02/mobile-web-api-evolution/)

(final note: we apparently need to add additional links to this section on Sunday night...will share those details when I get them, but that shouldn't block any of these other updates.)

Thanks!!
All updates have been made and are on the stage site.
Thanks Steven. Let me circulate for one final (quick) review and I'll give you the green light asap.
Ok, green light - please push live as soon as you're able.

Thanks everyone!!
Pushed to production.
Thanks all - hugely appreciated!
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
(In reply to raymond [:retornam] from comment #54)
> verified fixed 
> 
> https://www.mozilla.org/en-US/b2g/
> https://www.mozilla.org/en-US/b2g/faq/
> https://www.mozilla.org/en-US/b2g/about/
> 
> 
> Also made sure that other locales redirect to this page example
> https://www.mozilla.org/de/b2g/ --> https://www.mozilla.org/en-US/b2g/

Thank you for tackling the redirect problem. We learned a lot from this first fast-paced release on Bedrock. These iterations and bugs help us prepare for a smooth migration and relaunch this March.
    <li><a href="http://www-dev.allizom.org/b/en-US/b2g/about/">About the project</a></li>
    <li><a href="http://www-dev.allizom.org/b/en-US/b2g/faq/">FAQ</a></li>
    <li><a href="http://brendaneich.com/2012/02/mobile-web-api-evolution/">Brendan Eich on the Mobile Web API Evolution</a></li>

These should link to the real site, not www-dev.allizom... :)
Reopening per comment 57.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Stephen can you coordinate with Jason Thomas (jason on IRC) to do another push?
One note: I'm waiting to find out details, but there's a possibility we'll need to do another push on Sunday night to update the page with some announcement links. If that's the case, I think it would be fine to wait until then to fix this.

(That said, if it's easy to fix now then let's just do it.)
(In reply to John Slater from comment #60)
> One note: I'm waiting to find out details, but there's a possibility we'll
> need to do another push on Sunday night to update the page with some
> announcement links. If that's the case, I think it would be fine to wait
> until then to fix this.
> 
> (That said, if it's easy to fix now then let's just do it.)

John, that means that we'll need to have someone from WebDev, QA and someone from IT on call. Can you arrange that? Will there be a phone call or a time period you would want all three to be online?
(In reply to mcbmoz from comment #59)
> Stephen can you coordinate with Jason Thomas (jason on IRC) to do another
> push?

Anyone can do this, but I'm in a phone screen, so no, sorry.  Also, we need a fix to push, first.  James/Raymond?
(In reply to Stephen Donner [:stephend] from comment #62)
> (In reply to mcbmoz from comment #59)
> > Stephen can you coordinate with Jason Thomas (jason on IRC) to do another
> > push?
> 
> Anyone can do this, but I'm in a phone screen, so no, sorry.  Also, we need
> a fix to push, first.  James/Raymond?

James is on a plane to Mountain View, so he's not available. Steven is offline for the weekend. 

Fred, can you help?
(In reply to mcbmoz from comment #61)

> John, that means that we'll need to have someone from WebDev, QA and someone
> from IT on call. Can you arrange that? Will there be a phone call or a time
> period you would want all three to be online?

Yep, definitely. I just got off the phone with Leslie and it looks like we'll be able to do the push on Monday morning instead. I'll coordinate with Steven, Raymond and Jason on those details.
(In reply to Stephen Donner [:stephend] from comment #62)
> (In reply to mcbmoz from comment #59)
> > Stephen can you coordinate with Jason Thomas (jason on IRC) to do another
> > push?
> 
> Anyone can do this, but I'm in a phone screen, so no, sorry.  Also, we need
> a fix to push, first.  James/Raymond?

James is currently on a plane to SF. I can do this
Thanks Raymond.
(In reply to Marek Stępień [:marcoos] from comment #67)
> Made a pull request on github.
> https://github.com/mozilla/bedrock/pull/13

THanks Marek, Raymond has this covered per comment 65.
(In reply to mcbmoz from comment #68)
> (In reply to Marek Stępień [:marcoos] from comment #67)
> > Made a pull request on github.
> > https://github.com/mozilla/bedrock/pull/13
> 
> THanks Marek, Raymond has this covered per comment 65.

I am working with Wenzel and Jason in #www to get this fixed and pushed to production. I'll update when the push is done.
I fixed the URLs (re: comment 57).

https://github.com/mozilla/bedrock/commit/815f654

Steven, James: Please use Django's standard URL reversal for that purpose. I can explain more later.
Links are now fixed. Thanks all.

<li><a href="/en-US/b2g/about/">About the project</a></li> 
-->https://www.mozilla.org/en-US/b2g/about

<li><a href="/en-US/b2g/faq/">FAQ</a></li>
 ---> https://www.mozilla.org/en-US/b2g/faq/
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
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.

Attachment

General

Creator:
Created:
Updated:
Size: