Move Back to WordPress11 May 2015
Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!
I launched my first WordPress blog in around 2008. After a constant configuring, I developed my first theme, and finally changed my site url/parmalink to
/%postname%/ structure. Then I felled in love with WordPress, until I meet Drupal.
The architecture of Drupal is amazing compared to WordPress (in the developer’s point of view). It is so easy to create a custom typed content in Drupal, while the WordPress at that time does not support custom content types. The ability to support unlimited number of content types and organize these content with view, which is added to Drupal Core since version 8, gives Drupal the potential to create any type of site. So I moved my blog to Drupal and also ported my WordPress theme with the help of Zen Theme. The theme development in Drupal is more complicated, and also makes me feel more comfortable (as a technical person 😉 ).
However, the maintenance costs of Drupal is too high (for a single blog), especially for a major version upgrade. Once I make my Drupal blog online, I become hesitate to play any other functions with Drupal. The time I moved to Drupal is around 2010. In the following chart from Google Trends, it seems that the popularity of Drupal never went up after 2010:
After that I become fall in love with command line tools, such as vim and git. And partly because of the poor UI of Drupal (I am not a good UI designer), I decided to move to Github Pages. Static page is enough for personal pages that you do not need to change frequently, and excellent to serve static documents for open source projects because the documents often managed by version control tools together with the source code. However, for a full featured blog, Github Pages is not a good input portal. You have to have at least git to write. It is true that you can edit content driectly on Github since it support web based edit and commit feature since 2011. And you can even use the Github Issues as a Blog engine. They are cool and geek, but not a good input portal as a personal blog.
My final solution is to move back to WordPress, after years of hanging around. IMO, the key feature that makes WordPress success is it’s on-line rolling upgrade model and out of box usage. You can benefit from the new features and get the secure updates more quicker. And today, the functionality of WordPress does not defeat that of Drupal any more. WordPress now also support custom content types, and have a lot of out of box content type with the default installation. What lacks in WordPress is it is not easy to configure a custom content type from the Web UI. But who cares? The developer? WordPress now have social network BuddyPress, forum software bbPress, and ecommerce software Woocommerce, and many more. WordPress is releasing Drupal like functions. But when can a production site use Drupal 8? This question makes me feel painful.