Forcing h3 within topbar is bad practice

[danspam]

Heading tags are supposed to follow each other in descending order, starting from H1. The styles for the topbar are forcing you to use an H3 tag in the header before any other heading tags. Perhaps this should be changed to a class so that you can use whichever tag you want for the website name.

[mdo]

I've used the h3 since it provides some level of styling with and without the CSS applied. This makes a quick little hierarchy in the topbar before the page's started H1 and provides a label above nav that is larger than typical nav links. Make sense?

[fauzias]

I'd like to propose the tag for putting an images/logo also in the topleft bar, since lastly i've had to hack around to get the logo properly fit alongside the heading title

[harrybailey]

I agree with danspam. Replacing the h3 with a class or <strong> tag would by more semantic.

[vonkohorn]

fauziassegaff -- images/logo aligns pretty nicely if you also put it inside an h3 tag.

[fauzias]

vonkohorn -- i did, but it's just feel improperly to put it there, i'd much prefer putting it in it's on span/div with logo class, one of the reason also is sometimes we want to put the logo overalapping the component of h3 itself

[mdo]

Filing this under v2.0.0 for now since we'll have to change classes. We might be able to do it now with 1.3-wip and support the old stuff, but we'll see.

[mdo]

Welp, that was easy :).

Starting in 1.3, we'll have .brand in the topbar in addition to the h3 tag. With v2, we'll remove the h3 and other legacy cruft.

Why .brand? Because "logo" implies a graphical treatment of something whereas "brand" can be a word, an image, or both.

Thanks guys!

[harrybailey]

Great. Currently it's .container > h3 > a What will it be from v2?

.container > span > a
.container > p > a

?

[mdo]

In 1.3-wip and 2.0, it will be .brand a.