For the first-time blogger, deciding which platform to sign up with, comparing features is important. How much is advertising and how much is truthfully telling what you can really do? Today marks the start of a new series, comparing the features of WordPress and TypePad, as they are advertised on the TypePad Features website and the WordPress Features website.
It’s so funny. A year ago, after testing both systems, I knew very little about everything WordPress, but I fell in love with everything TypePad in an instant. Today I know I should have stayed with WordPress. A year ago I probably would have sided with johnny on his post about TypePad for serious bloggers. Today, I’m actually defending WordPress more than I thought I would ever do, hence my compulsion to leave a long comment on that post.
One of the biggest differences between TypePad and WordPress is how to insert images in post. As a long-term TypePad user I am really confused by this.
Just like WordPress, TypePad too has an easy “insert image” button/icon in the composer toolbar. But what happens when you click this button in WordPress is very different from TypePad. In this post I will try to explain the differences as best I can. As it turns out, WordPress does have some tricks up the sleeve that TypePad has not. TypePad on the other, seems more straightforward and intuitive for the inexperienced blogger. Which one is better I leave up to you to decide.
What amazes me is how different image display works in WordPress versus TypePad. A thumbnail in TypePad pops up neatly on top of the post in a new window the exact size of the image. Nice and as it should be; to me that is the whole idea about having a pop-up image. In WordPress, there’s a whole new window blocking my post, see examples below.
The ability to preview posts as they actually will appear on your blog is one thing where WordPress differs considerably from from TypePad…in favor of WordPress, huge favor that is. As soon as you have saved your post, before it is published, you can preview your post on WordPress, thus allowing you to do some more editing or tweaking, change line breaks or paragraphs, move images around or whatever, until you are completely satisfied. And then you can publish. TypePad cannot do this.
One of the things I don’t like about TypePad is the way TypePad handles image URLs if you’re having multiple domains or blogs in one account. TypePad is unable to separate one domain from the other when it comes to inserting images. All images are linked to the main domain or the default blog associated with the account, not with the domain mapped to the blog you are inserting the images into. However, there is a workaround.
Both WordPress and TypePad allow domain-mapping, and both TypePad and WordPress give detailed host-specific or generic instructions for how to apply domain-mapping to your blog, so it’s a straight-forward process. But there are some things you need to keep in mind, though.