Is your proprietary software better than open source?

That’s a question every news organization should ask itself, whether it be for its main CMS or other Web software.

And when I say proprietary, I don’t mean just software built in house but also software provided by vendors. If the answer is no, our proprietary solutions are inferior, than you have some serious soul searching to do. Why would you pay for an inferior product?

Now it is possible that A) your CMS and other Web software predate some of the quality, free open-source alternatives available (many would argue that Drupal, while quite a robust option now, wasn’t that good a few years ago). If this is the case, your organization should look into modernizing its Web software ASAP. I still hear journalists complaining about being hampered by creaky CMSes.

Don’t let outdated software stand in the way of your ambitions, especially when there are so many strong open-source options available. A good CMS won’t give you a good Web product, but it also won’t stand in the way of one either.

But if the answer is B) because we didn’t know any better, than that’s a serious, serious problem. There are news organizations that don’t have the right people making these decisions. Some will be easily swayed by vendor marketing tactics, while others will go with whatever CMS integrates easily with their print content management system. Listen, your Web CMS is more important than your print content management system.

Ideally, both will be strong systems that integrate well with each other. But with a Web-first strategy, tight integration isn’t that important anymore. Back when print content was pushed onto the Web it was, but times have changed. Web and print content are often different, with the Web often getting many exclusives. Increasingly, Web and print content will be distinct, negating the need for tight integration (or the need for purchasing a CMS and print content management system from the same vendor).

Utlimately, the point is that you can’t let poor software decisions hamper the potential of your news organization. The good news is that a good CMS doesn’t cost much money. The bad news is that the people in charge at your news organization may not know that.

Post navigation

  • Pingback: “No dejes que malas decisiones de software arruinen el potencial de tu organización de noticias” « tejiendo redes

  • http://www.adrianeden.com/2009/01/23/the-real-power-of-twitter/ Adrian Eden

    Super nice post, I bet CMS developers will be in UBER high demand this year!

  • http://openconcept.ca/ Mike Gifford

    Nice article. Also worth noting that there are security costs to maintaining proprietary software. There aren’t that many CMS platforms that have the kind of security expertise that Drupal draws on – http://drupal.org/security-team – let alone a community that has a proactive response to security issues.

    If you aren’t paying for ongoing security monitoring for your proprietary system you’re just betting that the exploits aren’t found on your watch. Security by obscurity is a bad approach, particularly online.

  • http://newmedianotes.wordpress.com Carlos Virgen

    Very timely post as far as I’m concerned. Our news org, union-bulletin.com is currently under contract with TownNews. We are now in the process of beta testing their new CMS which will allow us to redesign our site which is much needed. We briefly considered Drupal but our lack of in-depth programming skill and lack of man-power scared us off. I’ve recently been asking in Twitter if maybe WordPress would be a viable alternative for us. Just so you know our online dept. is myself and another guy with some PHP programming knowledge but is more of an IT person. We are reaching the desperation point and may stay with TownNews because it doesn’t require us to do any back end coding. What would you recommend for an org. like us? I’m willing to dive into learning Drupal/Django/Joomla but I’m not sure it would get us where we want to be in a timely manner.

  • http://sellingprint.blogspot.com Michael Josefowicz

    Re wordpress

    Google is rolling out XML sitemaps for WordPress. If you follow the links from http://googlemarteconomy.blogspot.com/2009/01/wordpress-google-xml-sitemaps-wordpress.html
    you can get the story.

    , given Google’s focus on ease of use it should help with the learning curve I have some information that folks are using WordPress as a CMS for web sites. Given that wordpress has wide adoption rates it makes sense that it’s pretty bug free and stable.

    As for the security problem:
    What exactly are the security issues? Protecting the “news”? Spam? I sincerely don’t understand the issues. Unless they are legacy thinking from the days of information scarcity.

  • http://www.patthorntonfiles.com pat

    @Mike,

    Great point about security. Security through obscurity almost eventually always fails. It’s impossible to remain obscure forever on the Web. I once worked at a paper that fell prey to a very simple SQL injection attack. These things don’t happen to mature, battle-tested CMes.

    Software that isn’t security tested and prodded by professionals will eventually be compromised. I wouldn’t be surprised if my former paper was exploited by a teenager. If you’re site doesn’t take security seriously, there is a much larger pool of potential threats.

    @Carlos,

    You may want to give WordPress a try. There are some really good premium themes available (they don’t cost that much either). Many of them are designed specifically for journalism purposes. You don’t need any back-end programmers for a custom WordPress site either.

    @Michael,

    The major security issue is having your site hacked and losing your data. Many custom CMSes are vulnerable to very simple attacks.

  • Pingback: » Subscribe to comments is a must-have feature | The Journalism Iconoclast

  • http://sellingprint.blogspot.com Michael J

    @Pat-
    I read that Google Aps has over 500,000 users. They just sold the city of Washington DC to move to Google Aps instead of maintaining their own servers.

    Maybe the best way to be secure is to host the content part of the CMS on Google servers. I would trust them to keep data safe from disappearing more than any proprietary system.
    Plus I’m more confident that they are continually upgrading the software.

  • http://www.papertracer.com/ SaaSonhand

    I agree with you Michael, Google has a lot to offer…what about storefront open source..is there anything better than magento?