LWN.net Logo

Campsite offers plug-and-play freedom of the press

March 18, 2009

This article was contributed by Nathan Willis

The non-profit Media Development Loan Fund (MDLF) released a major upgrade to its online journalism content management system (CMS) Campsite last week. Campsite 3.2 brings a flexible new plugin system and several improvements to search, templating, and content editing. MDLF describes Campsite as a CMS tailor-made for newspaper publishers — many of whom cannot afford expensive commercial products or the IT support required to heavily customize general-purpose CMS packages. Many of MDLF's target organizations are independent media in countries in transition, but the system is used in newsrooms all over the globe.

Campsite is deployed by more than 70 publications, many in Central and Eastern Europe near MDLF's Center for Advanced Media in Prague (CAMP), the office from which Campsite takes its name. But the software is also popular in Latin America, such as at El Periodico in Guatemala City, Guatemala.

MDLF's mission is to support independent journalists and media organizations, so that they are "strong enough to hold governments to account, expose corruption and drive systemic change." Founded in 1996, it provides funding to independent media in 23 countries, made possible through private donations and public grants. MDLF describes tools as the key investments for independent media, including printing presses, radio and television transmitters, and software. Campsite and the other CAMP projects grew out of MDLF's need to provide low-cost, open source software for new media outlets.

The feature set caters to the needs of professional news publications, which CAMP's Head of Research and Development Douglas Arellanes described as an "organic" relationship. "Campsite has been around since 2000, and nearly all of its features have come on the basis of real-world implementations."

Arellanes says journalists and editors on deadlines have better things to do than worry about CMS management, and that is the key difference that sets Campsite apart. He personally likes Wordpress and has great respect for the project, noting that:

It's really easy to get something resembling a news site up and running quickly. And that's fine, especially when those sites are one-person shows, where there's only one person inputting content and managing the backend. But when you start to get more people involved, and when you start to have different sections, with each wanting their own news prioritization, managing that can become much harder. And that's especially where a CMS like Campsite is best-used.

Campsite's back-end allows an organization to replicate the newspaper workflow: authors can create and edit stories, submitting them to the editors when ready; editors can alter them, schedule them to run at predetermines times, change their visibility, move them between sections, and ultimately approve their publication. The system also handles administrative tasks like managing subscriptions, tracking article views, and moderating reader comments. A single back-end can also run multiple publications with different rules, schedules, layouts, and subscription lists and policies.

It can handle paid or unpaid subscriptions, supports embedded multimedia in articles, can integrate with the Phorum web forum package, and is multilingual from the ground up. The interface is available in 14 languages, and every individual article can be translated, whether as a one-off special, side-by-side in a single publication, or with entire sections or publications in separate languages.

Lead developer Mugur Rus said Campsite takes security very seriously. The administration interface can run over SSL and uses fine-grained role based privileges on all accounts. The system also uses CAPTCHA for comment forms, logs all events, and can use email notification to alert system administrators. Rus says Campsite itself has only been cracked once, and that it uses the standard security features of its free software based platform.

A peek at 3.2

Campsite is written in PHP and is designed to run on Apache servers using MySQL. The manual cites Apache 2.0.x, PHP 5.0, and MySQL 5.0 as the minimum version dependencies, and requires ImageMagick to handle graphics. In addition, you must run PHP as an Apache module, not as CGI, and there is a short list of required PHP directives to set up in the installation's php.ini file. Campsite runs on Linux, FreeBSD, Windows, and Mac OS X servers. No current Linux distributions are known to include Campsite, although from time to time users have shared their own home-brewed packages.

New in version 3.2 are improvements to search functionality, content editing, and site templating. The search improvements include an "advanced" search mode and increased support for non-ASCII languages that were problematic in earlier revisions. The story editor now uses the WYSIWYG TinyMCE component, with which administrators can customize the available markup features by privilege level. The Smarty-based templating system now supports functions, and developers have begun migrating the Campsite administration interface to Yahoo's open source AJAX interface library YUI.

The most significant feature is the debut of a plugin architecture that can extend the functionality of a publication but remain integrated with the core Campsite story content. For example, one of the three default plugins in Campsite 3.2 is a blogging module. Arellanes observed that most newspaper sites are just beginning to implement staff blogs, and that when they do they are typically stand-alone deployments of existing blog systems that sit isolated from the rest of the publication. Using Campsite's blog plugin, however, content is accessible via the same topic tags and search, whether it is a news article or a blog post.

The other two default plugins implement reader polls and a "live" interview system — in which readers can ask questions, an administrator can approve or reject them. The interviewee can then respond to them and have the answers posted automatically.

3.2 also uses a simpler installation process, inspired by Wordpress's five-minute install experience. Users now need only to expand the tar archive of the latest Campsite build, put the site contents into the folder they desire on their Web host, and follow the step-by-step setup process through the Web installer.

Moving forward

Arellanes said to expect a quick turnaround for the next stable release of Campsite, focusing on cache performance and overall speedups, and implementing a content API that will permit Campsite sites to make their story content available to outside users for aggregation or content mashups.

He also hopes to see more development from third-party coders on plugins using the new plugin API. "The open source model, as it concerns Campsite, has meant that we're really growing in terms of the number of features that are being contributed from non-core developers. We expect this trend to really pick up now that we've got a plugin architecture to work with."

The press release for Campsite 3.2 notes that independent media in developing countries have long operated on limited funds that preclude the expensive CMS solutions preferred by other organizations — the very situation that drives MDLF's software projects. But it also points out that newspapers in the "developed" world are facing a financial crisis of their own. Consequently, an open source CMS like Campsite makes more sense than ever.


(Log in to post comments)

How is the history tracking?

Posted Mar 19, 2009 5:41 UTC (Thu) by mrjk (subscriber, #48482) [Link]

Reading the article, the press release, and the feature list, there is a conspicuous absence that is
common for all software of this type I guess. There is no mention of historical ability. That is, 10
years from now I want to refer to an article that was published by Campsite 5 years previously. How
can I refer to it and how does Campsite display it? I see the ability to publish "issues" but what
about old issues. There may be features that do this, but they are never highlighted in any of these
press releases. That lack of concern for me is a big issue for online news and sites. It ought to be a
main feature of reviews. Otherwise we lose citations and history.

How is the history tracking?

Posted Mar 19, 2009 17:24 UTC (Thu) by n8willis (editor, #43041) [Link]

mrjk, I'm not quite sure what you mean. Do you mean 'are published articles assigned unique URLs'? Because of course they are, but that still wouldn't prevent a site admin from removing or re-editing old content, or from messing with other settings. Or do you mean 'is there a way for editors and story authors working on new articles to automatically pull in references to old articles for citation'? Or something else?

Nate
PS - you can access the demo site at http://campware.org/en/camp/campsite_news/643/ -- it might tell you what you need to know, although it has not yet been updated from 3.1 to 3.2.

How is the history tracking?

Posted Mar 21, 2009 0:23 UTC (Sat) by mrjk (subscriber, #48482) [Link]

Hmm... I replied a couple days ago and it somehow was lost.

Anyway what I am looking for would be a kind of historical snapshot capabiity. Suppose I use
Campsite for 5 years. Its now 2014 under the Palin administration and someone alleges that two
years previously I had an article about Cheney next to an article about atheists and that insulted
Cheney and I am now a traitor and going to jail. (Ok, Ok this is just for illustration). I want to show
what the site looked like that day in 2012. The whole site in relation to itself. Not just articles.
Perhaps bundling issues would let me do this, but if I didn't want issues, is there a feature that I
could call and say, I want what the site looked like at a given point in the past.

With a paper this is always a given, but I think it is bad that it is not done for electronic Web
publication much.

Hope this gets across what I was looking for,
Mark

How is the history tracking?

Posted Mar 21, 2009 18:49 UTC (Sat) by Cato (subscriber, #7643) [Link]

I think the solution to this is outside Campsite - either rely on the Internet Archive to do this, or set up a weekly process that captures the whole website and archives it into static HTML. The latter is probably preferable, but what might be best is if the Internet Archive could be contracted to do this for newspaper sites - it would be a useful service and also provide some income to the archive.

Campsite offers plug-and-play freedom of the press

Posted Mar 26, 2009 8:48 UTC (Thu) by muwlgr (guest, #35359) [Link]

From the description of Campsite I can see a great extent of similarity to LWN own web site software. Only Campsite is more widely used-tested-developed.

Copyright © 2009, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds