725287 - Use One Mozilla breadcrumb style (revert bug 716018)

Status: RESOLVED WONTFIX

(support.mozilla.org :: General, defect, P4)

Description

[James Socol [:jsocol, :james]]

Revert the changes in bug 716018 to the breadcrumbs and use the One Mozilla style (c.f. http://careers.mozilla.org).

Comment 1

[:ibai]

Can I say that we should revert to the previous situation as soon as possible and implement the One Mozilla style as soon as we build a coherent information architecture that we can map with a consistent breadcrumb across the site?

At the moment we have breadcrumbs in the contributors forum and the support forum. The former has 3 levels while the later has only 2 levels.

Then we have "breadcrumbs" of one level in pages like this:

https://support.mozilla.org/en-US/flagged

Instead of changing something in 2012.4 and then change it again in a month or so I think that is much more efficient to do the whole implementation once we have a solution that is here to stay (i.e. we know how the breadcrumbs will be implemented in the KB).

Comment 2

[Ricky Rosario [:rrosario, :r1cky]]

I reverted the 3 related commits and will cherry pick to next so it lands next week.
https://github.com/mozilla/kitsune/commit/e0c05cef82e058325aac5d6b6522cd168f763fb2

Comment 3

[Kadir Topal [:atopal]]

Ibai: I don't think the information architecture would have an effect on the styling of the breadcrumbs, this is a CSS change. We'd need to do it anyway, no matter what the new iA would say. This bug does not touch code AFAIK.

Comment 4

[:ibai]

I'm not talking about the styling. What I'm saying is that we shouldn't rush the development of the One Mozilla styiling because this is not appropriate because today breadcrumbs are not really useful.

That's why, IMHO, is better to revert this changes, this almost for free...and then fit the One Mozilla design development after the new content and taxonomy is in place. At that moment the breadcrumbs will make sense.

In the meantime we can use that time to develop something that is more beneficial in these next weeks/months.

Comment 5

[Kadir Topal [:atopal]]

I'll take this as my personal free time project.

Comment 6

[James Socol [:jsocol, :james]]

To undo the change in bug 716018, simply use

git revert f38728a6cfc10adc888c05d299ad02fd795948b6

Comment 7

[Ricky Rosario [:rrosario, :r1cky]]

Sprint based milestone :-)

Comment 8

[Ricky Rosario [:rrosario, :r1cky]]

Moving 2012Q2 bugs to Future.

Comment 9

[Ricky Rosario [:rrosario, :r1cky]]

The new redesign makes this issue go away.