nav.primary vs nav.secondary... and beyond about boilerplate-archived

[khamer]

I would hope that most of the time, we wouldn't be implementing identical navigation in all three places, and the markup in Boilerplate only has them all to prove it works and make sure that the selectors are robust.

Also not really addressing the issue, we should be able to solve this with better navigation generation or such, as the amount of HTML isn't the issue, just the number of places we're maintaining it. Both Peter and I have put together navigation generation classes and implemented them, and while neither is likely perfect yet, that's probably a better long term solution.

All that said, I agree there's other implementations that work better for the use case at Moto (converting the active dropdown into the secondary nav and always showing it), I just was aiming to be flexible with Boilerplate and not too closely tie down the relationships between the different places navigation is shown. I'm fine with whatever UX thinks is easier to work with.

[davetufts]

I agree with Kevin's commend above - in the BP example we're basically showing two ways of representing the secondary nav on a single page. In real life we'd only do the horizontal bar or the sidebar. But I do like how BP has implementations of both.