My New Weblog

I haven’t posted for a couple of days because I’ve been in the process of migrating my weblog. In fact, all the weblogs are eventually migrating over to, and to a new version of Movable Type. I wanted to migrate mine first to get some experience with the process, and to get any issues/bugs worked out. If you see any problems, let me know.

The biggest challenge has been redirecting from old post URLs to the new ones (since the new version of MT generates different types of URLs). Anil Dash set me up with some MT code to generate an .htaccess file to make Apache do most of the work, but there are tons of other things to consider when migrating a two-year-old weblog (images, feeds, go URLs, and other files).

Over the next couple of months, I intend to update my templates, but for now, I’m using only a slightly modified version of the MT default. My stylesheet is pretty standard, as well, with only a couple customizations. In fact, I’ve heard it referred to as “nice, but unoriginal.” True. I’m not much of a designer, though, so if you have any suggestions, let me know.

Technical details first, aesthetics later.

7 Responses to My New Weblog

  1. Christian Cantrell says:

    This is a test comment. Does this new weblog work? Anyone want to help with my design?

  2. Jen deHaan says:

    10-4!I like designing, but there are many who far exceed me in talent so pick me last. 🙂

  3. I have always been a proponent of using the open source web design project ( for this type of situation. I used a slightly modified oswd design for my own blog.

  4. Tony Weeg says:

    design.i can design is my own i think that would look cool, with a new header, that is YOU centric… maybe Macromedia Centric, and could change based on whose blog it is…let me know if you want an idea thrown your way.later.tony

  5. You should take a look at WordPress if you’re going to be completely redoing your blog. I switched from MT to WordPress about 6 months ago or so and I have zero regrets. http://wordpress.orgMuch easier to setup than MT, publishing doesn’t take forever because of the static file generation, very easy to apply “skins” for the design, etc.Also if you’re not groking the RegEx needed to do redirects in Apache, you might take a look at this:

  6. Oh, nevermind. It looks like FullAsAGoog picked-up an old entry and aggregrated it… so you’ve probably already done the switch.

  7. Anil says:

    Looks great, Christian! For some quick stylesheets you can swap in, you can take a look at, or you can just use the Dreamweaver extensions to lay out your page and export the template set. (I dunno if Adobe’s tools are kosher at the Macromedia campus yet, but GoLive CS2 supports this, too.)To address Brandon’s points, I’m not sure his suggestion is realistic given the number of blogs you’re administrating, (nobody wants to update 50 application installs every time there’s a point release of a blog tool) but since you’re with MT, you can choose to do dynamic or static page outputs with MT if rebuilding is an issue for you. Since it seems like at least one of the Macromedia blogs gets slashdotted every day, the static pages are a good option, and either way you can output .cfm files if you want to include ColdFusion tags.And most of our users find it easier to simply swap in a different CSS file to format their pages so that they don’t have to mess with output templates, let alone dive into mixing scripting with their HTML structure.