Photograph by Grandpa, July 4, 2006. The lousy cropping is my fault; the original is framed quite beautifully.
I’m thinking of giving up iWeb in favor of SandVox. Not that I have to decide now, or in fact ever - I’ve got purchased copies of both. But being such a Mac-head, I’m feeling a little conflicted about it. Shouldn’t I give iWeb a little more time? Shouldn’t I have faith that 2.0 will clean up some of the irritants?
It might. And it’s not that SandVox is without irritants - it just has fewer, and it has some really nice features that I’ve felt the lack of with iWeb. For one thing: comments, and without weird configuration issues. For another thing: a built-in ftp client. For a third thing: when you publish the site, it only uploads diffs. Oh, bliss! That’s been the biggest iWeb pain for me - publishing to disk and running recursive checksums to see which pages are different. With SandVox, one click and I’m all done.
Of course, I haven’t developed a really large site yet with SandVox. They’ve got more templates, but in odd ways they’re less configurable. I haven’t tried them on non-Safari browsers yet, either (and in all fairness iWeb seems to have cleaned up some of the strange rendering bugs they had earlier).
I’ll certainly maintain a hybrid set of sites for a while. I’ve been using SandVox for largely text-only stuff so far - or maybe I’m just getting better at web design! As lovely as it is to have an adorable Emily picture with every blog entry, it makes for a BIG, SLOW SITE. Which probably wouldn’t matter to me if it weren’t for the dreadful satellite internet we’ve got - but that’s another issue. (Keep your fingers crossed for Princeton Electric. We’re hoping to see in-town broadband by the end of the year.)
What it comes down to is this: I don’t have anything different to say, but I’m having an awfully good time twiddling with these WYSIWSG tools.
(Here’s the SandVox site I have up. I change templates frequently, so don’t expect it to look the same.)