Why I moved my blogs from WordPress.org to WordPress.com

I finally got tired of the hassle and hours it took me to update my WordPress.org-powered self-hosted versions of two different blogs–danielgreene.com and smithersgreene.net. Trying to upgrade my blogs to WordPress 3.0 was the last straw.

I’m a guy who started writing his own HTML and CSS in 1996; in fact, I was one of the first handful of brave ones on the Internet to style valid HTML with CSS knowing that most browsers couldn’t handle it. After all, what did I have to lose? Little old me with his personal website.

This was a decade before Flickr and YouTube and Facebook and Twitter allowed you to post content with ease and let them take care of the code, and years before every major website was written in structural HTML and styled with CSS. This was back when you had to either have a self-hosted website or something like AOL Hometown Web pages. This was when “Web Designers” would charge you an arm-and-a-leg for a page and a couple of links. I was okay with the idea that, if I wanted a site that used proper HTML (without proprietary structural markup) and CSS, I had to get an ISP to host my own website. And I had to write all my own HTML & CSS.

Things have changed in the past few years. Even with WordPress.org, I had more freedom to blog without worrying about the coding. When I didn’t have to worry about updating WordPress and editing .htaccess pages and PHP files, it worked great. But I hated it when I would break my site when trying unsuccessfully to upload new versions of the blogging platform software. I thought, “Why can’t it be more like posting content to Facebook, Flickr, Twitter, or YouTube? I can’t break those sites. There must be an easier way.”

So I did some searching and found out that I could import my whole site–actually both sites–to WordPress.com, manage both sites from one Dashboard, and port my domain names for only $10 a year per domain. That’s when I decided to move over to the gentler, easier version of WordPress.

Yes, there are limitations. But there are also benefits. And for me, the benefits far outweigh the limitations. I should have moved over a long time ago, because I wasn’t using the advanced options of WordPress.org anyway.

Another reason I moved over is because I’m just enough of a stupid geek to get lost in hours of trying to figure out how to make things work, and I need to stop doing that. The important thing is for me to create content–be it writings, photos, videos, or updates–and publish it easily. So, here’s to my being more creative and less geeky!





One response to “Why I moved my blogs from WordPress.org to WordPress.com”

  1. How I lost money trying to make money on this blog | Daniel Greene Avatar

    […] on this blog when I self-hosted it. It took too many hours of my time to do manual updates, so I moved my blogs from WordPress.org to WordPress.com even though I knew I was giving up the right to have AdSense on my blog. Not having to bother with […]


Comments welcome

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: