Reskin and add a future release word press blog and download page to site to support all channel releases. Add newletter signup to both download and blog page (footer perhaps?).

(In reply to comment #0) > Reskin and add a future release word press blog and download page to site to > support all channel releases. > > Add newletter signup to both download and blog page (footer perhaps?). This should be ready for next website push, which I think is April 21st?

(In reply to comment #1) > > This should be ready for next website push, which I think is April 21st? The code freeze for 2.1 is 4/21. That content would go live 4/26. Laura - can you file separate bugs for the building of the blog and download page? (if there's not one yet).

i will now.

(In reply to comment #2) > (In reply to comment #1) > > > > This should be ready for next website push, which I think is April 21st? > > The code freeze for 2.1 is 4/21. That content would go live 4/26. This schedule may need to be altered and pushed a week back. These pages need to be live with the opening of the beta channel, scheduled for 3 weeks from the 12th. > > Laura - can you file separate bugs for the building of the blog and download > page? (if there's not one yet).

Hey Guys, Just wanted to add that the blog workflow will create individual tag pages for all individual: categories, tags, author names, and archives It might make sense to move this all to .org, given that the site can quickly bloat to several 100 pages, which will all need to be redirected to .org during the scheduled Q2 move. Possibly talk to Steven Garrity, Mike Alexis for ideas on this. If this microsite will become a core part of the Firefox culture, we might be better off making sure to launch under .org -CB

What URL will we use for the blog? If there isn't one already, we could use a policy for URLs for microsites (and for determining what comprises a 'microsite' vs. a collection of pages on the main website). sitename.mozilla.org? sitename.com? Ideally, I could see a site like this being relatively well integrated into the surrounding Channel pages. Something like mozilla.com|org/firefox/channel/updates (or whatever the 'updates' should be called). That said, if the UI, template, style, etc. of the blog is gear more towards it being its own stand-alone site, something like channel-updates.mozilla.org might be more appropriate. Also, is there a single blog for all channel updates (aurora, beta, final-release), or is there a blog for each channel?

(In reply to comment #6) > What URL will we use for the blog? If there isn't one already, we could use a > policy for URLs for microsites (and for determining what comprises a > 'microsite' vs. a collection of pages on the main website). The general rule is that we often use promotional redirects, but the root URL should be on one of our core sites. We actually have a pretty good start at a policy for this: https://wiki.mozilla.org/Websites/Taskforce/Proposals/Domain_Name_Strategy David Boswell is the expert here and may have more to add. > Ideally, I could see a site like this being relatively well integrated into the > surrounding Channel pages. Something like > mozilla.com|org/firefox/channel/updates (or whatever the 'updates' should be > called). a personal +1 for being well-integrated

(In reply to comment #6) > What URL will we use for the blog? If there isn't one already, we could use a > policy for URLs for microsites (and for determining what comprises a > 'microsite' vs. a collection of pages on the main website). > > sitename.mozilla.org? > sitename.com? > > Ideally, I could see a site like this being relatively well integrated into the > surrounding Channel pages. Something like > mozilla.com|org/firefox/channel/updates (or whatever the 'updates' should be > called). > > That said, if the UI, template, style, etc. of the blog is gear more towards it > being its own stand-alone site, something like channel-updates.mozilla.org > might be more appropriate. > > Also, is there a single blog for all channel updates (aurora, beta, > final-release), or is there a blog for each channel? +1 with being integrated. single blog for all channel.

It definitely makes sense to launch this on the .org domain since we shouldn't be releasing any more sites on .com. Since this is using Wordpress it also needs to be on a subdomain (web apps need to be separated on different subdomains) instead of being hosted as part of an existing site (like mozilla.com|org/firefox/channel/updates). So something like channel-updates.mozilla.org that Steven suggested would work. Even if this isn't actually hosted on the www.mozilla.com site though you can still theme it so it looks just like www.mozilla.com (for example, blog.mozilla.com).

Laura M - Any updates on the timing of Phase 2 and its corresponding bugs?

Phase 2 is scheduled for May 17th.

I believe this is all live. Resolving.