Choosing a Blog Platform

Never has it been easier to setup and maintain a blog, and a large part of the reason is the blogging platform. The blogging platform includes the blogging software itself, along with the hardware and infrastructure required to power the software.

The two main categories of platforms are hosted (often referred to as “services”) and self-hosted (often refereed to as “standalone”).

Hosted Blogs (Blog Services)

Hosted platforms refer to services whereby a service provider grants you access to their hardware, network connection, and software, and you create a blogging account to use on that platform. This would be very similar to signing up for an account at a site like Facebook or MySpace. As far as you’re concerned, there’s nothing more than a web page where you enter and view your information. Everything that goes on behind the scenes is con-trolled by someone else, and you have no stake other than being a user of the service.

Within the hosted blog space, you have a few subcategories of service, as well. There are pure blog plays—your account is used to create a blog, and the end result that gets traffic is a blog and a blog only.

There are also social networking services that build blogging into their platforms. MySpace has a very rudimentary blogging system, though I don’t believe that it meets the accepted requirements of a blog. Then there are services that fall somewhere in between, like Xanga and Vox, which offer a mix of media and social networking.

Some pure play examples include:

• LiveJournal
• TypePad
• Blogger
• Blog.com
• Wordpress.com (not to be used with the software available from Wordpress.org)

Advantages of Hosted Platforms

• Inexpensive: many are free; others (like TypePad) are offered with multiple price points
• Simple to setup: just create an account and get to blogging
• Page rank: search engines might give more favorable weightings to hosted blogs, but note that this, if it is true, would only hold true for low-traffic blogs
• Automatic updates: you don’t have to worry about keep-ing hosted software updated and patched

Disadvantages of Hosted Platforms

• Inflexible: there are fewer configuration options with hosted platforms. This often results in applying workarounds or “hacks,” which make moving off of the platform cumber-some.
• Fewer design choices: you typically only get to select from a limited number of average designs, and you often can’t make updates to the standard designs
• Generic URL: some hosted platforms will allow you to use your own URL, but the process can be complex; others don’t offer the option at all
• Less control: you are at the mercy of the platform
• No commercial sites: some platforms will not let you serve ads on their platforms

Self-hosted Blogs (Standalones)

Self-hosted platforms consist of a web hosting account you establish with a data center, and the blogging software you install on the data center’s server.

Some self-hosted solutions include:

• WordPress (not to be confused with the hosted accounts at WordPress.com)
• MovableType (the self-hosted version of TypePad)
• SubText
• typo
• Apache Roller

Advantages of Self-hosted Blogs

• Design flexibility: you have full control over design and lay-out
• Great software: the best software exists on self-hosted plat-forms
• Custom URL: custom URL’s are ubiquitous on self-hosted platforms
• Adaptability: your blog can change as your needs change

Disadvantages of Self-hosted Blogs

• Difficult setup: setup can sometimes be difficult
• Cost: while the blogging software is free, the hosting platform will cost you money
• Hosting issues: unless you choose a good host, you might have to suffer from downtime or poor support.
• Upgrades: you will need to keep your software patched

Blogs are really specialized versions of content management systems (CMS), which are systems used to manage the computer files, images, media and content of a Web site. CMS’s generally support workflow, which is a process for moving content from creation, through approval, to publishing with automated routing and notifications. CMS’s usually support a large number of authors and editors (sometimes collaboratively) in a distributed environment.

Blogs are simplified versions of CMS’s, though they retain many of the same characteristics, and I do know of some people who use WordPress in place of a full-blown CMS.

Popular CMS’s include:

• Textpattern
• Drupal
• Joomla

Which Platform is Best?

It’s a personal decision. The majority of my blogs are self-hosted. I prefer the flexibility and design options available to me in self-hosted software. Self-hosted solutions are also much more professional. Blog readers can tell a difference.

Often, whichever blog platform you start on, you finish on. As  your blog gets larger and more backlinks are created, you start to become handcuffed to the platform. This blog, for example, was hosted on Typepad until two weeks ago. Not because I preferred Typepad, but because it started as a quick and dirty personal blog that continued to grow. That’s one reason I always recommend that peopled start blogging on a flexible platform–you always have room to grow.

In February 2007, I conducted a usability study with several readers, placing the same content on two different blogs, one hosted, and one self-hosted. Both were setup to take full advantage of the underlying platform, meaning I made the blogs look and behave as best as I could with the tools I had available. Universally, the self-hosted blog was perceived to be higher value, and the content was considered to be more credible.

Note that this was a small study, and usability tests are not what I would consider scientific by nature, but the anecdotal evidence is worth considering.

For my money, I will always go self-hosted. Your mileage may vary. If you just want to try this blogging thing out, try one of the hosted services. But if plan to maintain a professional blog, I think you’ll find yourself upgrading quickly.

I’ve used six different blogging services, hosted and self-hosted, and I’ve dug around the API’s of several. WordPress is hands-down the winner.

• WordPress has an extensive theme directory. Themes are used to change the look and feel of your blog. You don’t need to know how to design or code a thing.
• Thousands of themes are available around the web, and if you want a premium theme, you can find quite a few of them. Premium themes are great for sites that you want to monetize, or where you want to convey a professional presence.
• WordPress has an extensive plug-in directory. Plug-ins enable you to add interesting functionality to your blog. How about a map of your recent readers? Adding a contact form to your about page? Showcas-ing affiliate products? Fighting spam? Improving your search engine rankings? Mobilizing your site? If you can think it, a plug-in is probably around to do it.
• WordPress offers complete administrative control over your blog. There are very few things that you can’t do with your WordPress blog if you’re self-hosting.
• WordPress has excellent user management, using a role-based security model that supports multiple levels of access. For example, authors can write articles, editors can publish those articles after approval, adminis-trators can change the design of the blog.
• WordPress fights spam. A comment spam plug-in installs with Word-Press by default. Say goodbye to that annoying Blog Blaster spam.
• WordPress has an active and enthusiastic contributing developer community. This means that software updates are frequent, bugs are fixed regularly, the software is mature, and requested features are actually added to the product by people who care about and use the product. The WordPress community is the reason why WordPress is such a powerful and easy-to-use product. It is a real gem.
• WordPress has an easy-to-use page editor. With pages, you can really blur the lines between what is a web site and what is a blog. Pages allow you to store static content (i.e. content that isn’t regularly updated). Pages are especially common for people who use WordPress as a content management system. For a lite version of WordPress-as-CMS, check out the Thirty Days to Blog Traffic site.
• There are a large number of SEO (Search Engine Optimization) reasons for choosing WordPress, but a discussion of them is outside the scope of this book, so I’ll just say that WordPress has paid atten-tion to how to help search engines find your blog.
• There are also plenty of SEO and traffic-related plug-ins available for WordPress.
• It’s free! There are other free blogging packages out there, but none offer the same combination of power and simplicity that WordPress offers.

Here’s an interesting exercise: Google “moving to WordPress.” People are moving for a reason!

In a nutshell, if you’re blogging, you need to be using WordPress. It’s that simple. WordPress has built a fanatical community and support base for a reason: they’re the best. If you find yourself on another platform like Blogger or TypePad and you want to move to WordPress, I’ve detailed the migration process step-by-step.

How to Port Your Blog from TypePad to WordPress (Part 2)

This is Part 2 of a 2-part post on migrating your blog from TypePad to WordPress. << Part 1

While the information in this post uses TypePad as the subject. much is transferable to other platforms.

Part 1 discussed overall migration considerations, preparing for the move, exporting data from TypePad, Importing data into WordPress, cleaning up images and file references, and taking advantage of some of WordPress’s features.

Redirect Traffic to your New Blog

If you’re going to drop any traffic, it’s going to happen right here!

1. Make sure the receiving server is ready for traffic.
2. Go to your domain registrar, and point your domain to the nameservers on your new hosting account or server. You’ll probably also have to delete the MX records that still exist.
3. Wait.
4. Ping your domain name to see which IP address responds, TypePad or your new server. As soon as the responding IP address is your new server, continue.
5. In your WordPress administrative panel, go to Options | General, and make sure your blog is pointing to your domain name, and not the temporary URL or IP address you used to setup your WordPress blog. If you’re using a new domain, this step doesn’t apply to you. Important: don’t perform this step until you know your domain is pointed to your server or you’ll lose access to your administrative panel. If this does happens to you, just open up your MySQL database, and update the entry in the wp_options table.
6. After cutover, go to your TypePad control panel and select Site Access | Domain Mapping. Remove your domain mapping. This step doesn’t need to be done, but I prefer to make a clean break.

DNS is painful. You need to coordinate different servers in different locations, and you can never be sure if what you see is what someone else will see (until propagation completes). So when something goes wrong, it’s often hard to pinpoint where the problem is. If you do things in the above order, you shouldn’t run into any problems. [Read more]

How to Port Your Blog from TypePad to WordPress (Part 1)

This is Part 1 of a 2-part post on migrating your blog from TypePad to WordPress. Part 2 >>

While the information in this post uses TypePad as the subject. much is transferable to other platforms.

You’re reading this post for one of several possible reasons:

• You’re looking into moving your TypePad blog to a self-hosted WordPress version, and you want to know what to expect
• You’re in the process of moving your blog, and something isn’t going right or something appears a bit wonky
• You’ve already moved your blog, and you want to make sure you’ve dotted your i’s and crossed your t’s
• You like me and you’re bored

When Quick Migrations Get Ugly

I have good news and bad news for you. Migrating to WordPress is incredibly easy (for the most part). And for most people, it should be a relatively simple move, even if some parts can get rather tedious:

• If you’ve hacked TypePad with any custom styles, stripping out the remnants of those styles can be painful
• If you have a large number of posts, error checking can be tedious
• If your posts are thoroughly cross-linked, you’ll have to re-link them
• If you’ve used a lot of photos in your posts, you’ll have to re-reference them and create your own thumbnails

That was the good news. The bad news is that to minimize downtime, to make sure your feed is available to your readers, and to ensure that you maintain your page rank after the move, you will have to jump through some hoops. So the physical migration itself is easy — moving your content from one blog on one server to a new blog on another server — but attending to the other concerns is what could cause you some headaches. If you have a high page rank, and want to maintain it, you’ll have to jump through some hoops. If you want to minimize site and feed downtime, be prepared for a little extra work.

There are many other smaller considerations, but the above are what consumed most of my effort. At the risk of stating the obvious, you probably noticed that characteristics of larger, more active blogs lend themselves to the more difficult migrations. Even still, I wouldn’t expect the total migration time to exceed 15 to 20 hours. For smaller, simpler installations, 1 hour would seem like an eternity.

Another thing I’d like to point out before going further is that I’m assuming that you’re going to be transferring a domain name along with porting your blog. That is, your TypePad blog is available at http://yourblog.com, and it should maintain that address when the migration is complete. If you’re moving from http://youraccount.typepad.com to http://yourblog.com, then the process is far simpler, because you won’t need to worry about the DNS propagation lags. Of course, you’ll also lose any page rank (at least temporarily) that you’ve worked to achieve, so understand that before you go in. [Read more]

Blog Ported from TypePad to WordPress

If you hadn’t noticed, I ported the blog from TypePad to WordPress over the weekend. I’ve been a WordPress user for a long time, but have been avoiding making this move. It’s not that I had so much content that it would be unbearable, just that I didn’t feel like the hassle. But it was time for a change.

I was expecting quite a few more hiccups during the migration, but it went rather smoothly all-in-all. There were some incompatibilities that had to be cleaned up, and the inevitable theme tweaking, but I’d much prefer to tweak with full control than hack without it! The biggest headaches were rereferencing the images and redirecting the old URL’s.

I’ll write up the experience step-by-step as soon as I verify that everything is working as expected. If you have any problems, or notice and irregularities, broken links, missing images, etc., please post a comment here.

Some things that I expect will need a little more TLC:

• Page formatting, e.g. line breaks where there shouldn’t be, sizing issues. (due to some hacks I used at Typepad)
• CSS formatting inconsistencies (hacks again)
• A few broken internal links; I think I caught all of the external links, but it’ll take a manual review to make sure I haven’t missed any of the internal ones
• A few hours to one day feed problems. Right now, FeedBurner doesn’t recognize the domain, so until the DNS changes propogate fully, the feed will appear to be down.

Old and new screen captures: