Closed Bug 763665 Opened 12 years ago Closed 12 years ago

[NativeUI GA] implement changes to mozilla.org/projects

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: jslater, Assigned: rik)

References

Details

(Whiteboard: r=107198 b=trunk) 

Implementation bug for the content changes at bug 763663. Note that I'm not putting this as a launch blocker b/c it's ok if it goes live after 6/26 (but not much after...should still be in Q2).
Assignee: nobody → steven
OS: Mac OS X → All
Hardware: x86 → All
I think the implementation of the hover/focus overlay is pretty clear, but this doesn't work in on a touch-based device. Is there a plan for that situation?
One possible solution would be to keep the hover/focus overlay, but on devices were touch events are supported, tap once to reveal the overlay, and a second time to follow the link.
I did have a version of the page which relies less on the hover/overlay. The copy would be place below the title, and the project title would then be hyperlinked too. 

Here's the example page: 
https://bugzilla.mozilla.org/attachment.cgi?id=637582
I like the option in comment #4 - good compromise. Let's go with that!
Here is the updated PSD for the hover-less option:
https://www.dropbox.com/s/mkmsryyd7zj1h0t/Moz_Products_Projects_noHoverState.psd
This is up on the dev site for review/qa: http://www-dev.allizom.org/en-US/projects/

Keep in mind that it is a responsive layout.
Status: NEW → ASSIGNED
Keywords: qawanted
Target Milestone: --- → 3.2
Hey Steven, this is looking great. Just a couple of copy things from me (Ty will comment about layout separately).

• We've still got the old headline at the top and we're missing the subhead copy entirely.

• Some of the project descriptions are old (Firefox and Pancake, for example). Can you make sure to grab the latest stuff from the PSD?

Thanks!
Awesome work Steven! 

Before we do a push live, can we add in the "Reserved" banner to fill the empty spot beside XUL Runner, and move Webmaker to the 3rd spot, 2nd row in Products please.

Thanks
Matej and Ty's changes have been implemented. The Reserved banner is updated with Ty's changes now too: http://www-dev.allizom.org/b/en-US/projects/
Hmm, what about the other projects currently listed on the mozilla.org/projects page, like SeaMonkey, Lightning, etc.? Will they not be listed anywhere at all in the future?
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #12)
> Hmm, what about the other projects currently listed on the
> mozilla.org/projects page, like SeaMonkey, Lightning, etc.? Will they not be
> listed anywhere at all in the future?

Can we get a confirmation on what the plan/solution is for the LACK of the community projects here BEFORE this goes live?

In my opinion pushing out all community projects from mozilla.org/projects might as well go back to being mozilla.com/products.
Blocks: 768507
Steven - the page looks great, thank you.

Kairo - you're absolutely right. I meant to communicate something to this effect earlier and forgot to, so thank you for the reminder.

Here's my recommendation:
- at the bottom of the new projects page, add a line that reads "See even _more awesome software_ based on Mozilla technologies." and link to http://www.mozilla.org/projects/mozilla-based.html
- add SeaMonkey, Sunbird/Lightning and Camino to the top of that projects page (and update said page with the Sandstone theme...will file a separate bug for that as discussed in IRC)

Thanks!
(In reply to John Slater from comment #15)
> Here's my recommendation:

... For what it is worth, I'm a bit disheartened with the added level of indirection this is for SeaMonkey/Lightning given our much tighter integration with Mozilla and the platform than many of those other projects on that page.

That said, if we are unable to integrate in a reasonable way into this page's redesign I can't argue too deeply against the plan, as it is surely better than the alternative of no place for "us" :-)
Thanks for the feedback...I'm certainly happy to keep discussing this, as I do want to find the appropriate spot for SeaMonkey and the other products being discussed. That said, this page is moving toward being more of a 'products' page (since we have more products) so I'm not sure it really belongs here. Ultimately I think the best solution is to come up with a great page for community projects...what we have now is ok, but could certainly be done better. I'd welcome any input on that, for sure.

Also, adding to comment #15 - I just filed bug 771268.
(In reply to John Slater from comment #17)
> Also, adding to comment #15 - I just filed bug 771268.

Thanks.

As a side-note (and that's what comment #14 hints at), in the old times, we had mozilla.org/products and mozilla.org/projects for some time, until the former were broken off into their completely separate websites where mozilla.org was seen as the community portal, so it only needed a reorganize /projects then. Looks like we're getting back to needing both. ;-)
Yes, the new page is looking very much like a "products" page so perhaps should be called / labelled that. I would welcome having a both projects and products again. Very much full circle!
Those are very good points, yes.

Steven, as part of this let's also change the header nav on mozilla.org to products, and the URL as well. Let me know if that should be spun off into another bug.
(In reply to John Slater from comment #20)
> Steven, as part of this let's also change the header nav on mozilla.org to
> products, and the URL as well. Let me know if that should be spun off into
> another bug.

Sure, should the header nav link change to Products to? Should we redirect /projects to /products for now?
(In reply to Steven Garrity from comment #21)
> (In reply to John Slater from comment #20)
> > Steven, as part of this let's also change the header nav on mozilla.org to
> > products, and the URL as well. Let me know if that should be spun off into
> > another bug.
> 
> Sure, should the header nav link change to Products to? Should we redirect
> /projects to /products for now?

Is it weird, then, that we're linking to a page called "Products" and the first category on that page is also called "Products?"

If we're calling all these things products now, would it make more sense to lose the categories and top nav on this page and just keep everything together?

Or should we just rename the first grouping to something else?
(In reply to Steven Garrity from comment #21)
> Sure, should the header nav link change to Products to? Should we redirect
> /projects to /products for now?
Yes, that sounds right - thanks.

> Is it weird, then, that we're linking to a page called "Products" and the
> first category on that page is also called "Products?"
> 
> If we're calling all these things products now, would it make more sense to
> lose the categories and top nav on this page and just keep everything
> together?
> 
> Or should we just rename the first grouping to something else?
Overall I like the categories and would like to keep them. I don't think it's the end of the world if we have a page called products and a category called products, but I'm open to suggestions if you (or anyone else) has any. Any ideas?
(In reply to John Slater from comment #23)
> (In reply to Steven Garrity from comment #21)
> > Sure, should the header nav link change to Products to? Should we redirect
> > /projects to /products for now?
> Yes, that sounds right - thanks.
> 
> > Is it weird, then, that we're linking to a page called "Products" and the
> > first category on that page is also called "Products?"
> > 
> > If we're calling all these things products now, would it make more sense to
> > lose the categories and top nav on this page and just keep everything
> > together?
> > 
> > Or should we just rename the first grouping to something else?
> Overall I like the categories and would like to keep them. I don't think
> it's the end of the world if we have a page called products and a category
> called products, but I'm open to suggestions if you (or anyone else) has
> any. Any ideas?

I'm OK with it if you are. I think products is the best fit there.
A new pull request with the move from /projects to /products and the new mozilla-based page: https://github.com/mozilla/bedrock/pull/242
(In reply to Steven Garrity from comment #25)
> A new pull request with the move from /projects to /products and the new
> mozilla-based page: https://github.com/mozilla/bedrock/pull/242

Nit: I don't want a 404 at /projects can you do a[n] (.htaccess?) redirect for now, to *either* /products, or the identified "more..." page
(In reply to Justin Wood (:Callek) from comment #26)
> Nit: I don't want a 404 at /projects can you do a[n] (.htaccess?) redirect
> for now, to *either* /products, or the identified "more..." page

Yes, we will redirect /projects to /products for now - I just have to wait until Monday to get that setup.
This is now setup on the dev site, though we have to clean up some old redirects from /products and setup a new redirect from /projects to /products.

The .htaccess file for the PHP site was updated in trunk in r107198. That commit will have to go live with the this page.
Whiteboard: r=107198 b=trunk
Thanks all. Will this be going live next Tuesday then?
CC'ing Anthony for help with this push. The PHP .htaccess change (r107198 in trunk) will have to be synced with the bedrock push.
Actually, this is just cleanup. This will become dead code after the push. So this can go out any time after the push.
Assignee: steven → anthony
Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/c33ff4c0d3dd772397a14690a4f27713d5483934
Initial setup of new projects page for Bug 763665

https://github.com/mozilla/bedrock/commit/2cab3af825afc6faf156c0eff6fdb463c278c910
Initial implementation of responsive projects page
Bug 763665 - [NativeUI GA] implement changes to mozilla.org/projects

https://github.com/mozilla/bedrock/commit/f57e0c4f87488806b761ca7c003228d7eef0e695
Initial setup of new projects page for Bug 763665

https://github.com/mozilla/bedrock/commit/fda1ce4aae0948e7c9670178cc21ec6d2fa56db6
Initial implementation of responsive projects page
Bug 763665 - [NativeUI GA] implement changes to mozilla.org/projects

https://github.com/mozilla/bedrock/commit/b9320d8679d163bb6dfdffe5cc15ae77a9cd4481
Redirect /projects to /products for Bug 763665
(In reply to Anthony Ricaud (:rik) from comment #31)
> Actually, this is just cleanup. This will become dead code after the push.
> So this can go out any time after the push.

Anthony, are you sure? Revision r107198 gets rid of the products -> projects redirect and the products -> /firefox redirect.

If these are left in, won't the PHP htaccess be redirect from products->projects and the Bedrock redirect going from projects->products, creating a loop?
You're right, I pushed this to stage with r107518 to fix the redirection problem I was seeing.
I have put a note about this on the bug fx14push
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
verified fixed https://www.mozilla.org/en-US/products/
Status: RESOLVED → VERIFIED
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
Restoring unintended removal of in-testsuite flag.
Flags: in-testsuite?
You need to log in before you can comment on or make changes to this bug.