Sporkmonger

purveyor of fabulously ambiguous eating utensils

Relaunched, Realigned

Posted by sporkmonger
Written April 2nd, 2007

If you can see this, apparently everything is working.

Update:

Ok, so there were some bugs. Incorrect permissions and such, not-quite-right Apache settings. But it’s likely to be more functional now.

After several weeks of work on the site, I’ve finally gotten everything moved off Typo, redesigned, and generally just looking a thousand times better than before. I also hosed out all of the accumulated spam. It wasn’t easy.

At Aristotle’s request, I made sure to modify the Typo conversion script (as well as Mephisto itself) to allow the feed entry GUIDs to remain the same. I wasn’t particularly pleased to discover that Mephisto doesn’t actually store its entry GUIDs in the database—it generates them each time the feed is requested, which in my humble opinion is a terrible idea, since the information it uses to generate the IDs might change. The change I made added a “guid” column to the database and uses UUIDTools to generate unique ids instead.

I also deleted a bunch of entries that I no longer felt were relevant to the site. I know a lot of people in the pro-standards crowd don’t like it when people do this, but I did anyways. I also tried to set up redirects for all of the old resources to the equivalent URIs in Mephisto, but I’m sure I missed a couple. If you bump into a 404 that you think is a mistake on my part, I’ll try to get it fixed as quickly as possible.

In addition to the switch to Mephisto, obviously I also took the time to redesign the site. I figured I should construct the design entirely from scratch this time instead of simply altering the default Typo theme. I gotta say, I really, really, really like the new look. I haven’t bothered testing and seeing how it looks in Internet Explorer. I really just don’t care that much about IE anymore. But I didn’t do anything particularly tricky with the design either, so it’ll probably look mostly OK. If you’re reading this in IE, stop, go install some other browser (preferably Firefox), and then come back. Web developers everywhere will thank you for it. And you’ll feel better about yourself. I promise.

I released a new library the other day called Squish. Admittedly, in its current state, it’s really effectively useless. I’ve never been particularly good at optimizing for performance, and while I did manage to improve the speed of the library (with the help of people in #ruby-lang) by at least an order of magnitude, it’s still way too slow to be useful. In retrospect, I’m not really sure why I even tried to write it in Ruby—I really should have known that a compression-based text classifier would need to be written in C. But hey, at least I know the basic idea works now.

Oh, and you may also notice that the site is faster and less error-prone now. You can thank Slicehost for that. I can’t recommend them highly enough if you’re in the market for a Rails-friendly VPS host.

  1. Written April 3rd, 2007 at 05:16 PM

    I’m curious, did you use any pre-packaged stacks on Slicehost, or roll your own? Anyhow, looking very slick!

  2. Written April 3rd, 2007 at 09:15 PM

    Looks just fine in IE7.

    IE6 has two problems:

    1. The content column is not centred, it’s flush against the left edge of the browser window. You probably don’t need to care about this.

    2. The content is much wider than the header; the header ends up flush left inside the column with 100 pixel of dark grey background to its right.

    The feed migration worked a treat! I hope your changes find their way upstream soon so they can commence trickling down to other Mephisto users

  3. Written April 3rd, 2007 at 09:17 PM

    Bah, I hate the Textile link syntax. Obviously the link was supposed to exclude the ellipsis…

  4. Written April 3rd, 2007 at 10:12 PM

    Oh yeah, two other things:

    1. It would be nice if the page title included the post’s title on post pages.
    2. The comment comes pre-filled with two lines’ worth of whitespace.

    (Sorry for the comment flood.)

  5. Written April 3rd, 2007 at 10:29 PM

    Jason:

    Nope. Set up everything from a basic Ubuntu server slice.

    Aristotle:

    Yeah, you’re right, the double line thing in the comments is annoying.

    I’ve been meaning to put together a comment preview, but I haven’t had the time yet. I like Textile mostly because I’m just used to it. I’d probably like Markdown more if I’d started off with Markdown. <shrug> Sam Ruby’s formatting system is pretty nice though. I like that one.

    Regarding IE6, I’m not really sure how best to fix it. I thought I had fixed it already, by putting in text-align: center hacks, but I guess not.

  6. Written April 4th, 2007 at 04:57 PM

    Thanks Aristotle, I get the hint! Although it may be too late for me, because I am fully on board with Mephisto now, and cannot see myself using the Typo migration code again.

    Bob, nice site design. And thanks for the slicehost recommendation.

    If you get comment preview working, I’d really like to use it.

  7. Written April 5th, 2007 at 12:41 AM

    I’ve fixed all the issues except the IE6 rendering bug. Still not sure how to make it look right in IE6, and I’m feeling awfully uninspired to deal with a bug that affects a mere 10% of my readers. All of whom should know better.

    But if someone is particularly bugged by it, feel free to tell me what I’m doing wrong and how to fix it and I will.

  8. Written April 5th, 2007 at 07:50 AM

    Alastair: I wasn’t hinting overmuch, you really were just an example. :-)

    Funnily enough, though, I still get dupes of all your items – not just the old posts from Typo, but also the new posts. But it’s never more than two copies of each item. If I delete either of them, sooner or later I get another copy; but always just a pair. It’s as though the feed generator is flip-flopping between two forms of entry ID.

    However, I do not get dupes in your comments feed! I don’t know what that’s about.

Leave a Response

NOTE: I'm afraid Javascript needs to be on in order to comment.

Comments should be formatted using Textile.

Ruby code should be enclosed within a <macro:code lang="ruby"> element. Other languages are supported. For output you can simply omit the lang attribute.