Author: Daniel Greene

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.”
(more…)

It’s been such a headache for me to manage my WordPress.org-powered blog that I’m thinking of moving it over to WordPress.com. I didn’t realize until recently that I could even have it all on danielgreene.com. I read this article called WordPress.com vs. WordPress.org tonight, and I realized that, on WordPress.org, none of the Pros are helping me and all of the Cons are hurting me, whereas on WordPress.com, none of the Cons would hurt me and all of the Pros would help me. I’m not a PHP programmer nor do I really want to hire one to manage my site for me. I freak every time I have to update from one WordPress software version to another. Automatic updates always hang. Manual updates are a pain. With WordPress.com it’s all taken care of, and I could focus solely on what I really love to do, which is write and share media. The terms of service for WordPress.com forbid ads, but I don’t earn more than maybe $100 a year in Google AdSense ad revenue on danielgreene.com anyway. With the money I’d lose, I’d gain time— and peace of mind! And the few “legacy” pages I have, such as my Style Sheets Demo Page, while pioneering in its day, hardly seems relevant anymore. I could probably even put some of that CSS into a WordPress page anyway.

What do you think? Any reason why I shouldn’t turn danielgreene.wordpress.com into danielgreene.com and move my blog over here?