It seems like there’s always something out there to fix, something to improve upon, and as a result, I bring you Cutline version 1.03. While it’s not quite as significant an upgrade as version 1.02, version 1.03 does contain a couple of major additions as well as a few cosmetic and under-the-hood changes.
All in all, this is yet another big step for the theme, and just like last time, I’ve gone ahead and compiled a list of the individual changes and the affected files. Oh, except this time, I was a little less reverent and a little more funny 🙂
Version 1.03 Changelog
Numbers one, two, and three in the list below can all be considered major upgrades. One and two were highly requested by users, and number three makes for a great addition to any blog. So, without further ado, here are the changes in Cutline version 1.03:
- 1. Link categories now supported in the sidebar
- Although I was hesitant to do it because the auto-generated code is so poor (my opinion), I went ahead and included link categories in the
sidebar.phpfile. Now, all of your links will be separated and nicely categorized, just like those you see in the sidebar on this site.
- 2. Larger font in the sidebar
- Lots and lots of people had complained, both here and on WordPress.com, about their inability to read some of the sidebar items on certain monitors. The primary gripe was that the text was too small, and that was actually something that I specifically set out to avoid when I created the theme. Apparently I didn’t do a good enough job on the first go-round, so now I’ve made the sidebar fonts a bit larger.
- 3. Support for the Subscribe to Comments plugin
- While this plugin actually works quite well out of the box, a tiny bit of styling is necessary to make it mesh perfectly with Cutline. Two lines of CSS later, you’ve got a perfect implementation of a comment subscription option.
- 4. All (and I do mean all) vertical spacing has been converted into ems instead of pixels
Paragraphs, margins, padding, text sizes, you name it — they’re all consistently sized in ems now, so that the entire site scales seamlessly whenever text is resized. This should have been done in the first place, but I figure it’s better late than never, eh?
Actually, it scaled nicely before, but whitespace was defined in pixels, not ems, and as a result, the whitespace appeared to shrink whenever text was resized. Since I lose sleep at night over things like this, I bit the bullet and changed all vertical pixel references into ems. Take that, neuroticism!
- 5. Line heights in the posts have been changed from 1.7em to
- Maybe it’s because I’ve been looking at the theme for so long, or maybe it’s because I’ve been reading too many books on typography…but the bottom line is that I felt as though the line height in the content area was just a tiny bit too large. So, I dropped the height a twentieth of an em, and the difference, although subtle, pleases me greatly. Y tu?
- 6. Vertical spacing after titles in definition lists
- Many of you may not even be aware of what a definition list is, but either way, I’m sure you’ll be happy to know that I’ve allowed for more vertical spacing after
<dt>items. Now, definition lists are cleaner and more legible than ever before! In fact, this entire changelog is one big definition list. Looks good, no?
- 7. Unnecessary XHTML removed from
- I found some lame code lying around inside the
comments.phpfile, so I got out my nuker and, well, nuked it.
- 8. (Some) unnecessary CSS removed from
- Ummm, yeah. Same story as number 7 above. Used the nuker.
Only three core theme files have changed for this release —
If you haven’t made any changes to your theme files, then you have nothing to worry about. Just overwrite them all and have a good day.
If you’ve changed your header images, don’t overwrite the images folder within the Cutline directory! Don’t do it! Stop already!
If you’ve made changes to your
style.css file, you’re kind of up a creek here. A lot has changed in various places, so I think it’s probably best if you just try and move your major changes over to this new CSS file.
Very soon, I’ll be releasing a special CSS file that you can use to handle personal changes to the theme. This way, whenever there’s an upgrade, your changes will go unaffected.
If you’ve got the moxie, you can go ahead and do this on your own by creating a new CSS file — say,
my_styles.css — and then including a second stylesheet reference in
header.php. You’d need to add this reference inside the
<head> tags, and it would look something like this:
<link rel="stylesheet" href="<?php bloginfo('template_url'); ?>/my_styles.css" type="text/css" media="screen" />
Now go forth, and be more functional than you were one version ago.