August 27th, 2006
5 Reasons Not to Use WordPress As a CMS
I wanted to get this out as fast as I could given that my post on 5 Reasons to Use WordPress (WP) as a CMS has been published. Why? Because I’d rather not get people too hyped up over WP’s non-blog content management system (CMS) abilities.
I’m not saying WP can’t work great as a more “web site-ish” CMS (I’m devoting a whole series on Using WP as a CMS after all!), nor am I trying to be a wet blanket, but there are a few things you really should consider before taking the plunge:
-
You’re Pushing It
WordPress was built to be a blog platform first, everything else second. So, everytime you push it to do something else, remember that you’re making it do something it wasn’t meant to do. You might very well go too far (think 20+ database queries on top of those WP normally calls, and I’m sure some of you rack in even higher numbers), and take a big performance hit. Or you just might break it trying to build a pseudo-Drupal out of WP by modifying core code… Ludicrous, but entirely possible. -
(Overly) Single Blog-centric
As said earlier, WP was meant to power blogs, so a lot of its features are optimised towards it. It’s hard to move away from a reverse chronological order post listing - meaning no alphabetical order, author-based order, etc., unless you use undocumented posts_* filters (and still have to hack around a bit more), or query your database to draw all your posts and sort them via PHP (it’s a pain for you and your server, trust me, especially since a lot of existing template tags, e.g. the_permalink(), may break in the process).In fact, each WP install is only meant to power one blog. No multiple blogs under one admin panel unless you use hackish plugins (see No. 6), which are mostly ugly to implement (no offense intended to the plugin creators!). Even then (or if you use WordPress Mu), it’s highly difficult to draw data from your other blogs, e.g. draw list of authors with their posts from another blog. And your Manage Posts panel doesn’t allow for listings by author for the multi-blog sort of administration community sites require - unless someone updates the Enhanced View plugin for WP2.
-
(Overly) Simple Post/Page/User Management
WP’s user-friendly admin panel (which stems in part from its simplicity), while great for running a single blog, would be insufficient for complex tasks, e.g. community sites, education portals, etc. For starters, by default, there’s no mass editing of categories (plugin available), custom fields, or comment enabling/disabling on your posts. Edit: To clarify, per-post custom fields and comment enabling/disabling are available, it is the batch editing of them that is not available.It’s a little better for pages given the Mass Edit Pages plugin, but still not enough. I’m sure you’ve noticed how hard it is to deal with your pages once they number in the hundreds… (Pages+ plugin helps, but not sure if WP2 version available). The same things apply with user management. And to my knowledge, WP also lacks a common user authentication system, e.g. LDAP,
which I think is going to be pretty difficult to implement without editing some core code.Edit: Someone slap me. Completely my mistake here. There are already LDAP plugins (an updated version) available - though I can’t seem to find a WP2 version. -
Single and Simple Category Tree
You only have one category/taxonomy tree unlike more community-based CMSes like Drupal. This seems minor in comparison with the previous three, but it does mean that you can’t have one category tree (called a vocabulary in Drupal) for your news posts and another for your blog posts - each under their own permalink structure. You can simulate multiple category trees by using sub-categories, but it will still lack manageability and flexibility.Moreover, all you have is a simple category tree (albeit with nesting available) - without associations between categories on different trees, etc. No related categories, synonyms, etc. Edit: As Matt Mullenweg notes, it’s possible to simulate a lot of associations via simple queries - though I’m sticking with my original analysis that WP’s taxonomy system wasn’t meant for (very) heavy lifting.
- (Relatively) Rigid Permalink Structure
Changing your permalink structure in WP normally involves only the general URL structure of your posts, e.g. whether it’s /year/month/date/ or just /postname/, and changing the prefix of your categories. So far, there’s no simple way to change the permalink structure of a single post or page, or set your categories to run without any prefix! You might have noticed that categories can’t go under yourblog.com/category-name/ because it could conflict with a page under yourblog.com/page-name/. There is a hackish way (see comments unde post) of doing it, but it’s not dependable - and should be used as an indicator of WP’s rigid permalink structure. Edit: Edited to add emphasis on “no simple way”, rather than just “no way” since if you’re persistent enough, you can always tinker with wp_rewrite.
All this might look a bit harsh considering how good WP already is, but if you’re thinking of using WP for very specific or very complex tasks, you’ll have to weigh it against more suitable CMSes - sooner or later.
And truthfully, I’m still sure I’ve missed a couple of points (at least), but try as I might, this is all I could come up with. Or… it could just be that WordPress has everything else built right for our “tweak-ish” desires.
Update: Rex points out that WP also lacks robust workflow management features - though he’s also right that such features are lacking in other open source CMSes as well.
Update 2: Qualified many points due to uncertainties /mistakes pointed out by Matt.
If you found this post useful, keep updated with future posts by subscribing to blogHelper (for free) through RSS or email.
89 Comments
August 27th, 2006 at 10:31 pm
WordPress was always designed as a simple CMS for people smart enough to not get mired in the things that CMSes usually get mired in.
Ordering of pages can be done per-page with custom page templates, per category with custom category templates, or per post with custom post templates. (Check out the template loader, you can do things like create category-123.php in your theme directory which will be used for category #123.) It can also be done in the query string itself. It wouldn’t be hard to write a plugin to trigger the various scenarios you describe based on the presence of a category or tag.
“Multiple blog” goals can often be satisfied with a single blog and some create category use. See the new Gigaom.com for an example.
To clarify one of your sentences, we do have custom fields and per-post comment enabling, but as you note there is no interface to batch apply those settings currently.
WP has a completely pluggable authentication scheme. A search for “WordPress LDAP plugin” will reveal no fewer than two plugins specifically for that purpose. (I haven’t had cause to use them myself.) It includes provisions for a combined user and usermeta system across multiple blogs, including remote host authentication in other applications like bbPress.
I don’t know if I’d call our category/tag system simple, as you can do quite a bit with the many:many relationships and hierarchy. On WordPress.com we’re able to pretty easily get “related” tags just by a simple query. I think bottom-up will still be the best mode here, rather than complicated top-down taxonomies.
Filtering permalinks and hijacking URLs for custom use needs to be documented better, but if you buy Ryan a virtual beer he can walk you through it. There was also a discussion on the hackers list about this recently.
Of course where we do suck, we should probably look at adding some filters and hooks.
August 27th, 2006 at 11:32 pm
[…] After all the hype of being able to use WordPress as a CMS, blogHelper has posted 5 Reasons Not to Use WordPress As a CMS: Im not saying WP cant work great as a more web site-ish CMS (Im devoting a whole series on Using WP as a CMS after all!), nor am I trying to be a wet blanket, but there are a few things you really should consider before taking the plunge. […]
August 27th, 2006 at 11:42 pm
No dispute on your first point. It’s basically the whole purpose I wrote this post.
Aiks, here’s where my understanding blurs. I think I understand the template loader system pretty well, but I don’t think I raised any issue with WordPress’ powerful templating system at all. I believe my issue was with WP’s default reverse chronological-ordered Loop, which is pretty difficult to reorder using different approaches, e.g. alphabetical. I apologise if I’m not seeing things right here.
On the “multiple blog” scenario, “creative category use”g
Oops, yeah I can see how my mass editing categories, custom fields, etc. could have been misintepreted. Thanks for pointing it out.
On the LDAP, completely my mistake. I must have missed it out.
Again, I’m fine with a bottoms-up approach, but I feel it is justified to point out that taxonomy in WP isn’t the most “powerful” among CMSes - and there’s really nothing wrong with that except that it’s something I feel should be noted.
Lol, maybe I should.
Though I clearly messed my own point up. It was supposed to be “there is no simple way”, since it was always going to be possible to play around with wp_rewrite.
All in all, thanks for the great comment. Time to do some corrections.
August 28th, 2006 at 2:17 am
Thanks for the Pages+ plug - it does work with WP2.
We have Wordpress running a site with >2,500 pages. With the help of a few plugins (Pages+, WP_Cache etc) it runs brilliantly. All the points you mentioned can be achieved with a little script editing or plugin use. The only thing we struggled with was the inability to have more than one content area on a page - it can be done, but what it comes down to is that wordpress is excellent at what it does and very good and what it can do.
August 28th, 2006 at 5:15 am
Nice post, and you do have a point here. Wordpress isn’t a regular CMS, it’s a blog tool. Then again, if you do know what you’re doing then it’s not a big deal to get it working for most purposes. Problems only occur when you need to do something really different but since it usually involves coding anyway you can always make a plugin of it. I’ve taken a huge site and converted it to Wordpress, and with the help of some category templates and the marvelous Ultimate Tag Warrior plugin I got it right. WP Cache helps me keep costs down (working like a charm) and a combination of Akismet and Spam Karma 2 keeps the monsters at bay. There’s not so many weird things here, no core file hacks at all - just plugins (some custom-made, granted) and suddenly I no longer needed my fairly complicated admin tool, made in-house by people who knew what they were doing.
Still, I don’t disagree with you. Pros and cons should always be pointed out, however I do feel most CMS needs can be fulfulled with Wordpress, and ending up a far better work tool than Joomla for instance.
August 28th, 2006 at 5:59 am
[…] More Links on this topic: bloghelper.is-there.net/5-reasons-not-to-use-wordpress-as-a-cms/ bloghelper.is-there.net/using-wordpress-as-cms/ bloghelper.is-there.net/at-bloggingpro-5-reasons-to-use-wordpress-as-a-cms/ Tags : , , By r00t 4orce August 28, 2006 9:52 am Comments : […]
August 28th, 2006 at 7:20 am
[…]All software have their pros and cons. Though WP is – no question – a great blogging app; it is by nature no CMS. Why go through all the hassel with searching for the right plugins, hacking the backend and reading through pages of tutorials? Rather save your time and dedicate to learning a solid CMS.
August 28th, 2006 at 9:29 am
First, let me thank you for the information you are posting. This exact subject has haunted me for days now. I’ve been trying to decide between Drupal and Wordpress, and so far Wordpress is my choice. I’m looking for basically a blogging/forum system now (which i’ve implemented with wordpress using the Simple Machines Forum plugin), and a more robust CMS later, as the site grows and evolves.
I’m new to the whole CMS scene (minus a lot of experience with CommunityServer.org’s system), and am finding Wordpress so much easier to grasp than Drupal, Mambo/Joomla, etc.
I’ll be paying close attention to your blog over the course of this series. Please keep the info coming! Perhaps you might look at some specific plugins people are using to adapt Wordpress into more of a CMS?
August 28th, 2006 at 9:50 am
Yes I agree with you, there are far better alternatives to be used as a CMS. Drupal does a much better job than wordpress. Even the inventor of the HTML — Tim Berners Lee — uses Drupal for his personal Blog.
Thank you for sharing your thoughts with me !
August 28th, 2006 at 10:16 am
[…] http://bloghelper.is-there.net/5-reasons-not-to-use-wordpress-as-a-cms/ […]
August 28th, 2006 at 12:30 pm
As a passionate Textpress user and want to be Drupal user I always love to read about WP as a CMS. When I set up my local news site I wanted simplicity and performance. I did not want a ‘it can do everything you want’ solution.
I decided not to use Drupal because of resources and learning curve.
I decided not to use WP because of its main advantage: simplicity
I need sections for my page like a newspaper has sections. That killer argument made the decision towards Textpattern easy. As every section can have its own CSS and page templates it is very easy to have completely different look and feels in different sections. I would really recommend TXP to everybody who is looking for a CMS which can easily mimic a blog (by default it does behave like a blog system).
August 28th, 2006 at 12:32 pm
Sorry! Textpress = Textpattern
August 28th, 2006 at 8:40 pm
Not at all, I’m really looking forward to seeing what you write here.
I think the things you highlight as difficulties are STILL difficulties even if they’re possible — the fact that you, as a WP enthusiast, weren’t able to easily accomplish the tasks you set out to do is indicative of problems.
I would love to see the road bumps you find translate into core improvements in WP. For enhancements that may not be appropriate for core, it could be really nice to have like a “CMS Helper” plugin or plugin pack. If you’re passionate about this issue, you have a real chance to affect the WP community in a non-trivial way.
August 28th, 2006 at 11:24 pm
Adam: Not much for me to disagree with, except that I feel “little” script editing can be a matter of perspective. If your purposes happen to only require plugins that already exist, then yes, you barely need to do anything. But if they haven’t been written…
TDH: You just made my day. That’s exactly what this post was written for.
Alex: I’ve written 5 reasons why you might want to.
Redth: Yeap, that’s what will happen as the series progresses. I’ve already started with portfolio site and I’ll go on with others as time permits.
Maria taking pictures: Oops, I think I gave the wrong picture. I’m not really trying to push other CMSes over WordPress. Just trying to point out some possible considerations if you’re trying to use WP as a website CMS.
Markus: I’d still like to recommend WordPress to you though. Multiple content sections can be simulated with WP too.
August 28th, 2006 at 11:35 pm
Matt: Thanks, and I’d love to try, though only time will tell how strong my passion is.
Let’s see how far my series on this goes first.
August 29th, 2006 at 4:29 am
Great stuff, reading both pro and con articles. A good insight into what to expect if going down this route with WP.
I’m a tweaker (but no coder) and I’d love to change bits and pieces on my WP to accomplish what I want - which is no advanced CMS stuff. Jst a few tweaks here and there.
This is going to be a great series - and if you can spark some plugin developers interests to create cms-like focused plugins then you’ve done a stellar job of moving WP forward.
BTW, can anyboday tell me how GigaOm achieved their subdomain categories? A plugin?
August 29th, 2006 at 10:17 am
Martin, try this Subdomain plugin. I haven’t tested it out yet though.
August 30th, 2006 at 11:45 pm
[…] read more | digg story […]
August 31st, 2006 at 10:58 pm
well, I honestly think that WordPress would be enough for simple, brochure-type sites that don’t require extensive features. For sites that need more “stuff”, CMS such as Drupal would be a safer bet.
I am not sure about stability though… I haven’t tried WordPress for a featured-laden site (ie. sites with an extensive photogallery, forum, member reg, etc.). I guess I haven’t had the guts to risk my client’s sites yet. What if it fails? Will WordPress be able to handle that much load?
I used WordPress for my little ecommerce site that doesn’t require a shopping cart: Filipino Artisans. (thanks for the link by the way hehe). I have my “info” pages such as the About Us type of thing, and i have my news area and “product page” by using posts. Simple, yet, fulfills the purpose. In the long run I might have to change it, but for now, I’m fairly satisfied with using it as a CMS.
September 6th, 2006 at 11:17 pm
Stability is a good point since I’ve not heard of any tests on a featured-laden CMS-type WP site either (if anyone has, I’d be thankful if you pointed me to any). But WP does scale for conventional blogs, so there’s a good chance it’ll scale for any CMS implementation as long as you play by the rules (keep away from core code) and optimise your installation (page and script caching, etc.).
September 13th, 2006 at 11:38 pm
[…] 5 Reasons Not to Use WordPress as CMS […]
September 15th, 2006 at 2:52 pm
[…] Bloghelper har en informativ post om hvorfor man ikke bør bruke WordPress som CMS. Noe å tenke på for alle hobby-designere der ute. Eller for webmastere generelt. Tanken er; ikke gjør noe med WordPress som det ikke er beregnet til. Mens du er i farten med design og sånn, så kan du alltids kjøre en tur innom Theme Viewer, sånn for å finne litt inspirasjon. Lovely Blogs har også en del å kikke på. En ordkunster av de sjeldne: Davy Wathne. Nå med egen blogg faktisk. Handler, overraskende nok, om fotball. […]
September 19th, 2006 at 2:02 pm
Thank you for the post. This information gives me thoughts for future.
Best regards,
Tomas
September 21st, 2006 at 7:46 am
[…] 5 Reasons Not to Use WordPress As a CMS I’m of the mind that WordPress is a terrible CMS, and a great blogging platform. Textpattern would be the best blogging system for me, and yet I’m using WordPress as a CMS. Go figure. (tags: wordpress cms tips textpattern) […]
September 25th, 2006 at 3:02 pm
[…] Nota: Questo articolo è la traduzione in italiano di 5 Reasons Not to Use WordPress as CMS il terzo di una serie di post pubblicati su blogHelper che spiega come trasformare WordPress in un sistema di gestione di contenuti. La traduzione viene pubblicata qui con il permesso dell’autore: Ang Zhuu Ming. […]
September 25th, 2006 at 5:27 pm
[…] WP ha una sola struttura di Categorie A differenza di altri CMS come Drupal, WP presenta un’organizzazione delle categorie molto semplificata. Ad esempio, non è possibile creare un’albero di categorie per una sezione di notizie e un altro albero per la sezione blog - ciascun albero con la propria struttura di permalink. Questa cosa si potrebbe fare tramite le sottocategorie, ma perdesti parecchio in termini di gestibilità e flessibilità. Tutto ciò che abbiamo è un singolo albero di categorie senza nessun tipo di associazione tra categorie appartenenti ad alberi diversi, ecc. Non ci sono poi categorie correlate, sinonimi ecc sebbene ciò si possa fare grazie a qualche query supplementare. […]
September 27th, 2006 at 4:06 am
[…] WP ha una Sola Struttura di Categorie A differenza di altri CMS come Drupal, WP presenta un’organizzazione delle categorie molto semplificata. Ad esempio, non è possibile creare un’albero di categorie per una sezione di notizie e un altro albero per la sezione blog - ciascun albero con la propria struttura di permalink. Questa cosa si potrebbe fare tramite le sottocategorie, ma perdesti parecchio in termini di gestibilità e flessibilità. Tutto ciò che abbiamo è un singolo albero di categorie senza nessun tipo di associazione tra categorie appartenenti ad alberi diversi, ecc. Non ci sono poi categorie correlate, sinonimi ecc sebbene ciò si possa fare grazie a qualche query supplementare. […]
November 19th, 2006 at 8:22 am
[…] Wordpress est très souple, facile d’utilisation, en plus je le connais pas mal. Problème, il est vraiment trop orienté blog. J’ai bien trouvé quelques articles qui expliquent comment transformer Wordpress en véritable CMS mais détourner la vocation première d’un outil pour en faire autre chose, c’est souvent s’exposer à des problèmes que l’on avait pas vu venir au début du projet. […]
December 21st, 2006 at 5:46 pm
Hello!
I didn’t see this post until today but I already read 5 Reasons to Use WordPress (WP) as a CMS when Matt mentioned it in his blog. I left a message there since I used WordPress for my weggis.net site. Would you like to take a look at my sites - weggis.net, sehdi.com and pandan.ph especially on how I use WordPress as CMS. I’m just experimenting and it works. I’m still working on the other sites.
January 18th, 2007 at 6:48 am
I am currently using WP as a CMS on a couple of sites I maintain, but one of the main reasons that I would steer clear of it if I wanted a true CMS is that it does not have post and page versioning. Now, to my knowledge, neither Drupal or Joomla feature this either, but some of your high-end proprietary CMSs do. If someone wanted to create the ultimate WP CMS plugin, they would develop one that uses an extra table in the database to maintain old versions of posts and pages. I guess the database could potentially get unwieldy, unless somehow only delta changes were saved.
February 25th, 2007 at 12:00 pm
[…] There are pros and cons to using Wordpress as a CMS, just as there would be with any other application, even if it’s specifically intended as a CMS. For example, complexity is one disadvantage to choosing Drupal, which in my opinion was entirely unimpressive. Configuring Joomla was equally complicated, although easier to get up and running with initially. ModX so far has been the most impressive, and certainly the best looking of the three. […]
March 19th, 2007 at 2:41 pm
@Jason: Very true what you say about versioning.
Another thing is that you have no choice of having the productive online system being another part then the editorial system.
But Textpattern at least supports different roles which is important if you work on a site with a team of contributing people.
March 20th, 2007 at 4:42 am
[…] 5-5 Reasons Not to Use WordPress As a CMS by ZMAg […]
March 25th, 2007 at 10:29 am
Matt,
Well one thing we know for sure is WP will continue to change and will be a must better CMS and whatever it is missing we will soon have a plugin to fill the gap.
In short, WP is great at being s CMS.
With the constant changes i use a Free service from www.findallabout.com
I can create custom PDFs or get a weekly update simply by
http://www.findallabout.com/search.php?keywords=wordpress
I get PDFs every week and it is easy to follow the fast changing world of WP.
March 25th, 2007 at 11:47 pm
Got started in blogging and Im loving it, just setup my blog. Just learning as much as I can could do with some useful links.
July 6th, 2007 at 12:37 am
[…] elencate 5 motivazioni secondo le quali Wordpress può essere anche usato come CMS ma anche da quest’altro testo dove si afferma il […]
July 16th, 2007 at 5:13 pm
I’m amazed at how many articles mention using it as a CMS, without touching on key functions like versioning or workflow control (approval, publishing, etc.)
August 17th, 2007 at 2:01 am
It’s very good article. Great site with very good look and perfect information.
August 22nd, 2007 at 11:29 am
I would make sure that I was upgraded to XP SP2 before trying to restore an XP SP2 backup, however, until after the backup was restored
August 26th, 2007 at 6:49 am
[…] then change back. There are many other Wordpress vs. Drupal articles you can read here, here, here, here, and here. Make your own decision in the Wordpress vs. Drupal debate as pertains to your situation, […]
August 30th, 2007 at 7:59 pm
thanks.
September 9th, 2007 at 8:46 pm
thx for the great stuff. saved it! greetz from germany
September 13th, 2007 at 11:26 am
Thanks for the good information - now I think about using WordPress or not…
September 16th, 2007 at 3:49 am
thanks for very interesing informations. great job. thanks
September 17th, 2007 at 7:20 pm
thanks for very interesing informations. great job. thanks
September 19th, 2007 at 5:30 am
Thanks for the good information - now I think about using WordPress or not…
September 20th, 2007 at 2:18 am
thank you
September 20th, 2007 at 2:43 am
evden eve
September 20th, 2007 at 2:44 am
thank you
September 20th, 2007 at 2:44 am
wery good web sites
September 20th, 2007 at 2:45 am
evden eve nakliyat
September 20th, 2007 at 4:09 am
wow i cant believe that these people took the time out to make these! im absolutly impressed. GREAT ARTICLE
September 21st, 2007 at 1:11 pm
Thanks for the good information - now I think about using WordPress or not!!!!
September 21st, 2007 at 1:12 pm
I would make sure that I was upgraded to XP SP2 before trying to restore an XP SP2 backup, however, until after the backup was restored…!
September 21st, 2007 at 5:09 pm
thank you admin. it is good works. i am reading all
September 25th, 2007 at 3:25 am
thanx
September 27th, 2007 at 11:33 pm
Kapışın lan gidiyo :D:D
September 28th, 2007 at 7:08 pm
Thanks so much, i prefer Joomla and Typo3!!!
September 29th, 2007 at 1:09 am
thanks for your great work!
October 3rd, 2007 at 6:59 am
realy nice article, great site, thanks for very interesting informations
October 25th, 2007 at 3:36 am
Very good post, and comments as well. I think that I agree with you on a number of points – if you push the platform too far, you will break it. All that effort might be saved by simply doing something on your own that’ll do what you want it to do. That might be debatable, though.
I think WordPress deserves a standing ovation for the strength of their application, their service, and awesome attitude. The truth is that you CAN use it for a tremendous amount, and they have really done an excellent job with practically everything. But, as you say, if you push it too far… well… you might end up with something hardly close to what you were hoping for.
October 29th, 2007 at 11:23 pm
I have nothing against the points you listed. I think all of those are the reasons why most web sites nowadays were previously built out of WP.
November 3rd, 2007 at 4:46 am
Thanks for article.
Regards,
Mehmet.
November 5th, 2007 at 1:13 pm
thanksss very good site..
November 9th, 2007 at 5:35 am
[…] 5 Reasons Not to Use WordPress As a CMS ( bloghelper.is-there.net ) […]
November 9th, 2007 at 7:18 am
I disagree - WP is a CMS as all blog platforms or content platforms are. Content management system, you are managing content - it is the style of the layout and design that has gotten WP very popular to be a Blog Platform.
Hence I can say Article Directory CMS does not even have to be an article directory system, it can be use as a content platform because it is a CMS - I once used an article CMS because it was better and easier to manage than drupal or joomla, then I found WP - the best CMS platform out there. it can be easily manipulated and arrange to be a Content Management tool as it was made to be.
November 9th, 2007 at 11:33 am
Hey… just where’s the “Blog” in WordPress? I really don’t see it anymore — in many sites we do for clients… and elsewhere on the internet. Take a look at the article, “Where’s the Blog in WordPress”, and you’ll see some examples that make my point:
http://webhelpermagazine.com/?tag=wordpress
I noticed the original article here is over a year old, so perhaps you have a different opinion now. It’s interesting that WordPress just one a SitePoint contest — for a CMS!
I think your points are well taken, but a) WordPress is whatever you want it to be, b) WordPress is evolving way beyond a blogging platform, and c) Your general point that WordPress is “simple” is precisely why it makes such an excellent CMS for non technical users.
Regards, Scott
November 16th, 2007 at 12:22 pm
Very nice article. I really liked it a lot and it gave me a few good pointers. Thanks!
December 21st, 2007 at 2:06 am
very good blog
December 21st, 2007 at 2:07 am
good good
December 21st, 2007 at 2:08 am
good article thanks
December 21st, 2007 at 2:08 am
very good
January 7th, 2008 at 3:46 am
My site-builder proposed wordpress as cms: http://www.theaterbureauspot.nl.
So it was made. But now Google looks at all the pages but like the posts the most. And that is only part of a guestbook. My old html website was better to find. Does anuone have a good proposal to make my site better googabale or are you right and is Wordpress a blog and you don’t use it for cms? I think only allready for the google thin, you should use statistic html pages? Or am i wrong?
January 10th, 2008 at 10:49 pm
super article. thanks
January 18th, 2008 at 7:17 am
evden eve nakliyat
January 30th, 2008 at 8:18 pm
dfdfd
February 28th, 2008 at 10:20 am
[…] are reasons not to use WP as a CMS, but there are also reasons to use WP and many tutorials on how to do so. The fact is, […]
March 4th, 2008 at 1:28 pm
Thank you for the post. This information gives me thoughts for future. Of all the five reasons mentioned I must agree. I you need more I would advise Joomla CMS
March 5th, 2008 at 2:13 am
[…] Bloghelper: 5 reasons not to use wordpress as a cms […]
March 7th, 2008 at 3:59 am
[…] 5 Reasons Not to Use WordPress As a CMS […]
March 17th, 2008 at 6:29 am
I would still recommend wordpress i use it for my African safari and africa vacation blog and it has surely served me quite well.
April 7th, 2008 at 1:02 am
great site, thanks
April 15th, 2008 at 10:03 pm
Very good post, and comments as well. I think that I agree with you on a number of points – if you push the platform too far, you will break it. All that effort might be saved by simply doing something on your own that’ll do what you want it to do. That might be debatable, though….
April 20th, 2008 at 6:23 pm
Thank you for the post.
April 22nd, 2008 at 12:43 am
As by design WP is a blog so use it for what is was made. BTW: Recently I stumble over drupal and it seems to be a very good CMS.
April 25th, 2008 at 5:12 pm
great site, thanks
May 5th, 2008 at 9:57 am
thanks for the great article…
May 5th, 2008 at 9:57 am
thanks…
May 6th, 2008 at 1:03 am
thenkss
Leave a Reply