+1 for wordpress for the ammount of plugins available that let you customise almost everything. For this same reason more and more "big" sites are relying on wordpress as a CMS -1 for wordpress for the code itself. I've written a few plugins for Wordpress myself, and I found the following "problems": - Non object oriented API - I'm so used to having all my functions encapsulated in classes and objects that old style coding just looks "dirty" to me. - No true plugin api. Plugins are developed using hooks, instead of a proper plugin api. This means that as long as you use the right hooks you can do pretty much anything you like in any way you like it. Although it sound's like a powerfull concept, try picking any random 3 plugins and look at the code. You'll see that every single one of them is coded in a completely different way! - Lack of good developer documentation. You need to do lots of things by example, and as I said there's no 1 example to follow, as everyone does their own thing. For all these reasons I'd try to stay away from WP as a CMS, specially if you're planning to add your own code on top. Still, as it was said here before it does the job and most of the time it does it well.
[ Now playing: "Culpable" by Vicentico from "Vicentico" ] On 13/01/2009, at 12:58 PM, Sid Bachtiar wrote: > Templating for example seems to be a hit or miss affair - you need > to create > a full theme to get any template changes happening and then what > happens if > you want one page to look different from the rest? I don't think so. It's not hard at all, for example you can create something like tmp.cat-5.php to give all posts under category 5 a different look (I can't remember the exact naming convention, so don't quote me on this example). Wordpress is largely built around the concept of pages and posts. A simple example of a Wordpress website that doesn't look like Wordpress blog: http://wn.elim.org.nz/ On Tue, Jan 13, 2009 at 12:44 PM, Paul Bennett <[email protected]> wrote: > Hi yeosteve, > > In my experience it's harder to get wordpress to behave *not* like a > blog > than it is to work with most of the other cms's mentioned here. > Templating for example seems to be a hit or miss affair - you need > to create > a full theme to get any template changes happening and then what > happens if > you want one page to look different from the rest? CMS's like > silverstripe > and expresison engine provide massive flexibility with templating in > comparison to wordpress, as wel as the ability to have template code > in one > central file, rather than needing to create 5 different bits in > order to get > one page working coherently. > > Do you have any examples of (non-blog) sites running wordpress as > cms? I'd > be interested to see. > > Having said that, for running a blog, I've found nothing better than > wordpress yet :) > > Paul > >> > -- Blue Horn Ltd - System Development http://bluehorn.co.nz --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
