HOME
          
LATEST STORY
Newsonomics: The Financial Times triples its profits and swaps champagne flutes for martini glasses
ABOUT                    SUBSCRIBE
June 15, 2012, 2:55 p.m.
Reporting & Production

The Lawrence Journal-World gets out of the CMS business, losing out to freebies like WordPress

The company laid off engineers working on Ellington, a CMS built on Django.

The future is uncertain for Ellington, the content management system designed by a news organization for news organizations. Ten people working on the project were laid off this week.

Developers at the Lawrence (Kan.) Journal-World created Ellington for their own needs, and they liked it so much the company got into the business of licensing the CMS to other news organizations. About six years ago the World Co. created a division called Mediaphormedia that provided hosting, software updates, and ongoing support to clients.

Now, with most of that division laid off, the World Co. is refocusing on its own software needs. Existing customers will be able to keep the platform at least through their current service contracts, and the company is considering partnerships with other developers to potentially keep the project alive.

“The efforts to support a commercial base of customers, as opposed to using our software internally, have become difficult in a competitive CMS field that is also serving a pretty stressed industry,” said CFO Tom Hornbaker.

So what happened? Six years ago, it was unthinkable for a news organization to power its website with a seemingly anemic platform like WordPress or a mind-bogglingly complex one like Drupal. Ellington just worked, right out of the box, and it was tailored to the needs of newsrooms.

But WordPress, Drupal, and others have matured tremendously since then, and they remain free and open-source. Active communities of developers have sprung up around the products, making deployment a lot easier than it used to be. (We use WordPress here at Nieman Lab.)

Nowadays, “it’s hard to compete with a product like WordPress,” Hornbaker told me. “We basically have become a hosting operation that has a pretty good suite of software that nobody likes to pay for. We think a lot of our Ellington product and think it’s one of the tops in our industry. That said, many people don’t have the resources to pay for it and would rather get something that is less expensive that meets their basic needs.” Hornbaker said Ellington has fewer than 100 customers.

Ellington’s roots go back about nine years, when a couple of Journal-World developers found themselves frustrated with their CMS. Not only that, they were frustrated with the programming languages they could use to build a new CMS themselves.

So Adrian Holovaty and Simon Willison started hacking on top of Python, a language liked for its uncluttered syntax. They designed a custom CMS with their newsroom’s needs in mind. That work gave way to Django, a framework to help other developers build apps more quickly. The World Co. released Django as open-source, and today Ellington is built on Django.

This news got us wondering about how Django is doing as a platform for news applications. Rails, a competing framework for the Ruby programming language, is big in the broader web development community; Django has had a particular strength in the news apps world because of its built-for-news background. So I put the question to several smart news devs: Which one is winning, Django or Rails? (I decided to do this on Branch, a new and still-in-beta discussion site bankrolled by Twitter’s co-founders.)

It was kind of a stupid way to put the question — “winning” isn’t the right framing — and I should have anticipated the initial response: The tools don’t matter. Okay, fine, but developers need to pick one or the other, and news organizations still need to hire people who can work with the tools required.

The discussion evolved (and continues as I write this), and there are a few interesting points, like this one from NPR’s Chris Amico:

All of us in here build news apps, mostly outside our main publishing systems. Would you rather spend your days hacking on a newer, better CMS (whether that’s Armstrong or Baroque or Vox Media’s new toy)? Or do you see an ongoing separation between daily publishing and app building? Or is the future more bespoke mini-CMS things like PolitiFact and Homicide Watch?

ProPublica’s Jeff Larson replied:

That’s a good question. While I do want a better CMS from time to time, as a developer who is also a reporter, I want to spend more time building stuff that tells a story and not stuff that publishes stories.

Plus I’m skeptical we’ll ever have a CMS to rule them all, and our current one (Expression Engine) does just fine putting words on a page.

This is a perennial problem for journalists trying to build digital things on deadline: Do it right or do it fast. Whole publishing systems can spring up from messy workarounds — that’s how Ellington came to be, after all.

The conversation is embedded below.

POSTED     June 15, 2012, 2:55 p.m.
SEE MORE ON Reporting & Production
SHARE THIS STORY
   
Show comments  
Show tags
 
Join the 15,000 who get the freshest future-of-journalism news in our daily email.
Newsonomics: The Financial Times triples its profits and swaps champagne flutes for martini glasses
The FT is a leader in crossing over from print — digital subscribers now make up 70 percent of its paying audience, a number that keeps growing.
A farewell to #content: Optimism, worries, and a belief in great work
A few thoughts on the state of media (and meta-media) from our departing staff writer.
On convening a community: An excerpt from Jake Batsell’s new book on engaged journalism
“An engaged journalist’s role in the 21st century is not only to inform but to bring readers directly into the conversation.”
What to read next
789
tweets
Snapchat’s new Discover feature could be a significant moment in the evolution of mobile news
By putting mobile-native news adjacent to messages from friends, Snapchat could be helping create part of the low-friction news experience many want and need.
750Snapchat stories: Here’s how 6 news orgs are thinking about the chat app
From live events to behind-the-scenes tours, The Huffington Post, Fusion, Mashable, NPR, Philly.com, and The Verge tell us how they’re approaching Snapchat.
714Here’s how the BBC, disrupted by technology and new habits, is thinking about its future
The British broadcaster released a new report looking at the future of news as it looks toward its royal charter renewal in 2017.
These stories are our most popular on Twitter over the past 30 days.
See all our most recent pieces ➚
Fuego is our heat-seeking Twitter bot, tracking the links the future-of-journalism crowd is talking about most on Twitter.
Here are a few of the top links Fuego’s currently watching.   Get the full Fuego ➚
Encyclo is our encyclopedia of the future of news, chronicling the key players in journalism’s evolution.
Here are a few of the entries you’ll find in Encyclo.   Get the full Encyclo ➚
Voice Media Group
Ars Technica
Connecticut Mirror
Minneapolis Star Tribune
U.S. News & World Report
MediaNews Group
The Weekly Standard
DocumentCloud
Next Door Media
Byliner
Publish2
Voice of San Diego