I’ve moved the blog from WordPress.com to WordPress.org, which has many more features, options and added stability and security. The layout is still essentially the same, although I upgraded the theme from Twenty Ten to Twenty Eleven. I looked at dozens of others, but stlll came back to this as my favourite. Simple and clean, but with lots of modification options.
The domain / url is still the same: cccrn.ca.
I’m still tweaking things a bit in terms of plugins and widgets, etc., but the basic look is done.
Posts now have a “comments bubble” in the upper right corner for adding comments (and comment count) or you can still do it using the link below each post. There are also sharing buttons for Twitter, Facebook and Google+, the primary social services, as well as email and print, below each post. Also follow and subscription widgets for Twitter, Facebook, rss and email in the sidebar. I’ve also added widgets for the latest Twitter updates, as well as an animated category cloud widget in the sidebar.
Please note that since the previous default email subscription service with WordPress.com isn’t part of WordPress.org where the blog is now hosted, I’ve changed email subscriptions back to Google’s FeedBurner service, which also publishes the RSS feed, and is still easy to use and reliable. If you were previously subscribed to the old service, please resubscribe to the new one. People who were originally using Google’s FeedBurner service before that are still subscribed. Email updates are still basically the same, just whenever a new post is added to the blog.
I’ve also added Google ads as a source of extra revenue to help support the blog (when clicked), but trying to not clutter posts or pages too much at the same time.
The formation archives are still in the process of being updated as well, I just haven’t had time to work on it more yet, sorry. It is on my to-do list, though!
Note: There seems to be an issue with the Google+ share button not displaying properly with older versions of the Firefox browser and possibly the Internet Explorer browser, as well as on iPad and iPhone. From what I’ve read, this is a fairly common problem, but seems to be ok with the Safari and Google Chrome browsers.