The Trouble With Back-Ends - CMS Woes: Why Publishers Can't Publish on the Web | Adweek The Trouble With Back-Ends - CMS Woes: Why Publishers Can't Publish on the Web | Adweek
Advertisement

The Trouble With Back-Ends

CMS woes: Why publishers can’t publish on the Web
Advertisement

With hundreds of new “out-of-the-box” CMS products having sprung up over the last two years, and several mainstream news sources like CNN, NBC Sports and CBS Radio adopting open source blogging systems like WordPress, there’s a tidal wave of CMS changes in the works. “Most publications we talk to are doing a move right now,” says Vineet Gupta, an account director at publishing platform company Daylife.

Technology officers, already under pressure to please editors and/or brand executives, tech teams, accounting, and, oh right, readers, have much to consider: open source or closed? Off the shelf or home baked? End to end or next gen? Silo or multi-vertical? What’s cheapest? Easiest? Most flexible? Most secure? And what matters most?

Condé Nast CTO Joe Simon, for one, recently moved the company to CQ5, a CMS created by Adobe’s recently acquired Day Software. Whether it will pay off for the prestige publisher is unclear. While Simon, brought in last fall, called the system a “much more elegant way of managing content,” the case could be made that CQ5 is a step backward. Adobe’s products do have consistent language and tools, but industry observers note that CQ5’s language and tools are jarringly different from Adobe’s other products.

Regardless, anything is an upgrade from Condé Nast’s previous system, which required the tech team to be heavily involved in almost any Web publishing. The CQ5 system will let editors publish independently of that team, a function the staff at most other digital publications have had for a decade.

The Washington Post is spending $7 million over two years migrating from three separate platforms to Méthode, an EidosMedia-developed CMS popular with daily news organizations. The shift from many to one system altered the way WaPo’s newsroom operates; in a March column, ombudsman Patrick Pexton lamented that the system reduces journalism “into generic ‘content,’ something akin to the unidentifiable filling in a Twinkie.” Managing editor Raju Narisetti maintained that the integration, while rocky at first, has paid off, noting that newsrooms, digitally speaking, “will always be in beta mode.”

Time Inc.—a close runner-up to BusinessWeek when it comes to CMS-icide—is in endless development. The publisher of high-volume websites like People.com and Time.com has been building an in-house CMS system for seven years; and yet the company will probably abandon it, says Time Inc.’s Klaif. The project has taken on multiple incarnations, with the most recent strategy change happening two-and-a-half years ago. But technology waits for no CMS, and only five of Time Inc.’s lowest volume titles have moved onto the system. (Such in-house systems are notorious for being outdated once they get around to being implemented.) The company’s high-traffic sites still operate on old versions of Vignette; others use Drupal, WordPress, or a homegrown system, TIPS.

Are the editors of those high-volume sites happy with Vignette? “Well, they’re familiar with it,” Klaif says. Vignette is limiting, but Klaif sees no stable alternative. People.com broke 180 million page views on the day of the royal wedding—most open-source publishing systems couldn’t handle that traffic or volume of content, he notes.

Time Warner divorcée AOL (approaching the bittersweet two-year anniversary of its spinout) has had no less of a costly, roundabout course. In the mid-’00s, the company planned to unify its publishing platform onto one large CMS called Dynapub. Three years and dozens of engineers later, AOL flat-out abandoned the project.

“When you try to build a product that works for everybody, it works for nobody,” a former AOL employee says. The company eventually bought the platform Blogsmith for around $5 million, and AOL’s content properties migrated there. But with AOL’s acquisition of The Huffington Post, the company plans to migrate once again, this time to HuffPo’s highly customized adaptation of the Movable Type blog software.

At least Time Inc. and AOL are further from the dark ages than Salon.com. The first online magazine runs on the Internet’s oldest, creakiest CMS. “MPS” was built 15 years ago—ancient in Web years. The company put off a migration because it was expensive and time-consuming. Salon’s tech team also held its breath for that silver bullet.

“No one knew if there was going to be an industry standard,” Salon editor-in-chief Kerry Lauerman says. Since none has emerged, Salon decided to migrate to WordPress, an eight-month process it will complete this month.

These stories are far from unique. MSN’s developers are stuck using Microsoft’s .NET Framework even in instances when other options are more suitable; Disney properties operate on GoPublish, a homegrown system built with its own frustrating “Java-like” language called Tea. MTV has made several changes over the years—from uniting every brand on the same platform to letting each of them choose their own CMS platforms.

The rarest of all CMS-using species? The publisher with the “right” one.

Fortunately for AOL, The Huffington Post is one such publisher. AOL’s migration to HuffPo’s customized Movable Type will be a certain upgrade—despite the home page of Huffingtonpost.com looking like an ADD nightmare of bells and whistles. It’s also a raging technical success, thanks to HuffPo’s jet-fueled CMS.

The company’s platform—built over an old version of Movable Type—has developers tweaking it round the clock in every time zone. HuffPo rolls out 10 to 30 new pieces of code each day, says CTO Paul Berry. The secret, he says, is the lack of sales people interfering with the editorial and tech teams, who collaborate on development. HuffPo’s editors “care a ton about social” and its developers are “not just contracted code monkeys,” Berry adds. In addition to absorbing AOL’s Web properties, HuffPo is offering its CMS to advertisers like GE and IBM Smarter Planet as a part of its social marketing ad offerings.

The Onion, being powered by a small but mighty three-person tech team, successfully takes the opposite approach. It abandoned Drupal because it wasn’t scalable enough, and its current CMS is homegrown with help from Django and Python. “The initial impulse is to go with a big enterprise-y system that may cost a lot of money and do everything,” says Jeff Weston, The Onion’s lead developer. But that’s dangerous, he notes, because it overlooks specific needs, while going completely open source can be messy and underpowered.

SB Nation, a network of around 300 sports sites, is often cited as the outlet doing CMS best. The startup, backed by $23.5 million in venture funding, was founded in 2003 as AthleticsNation.com; one of its co-founders is Markos Moulitsas, who’s behind the Daily Kos political site. Since launching, it’s broken into the top 10 sports media properties online, and is valued at a rumored $90 million.

“The company is built on a marriage of talent and technology; the more talented storytellers we have, the more they push the product team,” founder Jim Bankoff told Forbes.com. In April, SB Nation recruited several key players from the tech and editorial team at the blog Engadget after AOL, which owns Engadget, acquired HuffPo. The network’s spate of innovative publishing tools was a key in its recruiting, according to former Engadget editor Joshua Topolsky, who will become editor-in-chief of SB Nation’s new tech-focused vertical. “SBN isn’t just another media company pushing news out—it’s a test bed and lab for some of the newest and most interesting publishing tools I’ve ever seen,” he told PaidContent.org.

Of course, the elusive success stories of SB Nation and its peers are no accidents. Happy back-ends have a few things in common: They cut out the middlemen; they dedicate relentless energy to their CMS; and they stay in front of new technology. Oh, and they don’t really care about silver bullets. —With additional reporting by Gabriel Beltrone

After the jump: What your CMS says about you.

Continue to next page →