Mar 30
2007
Jerome’s Keywords and Tag Cloud Widget
With this new edition of The Daily Twaddle, I decided not to use categories. I’m using tags instead. Word Press calls their categories tags, but they’re really categories. Tags are more flexible and accurate to organize and categorize blog posts.
I used Chip’s Tag Cloud Sidebar Widget. You can see it on the side listed “Tag Cloud”.
Want This On Your Blog?
1. Enable widgets.
2. Go to Jerome’s website and download the 2.0-beta version of his keywords plugin. This is the only version that will work with the sidebar widget. Follow the directions from the website.
3. Go to Chips’ Tips and click “give me the code.” Follow the directions from the website.
No related posts
[…] Jenn uses the tag cloud widget, and links to it. Phastidio uses it, too. […]
Styling Update
I don’t use the font tag anymore since everyone yells “DEPRECIATED” at me. And the yelling hurts my feelings. Therefore, hence, and forthwith, I changed the code in the original Chip’s keywords-tagcloud.php file so I can use pretty CSS.
I replaced:
<font size="%count%" class="cosmos keyword%count%"><a href="%fulltaglink%">%keyword%</a></font>with:
<a class="keyword%count% "href="%fulltaglink%">%keyword%</a>Then I styled my main CSS stylesheet like so:
a.keyword3, a.keyword4, a.keyword5, a.keyword6, a.keyword7
{font-size: 11pt;}
a.keyword5, a.keyword6, a.keyword7, a.keyword8, a.keyword9
{font-size: 12pt;}
a.keyword10, a.keyword11, a.keyword12, a.keyword13, a.keyword14
{font-size: 13pt;}
a.keyword15, a.keyword16, a.keyword17, a.keyword18, a.keyword19
{font-size: 13pt;
font-weight: bold;}
… etcetera, etcetera…
Hey Jenn,
Thanks for using the widget. You can still use CSS styling even if the font tag is left in. The CSS font size should override the font size specification.
Hey Sterling Camden! It’s totally awesome that you left a comment on my blog!
You’re right about the font tag working fine by styling with the CSS. In fact, the widget worked great right out of the box! But I read somewhere that the font element is not supported in XHTML 1.0 Strict DTD.
I can’t back this up on paper though. I should have said pretty XHTML instead of pretty CSS.
You are correct, Jenn. I’ll have to look into upgrading my widget without impacting existing users.
WordPress pingback led me to your post. I’m honored that you think my commenting here is “awesome”. I wonder what would you think if I subscribed to your blog and added you to my blogroll in the sidebar here?
Ooh - great list! Oh no! I’m still using the strike tag. I’ll have to strike that from my available tags… ha ha - good one Jenn.
Subscribing to my blog? Adding me to your blogroll? Holy cannoli! That is colossally awesome! I’m clapping like Paula Abdul during finals week!
[…] me clueless, but I did not know until I found out from Jenn that the <FONT> element has been deprecated and will not validate XHTML 1.0 strict DTD. […]
Hello
Great book. I just want to say what a fantastic thing you are doing! Good luck!
G’night
Thanks! Hopefully I can reply to comments within a reasonable amount of time (thanks to Verizon).