I’ve mentioned this before and it didn’t go anywhere. I ended up hacking WP’s innards to get what I wanted, but after several updates, it’s getting old. So I’m back, and this time I ain’t going down without a fight ; )
Currently, the xhtml used to mark up the Link List has 2 probems.
- It severely limits the ways we are able to apply css.
- It isn’t semantically as strong as it should be
Using the default as an example:
It is impossible for me to style(e.g.
padding-left: 1em;) the word ‘Links’ without also affecting the nested list that follows (i.e. Alex, Dougal, Matt, etc.). (In this case the nested list that follows would also have the padding applied)
If the word ‘Links’ were just marked up in any way at all(even a dreaded span tag would do)–rather than just hanging out naked in this giant list item–then I could add padding without affecting the list.
Semantics are obviously important to WP developers and users, otherwise the entire menu wouldn’t be marked up as a series of nested lists. Which is why I don’t understand why in this case ‘Links’ isn’t marked up as an
h4. After all, it is a heading for the list that follows.
I know there are those who oppose all but the most minimal markup necessary to get the meaning across, even if that means leaving no hooks for css. But in this case–semantically speaking–I argue that it is more important that the word ‘Links’ function as a heading(describing the list of links that follows), than as a member of the
But the beautiful thing is that, in this case, we can have our cake and eat it too.
Vote yes on the
- You must be logged in to reply to this topic.