Smile! As brightly as you should!
Smile! 2.0 has just been completed! There are two awesome things about this release: it finally looks to everyone1 like I want it to, and it does a better job of saying what it means.
The first thing—looking how it was meant to—is thanks to Google’s release of their fonts API and directory, which includes Inconsolata. This means that I can now say “use Inconsolata for this!”, and even people who aren’t programmers on Linux with a good taste in monospace fonts will have their headers set properly. This is a great improvement from before; I shudder at the number of people who had to look at headers in Andalé Mono or—gasp—Courier.2
The second bit comes as a result of Smile! being almost totally rewritten to take advantage of the new semantic bits of the up-and-coming HTML5. I have my doubts that anyone actually cares about this, but I offer my assurance that it’s very exciting. It’s entirely unnoticeable on the outside, but any computers trying to make sense of a happy, Smile!-using blog would, themselves, smile if they could.
My gushing complete, here’s a (very) short list of minor changes in 2.0:
- Styling of answer posts.
- Addition of tags to post footers.
Finally, there’s one major feature that was not included in this release: better typography. I’ve been experimenting with this in a new theme, and intend to improve it in Smile! once I’m confident I’ve figured out what I’m doing.
Update: 2.0.1 is out, adding a few improvements and fixing a stupid bug (I forgot to wrap titles for text posts in a {block:Title}. Good, eh?).
Update again: 2.0.2 is also out, adding support for pages.
Oh, come on now—really?: 2.0.3 puts a bit of whitespace back where it belongs.
-
That is, everyone with a browser that supports
@font-faces. This includes Google Chrome and Apple’s Safari, Mozilla Firefox, some recent version of Internet Explorer (6 and up!), and Opera. (The latter does it a bit poorly, though.) If you’re in the market for a new browser, I heartily recommend Chrome. ↩ -
I know a guy who programs in Courier. I helped him track down a bug—a nonterminating
forloop—in his homework once. Turns out1, unlikei, is always less than 1000000. Also turns out that bit about ‘1unlikei’ isn’t really true when you program in Courier. ↩