graeme_p - 11:40 pm on Aug 3, 2011 (gmt 0)
When all you have is a hammer...
Just because you can run a site on Wordpress, does not mean its the best solution. How easily could I port my encyclopaedia site back to WP without losing functionality? What about my client with a database of (a particular type of, in a particular area) luxury holiday accommodation? What about my Q & A site?
My main site started out as a section of a Wordpress site, and so it began life on Wordpress. It even got mentioned in other people's posts on WP running a site very different from a blog.
The problem is that sites like that (niche encylopedia) are much better off with a database structured to their needs: you ensure integrity of your data (rejection of duplicate data, transactions on updates....) and its easier to automate stuff like generating the index. You COULD write a plugin, but its easier to the site on top of a framework. I now use Django. As a bonus, the admin interface is better suited to the site because it reflects the structure of the data, is VERY easy to customise.
Its much the same with the other sites I mentioned. There is a better tool.
For simple hierarchical sites where I do not want much blog functionality, and would end up with a Wordpress site consisting mostly of pages, I would use a simple CMS like WOlfCMS. At the very least you get a UI geared to managing that rather than posts.
It is good to reduce time to implement, and increase time to write content, but an hacking an unmaintainable mess to make WP do something it was not designed to might cost you more time in the long run.