I was saying this exact thing: WordPress is just a CMS, which severely limits what you can sanely do with it. You won't build a PSP in a CMS. That was my point.
I think he is more referring to the portability of content within Wordpress. If I am using a platform to manage content, I'd like to think that I could easily port that content wherever I want.
Building anything that rivals Wordpress in terms of features, extensibility and ease of use is a massive undertaking.
Building a CMS is relatively easy.
Building a CMS that does everything WP does is difficult.
Building a CMS that does everything WP does whilst still remaining easy to use is incredibly difficult.
There are plenty of blog alternatives out there - but few that you can turn into virtually any other kind of system in just a few clicks. WP can be turned into a whole host of other 'types' of website and you don't need to know anything particularly technical in order to do it.
Even installing Wordpress itself is just a few clicks (depending on your hosting provider).
WP is terrible in lots of ways, but in the ways that most people care about, it does a reasonable-to-good job.
WordPress core is not trying to be all things to all people. But can he tell me a CMS that makes it simpler to build out the requirements for a vast majority of the websites in the world?
If you are looking for a custom feature set on a project that you claim WordPress doesn't meet your needs, then build a custom CMS for the job and charge appropriately. WordPress allows organizations and individuals to have massive power in their website for a fraction of the cost of a custom CMS. And in comparison to a custom CMS, it gets a great deal of testing.
WordPress is always looking for new contributors, and if your solution isn't something that works for core and the WordPress core philosophy, then you can extend your idea via a plugin.
And in the author's list of things WordPress "has either no, or severely limited" support for, he is way off the boat. There are a slew of highly talented developers that either having working solutions for or are working on almost all of those things, and more.
Wordpress is a blogging engine that can be hacked to work as a CMS. Thousands of mostly low-quality plug-ins with questionable security and unproedictable compatibility issues when used with other plugins.
If you want to install a theme and not adjust anything it’s ok-ish. For anything more complicated I’ve found Wordpress unworkable.
I feel myself lucky to have discovered craftcms - well architected CMS with flexible content modeling. Free for a single user.
And I don't understand Wordpress as a CMS. It's frankly a terrible one as well. Poor internationalization support, doesn't meet government accessibility requirements, its non-structure makes maintenance and teamwork almost impossible, its plugin structure is a landmind, terrible (no) dependency management, encourages deployment via FTP, and a terrible security model.
I'm not a Python guy, but Plone kicks its ass in pretty much every way as a CMS.
Wordpress can't seem to choose what they are- and they fail miserable from a technical perspective (yes, I know they have a huge market share, but I'm not one to believe that the markets actually pick the best option. McDonalds burgers are not the height of cuisine).
Exactly. I don't keep up with Wordpress too much, but my perception is that you should go with something like Drupal (or other proprietary options) if you want a platform fully capable of being a CMS.
That said, any CMS will struggle with the challenges that he lists. It's not some sort of magical entity where you turn it on and it's perfect.
I wouldn't count wordpress as a CMS personally, more of a super blog. Drupal is much more powerful and flexible (out of the box -- you can modify both)
Wait so he's complaining that a free piece of software that is designed to "create a beautiful website or blog" (from Wordpress.org) doesn't cut it as a high powered CMS?
I think if we're honest, wordpress is a blogging platform and if you try to deform it into your own little niche needs, you need to accept the inherent risks.
This guy seems to be arguing that Wordpress should turn into a Drupal-like app, which it was never designed to do. Although I am also guilty of using WP for CMS on some simple sites, this is mostly due to convenience of installation and (mostly) ease of use for clients. I don't think most developers who use WordPress seriously consider it a "professional" CMS solution.
On the other hand, the alternatives kind of suck. This author doesn't even recommend one, which is odd considering he purports to have recommended WP to everyone for the last 4 years. Most other CMS solutions I've used over the last years have either been vastly overkill and overly cumbersome, or still severely lacking the features he describes as lacking in WP. It usually turned out almost as easy to develop your own skeleton CMS depending on the site's needs.
Using WP as a CMS is like trying to use a Honda Civic to pull a boat through the mountains. Yeah, you can probably bolt on some parts to get the job done, but eventually it's going to end up a big smoking pile and you're going to have to buy the truck you should have used in the first place.
Maybe the poster means wordpress.com is not capabale enough? To me, Wordpress is a self-hosted platform and overly capable as a blog. It's also pretty capable for any other CMS-based site.
You can treat WordPress as a PHP based content management framework, and that is in fact what many people do. Also he is in fact using a Clojure web framework- Compojure. In anycase, contrary to what you are saying, his point is coherent.
I was saying this exact thing: WordPress is just a CMS, which severely limits what you can sanely do with it. You won't build a PSP in a CMS. That was my point.
reply