I plan on adding some sort of sidebar (perhaps one with minimizable sections that bobs along with the reader) with relevant code fragments/explanations beside the content, as well as plopping in a TOC sort of box dealy with named anchors for long posts like this one.

The syntax highlighter plugin actually doesn’t use a stylesheet, it’s all inline styles so it works even within feed readers. (check it out on FeedBurner by following the RSS link at bottom) I will definitely be looking at this soon.

Linking to relevant jQuery docs is a good idea, which I’ll follow inasmuch as the first time a function shows up I’ll link to it.

I’ll look into the cowbell suggestion.

If I had linked to the jQ function parents() line 3 would’ve made more sense. (see here: http://docs.jquery.com/Traversing/parents#expr)

Passing in a CSS selector string filters the results which would otherwise provide the entire set of ancestors for a given node.

The function “parent()” (singular) returns only the direct parent. The function “parents()” (plural) returns this ancestor set. It’s the fastest way to obtain such references.

Since “.tabset” may or may not be the direct parent, depending on varying markup mentioned earlier in the article, calling parents() was the safer bet.