WordPress as a CMS? As an App? For the Enterprise?

In a recent post by Morten Rand-hendrikso, he wrote an extensive piece about WordPress and its many facets.

WordPress for blogging? WordPress as a CMS? WordPress as an application? WordPress powering a network of sites? WordPress as Software as a Service? There are many more ways you could use WordPress.

WordPress is celebrating its 10th birthday, and it’s been a wild ride. Morten discusses killing an ant with a tank and how WordPress has been taking on more qualities similar to what Drupal previously represented.

His piece sparks a very interesting conversation. Should WordPress be forked for different purposes?

Those of you who have been around with WordPress long enough, you know that there used to be WordPress Multi-site (WPMU), and that branch was eventually merged into WordPress core in the major release of WordPress 3.0.

This approach of forking off different use cases of WordPress makes for a certainly interesting proposition. It would cause more code maintenance, just as WP and WPMU had caused when they were being developed in parallel.

If WordPress were to branch off and create a WordPress Blogger branch, a WordPress CMS branch, and maybe a WordPress Network branch, how would this positively impact the WordPress ecosystem and community as a whole?

I think it would actually be a positive thing. I’ve personally used WordPress in many different ways, but I started out using it just as a blogging platform. I’m currently in development of extending WordPress to act more like an application. I am certainly finding that some things are limiting, but largely I can extend it to do what I need to.

Morten continues on to talk about WordPress Enterprise and WordPress Network as an extension of WordPress Enterprise. I whole-heartedly agree with his points.

WordPress has a huge potential to be so much more than what it is today.


  1. By Azim on

    I think it’d be an interesting idea to have these 3 (or maybe even more) versions of WP available for download as separate packs. For instance, `blog-version` wouldn’t have custom post types support and be a lighter version overall, while CMS-version would have a home static page by default and no comments bundled, and Tumblr-like version would be more about custom post formats… sky’s the limit. This way users wouldn’t have to upload (and update) many files from the core that they’d never use anyway and probably complain less about WP becoming bloated with too many features that average user doesn’t need.
    There’s probably an apparent problem rising about plugins and themes being compatible with just one of these `versions` and not two others and vice-versa.

    Reply »

Leave a Reply

Your email address will not be published. Required fields are marked *