When this blog was born, at the end of 2009, I opted for WordPress to contain and manage it. Now I have begun to implement the functionality on my own and got rid of the framework. Why?
There's no need to compare the wrath of WordPress
and my own humble programming skills. WordPress is a great blog and content management framework. I use it for some of my private customers at the moment and I will keep it in the future. No question. It has many advantages, especially if you want to set up a website rather quickly, with many features and less programming. Widgets, pages and categories are exactly what an association's website needs. And it's free. So the functionality is not the reason why I changed my mind.
On the other hand, the layout is a very important topic for me. I'm a perfectionist and I want my website's design to match my concept, even on pixel level. So I win here.
WordPress has the best functionality, but it will never ever be able to provide me the architecture I have in mind from the beginning. I have no fun digging in someone else's CSS to make it look like I want to. I hate "reverse engineering", I prefer to create. Again, doing it my way seems the right thing to do.
My scripts won't stop working when a new WordPress version comes out. My RSS feed won't suddenly decide to pollute my Twitter account with useless updates.
The spam folder seemed to be the mostly used part of my blog when it was based on WordPress. Let's see how real humans can enjoy the hand-crafted one.
What changes for you
The typical blog stuff is gone for now: categories, calendar, tag cloud, search field, blogroll, comments, eMail newsletter, etc. We'll begin with a basic paging that lets you navigate to the previous or the next article. Of course, I'll add more functionality as time goes by and keep you updated.
Although I will continue to work with WordPress for and with others, I won't use it anymore for my own blog. If you're missing some specific functionality, don't hesitate to let me know.