So, before I get too far into this post (or perhaps before I even start it), I should point out that there are essentially two recognizable types of WordPress. There’s the main one, WordPress.org, which is blogging software that you install on a hosting provider. You own it and manage it, so there are fewer restrictions, but there are more responsibilities. Then, there’s WordPress.com, a blogging service which offers you a free WordPress-powered blog with the option to purchase additional upgrades. Someone else manages it for you, so there are some restrictions, and additional features cost extra, but you don’t have to worry about anything (like features breaking, incompatibilities, downtime, etc). For a more in-depth analysis, please refer to this handy chart.
I used to blog with WordPress.org, but since joining Automattic about 3 years ago, I switched to WordPress.com, since WordPress.com is an Automattic product. It was great to get down in the trenches with our users and help to put out fires as I found them, but I found that my ability to code in PHP and JavaScript had degenerated quite a bit. There’s really no way to tweak a blog outside of CSS on WordPress.com, so no way eventually lead to no need, which lead to no want, which lead to a severe lack of practice and ultimately a loss of knowledge. Now that we have grown to 190 Automatticians, I figured there’s enough of us in the trenches on WordPress.com that I could go back to WordPress.org. Being back on WordPress.org frees me up to experiment with code again and break things on my blog, which I have been doing all weekend.
With the polite prodding of Mike Schroder over the years, I came back to my first-ever hosting provider, DreamHost. A lot has changed over the past nine years at DreamHost, all for the better. Resurrecting a nine-year-old dormant hosting account was no easy task, but Mika Epstein saved the day. It was like moving back into an old and much-loved home. Transferred a blog this size was rather rough and interrupted with frequent errors, but Michael Koenig of the WordPress.com Guided Transfer team had the magic touch and had my WordPress.com blog up and running on WordPress.org in a matter minutes. I don’t mean to sound like a commercial for one of our products, but the ability to sit back and let someone else who does this for a living (dozens of time a day) take charge of the whole situation is well worth the price.
There are a lot of handy built-in features on WordPress.com that are unfortunately left behind when you switch to WordPress.org, but it’s easy to either get them back or supplement them with something else. First, you’ll need Jetpack, which provides many of WordPress.com’s built-in features. Then, it’s just a matter of finding things to provide you with the security and reliability that WordPress.com is known for. Having talked with the folks behind Sucuri several times, I went with them for security. They’re good people, and you can trust them with the safety of your site. I also locked this down a bit more with a two-factor authentication plugin. Choosing what to use for reliable and automatic backups was an easy decision. I went with VaultPress, another Automattic product that’s well worth the price. Finally, you don’t have to worry about updates on WordPress.com, and you don’t have to on WordPress.org either, as long as you’re running the Automatic Updater plugin (from fellow Automattician Gary Pendergast).
In short, if you don’t like breaking things, stick to WordPress.com. If you want to experiment, WordPress.org is for you. DreamHost is great, and you’ll want to try Jetpack while securing everything with Sucuri, VaultPress, two-factor authentication, and the Automatic Updater plugin.
12 responses
Welcome back to the dark side.
It’s good to be back. I hear there are cookies. 🙂
Man, I’ve had my hosting at DreamHost since 2005 – I never got cookies! 😛
Welcome back. I’m not a fan of Dreamhost, but I’m a fan of running your own install of WordPress.
Thanks! 🙂
You should really try DreamHost again, it’s a much different and far better hosting service these days, plus there’s a 97-day money back guarantee. Grab an account and smack it around a bit with a test blog and some of your more demanding plugins. It’s still shared hosting, but it can take quite a beating.
Recently switched to Digital Ocean for most of my hosting and so far so good.
You need to enable the WP.com Like button so I can like this post. 😉
I have mixed feelings about the Like button, but I’m willing to try it again just for you. 🙂
[…] three years of blogging on WordPress.com, I moved back to a self-hosted WordPress.org installation so I could re-learn what I had forgotten and tinker […]
[…] three years of blogging on WordPress.com, I moved back to a self-hosted WordPress.org installation so I could re-learn what I had forgotten and tinker […]
[…] so I can break things and learn without fear. I still learned quite a bit in just ten days, like how to have a similar setup to WordPress.com, working with caching, choosing a stats program, and how to work with Genericons (which you can do […]
[…] wasn’t too long ago that I moved to WordPress.org after an almost three-year absence, and then quickly moved back to WordPress.com. I had a lot going […]