While developing Snowball<\/a>, Thomas Park, a researcher at Drexel University, found that, among the top newspaper websites in North America, WordPress is the most identified CMS, but at only 11%. For most (62%) of sites, the CMS could not be identified. These \u201cothers\u201d are likely using custom solutions, and I wondered why so many newspapers seemed to be going in that direction. (Student newspaper sites overwhelmingly use WordPress, at 68%). View his research here<\/a>.<\/p>\n Let\u2019s look at a case study in introducing a custom CMS: Total Publishing System (TOPS) at the Toronto Star. This case study comes from Scott Rodgers who did an ethnographic study of the Star\u2019s newsroom from 2005-2013 and published his work in the journal Journalism<\/em> in 2014 \u2014 view the study here<\/a> (at a cost unless you are affiliated with a public institution with a subscription to the journal). TOPS was introduced in 2006 as the so-called \u201chigh performance engine\u201d of thestar.com. The Star started a new unit, TorStar Digital, with a start-up style office with hundreds of staff, which ran the CMS and built new products, at least in theory.<\/p>\n In practice, TOPS and TorStar Digital posed many challenges to the everyday operation of Star reporters and editors. Technically, anyone at the Star could edit content on TOPS, but because the CMS was complex, the web team that implemented it just never left the newsroom. The CMS had all kinds of problems such as lags between updates, constrained navigation and layout, and poor SEO \u2014 and the web operation in the newsroom actively worked to subvert it.<\/strong><\/p>\n Senior management\u00a0at the Star\u00a0was\u00a0frustrated that TOPS hadn\u2019t been designed collaboratively and an us vs. them mentality gradually developed: a senior digital editor complained, \u201c[TOPS] just doesn\u2019t give us the flexibility we need to respond to things instantly and overly creatively.\u201d The CMS wasn\u2019t empowering \u2014 it was limiting.<\/strong><\/p>\n The TOPS CMS demonstrates what goes wrong in general when you do a top-down design process. It also shows that having a website and a custom CMS isn\u2019t a digital strategy on its own.<\/p>\n By contrast, Chorus from Vox Media is lauded as the holy grail of CMS solutions for digital publishing<\/a>. It should be noted that Chorus had a major advantage over TOPS \u2014 it wasn\u2019t developed in an existing print newspaper culture. That said, it\u2019s a good case study for us to look at because it shows the power of what a CMS can do for a digital publication.<\/p>\n Chorus is the product of an iterative design process with a tight development loop between developers and writers. Everything can happen inside Chorus and everyone can use the CMS.<\/strong> Some features include forums, an editorial workflow system, and flexible layout.<\/p>\n It\u2019s the Chorus CMS that led to the creation of websites like Vox.com and The Verge. Ezra Klein was formerly a reporter at the Washington Post and went to Vox because of Chorus \u2013 he says of his decision to leave the Post in the New York Times<\/a>, \u201cwe were badly held back not just by the technology, but by the culture of journalism.\u201d<\/p>\n Chorus is flexible \u2014 tools can be created as tools are needed.<\/strong> Developers are embedded in the culture of the organization and content creators are part of the development process.<\/p>\n So between these two case studies, we learn that for a CMS to be a productive part of a newspaper\u2019s digital strategy, it has to be user-centred \u2014 it has to help journalists become developers, and developers become journalists. So what are some ways custom systems are tackling this?<\/p>\n One approach to making reporters \u201cdigital\u201d is to reflect actual editorial workflow in the CMS. At a newspaper, many people are editing the same content at the same time. If they want to add a comment, they want to note it right above the spot they\u2019re critiquing. Certain editors or reporters should be able to access certain content at certain times; others should not.\u00a0These are really fundamental processes of editing nicely reflected in the New York Times\u2019s custom CMS, called Scoop<\/a>.<\/p>\n Another approach seen in Scoop is to empower non-technical editors. Flexibility is a major limitation of traditional newspaper CMSes. Like I said, at The Varsity<\/em>, we wanted to do a lot online that we couldn\u2019t because our online team was busy doing things like copying content into text fields and maintaining the website.<\/p>\n So, as much as possible, non-technical editors should become digital editors \u2014 they should be actively using the CMS and able to create custom, interesting content simply through CMS tools, like\u00a0Atlas\u00a0by Quartz<\/a>\u00a0and Snowball. This also frees up time for the dev team to spend time responding to requests for new features and actually fostering a culture of innovation.<\/p>\n These are just a few key ways the right CMS can help facilitate culture change \u2014 in fact, my research turned up quite a few more, as well as several tensions in approaches to CMS design, including integration\u00a0of user-generated content, the role of algorithms and computational journalism, and how CMSes should integrate with print content management.\u00a0As newspapers continue to hone their digital strategies, more approaches to CMS design and open source tools will emerge.<\/p>\n TL;DR? When your editors are able to participate in and post digital content, you can facilitate a culture shift wherein developers are in turn able to participate in content creation and you get innovation.\u00a0A custom CMS, built with input from content creators, can help to foster a culture shift in news organizations in which editors become digital editors, developers become journalists, and newsrooms become digital-first.<\/strong><\/p>\n Lastly \u2014 to address a great question that was brought up during my talk: how can a small paper, like the one that inspired this research, afford to change their CMS? First off, no need to re-invent the wheel: WordPress is a great foundation to build off of.<\/strong> Secondly, there are lots of open source resources that can be integrated into a patchwork custom CMS for smaller organizations. To name a few well-known organizations with github repositories: The Guardian<\/a>, The New York Times<\/a>, Vox Media<\/a>, and FiveThirtyEight<\/a>. Those are just a few \u2014 and even better for smaller papers is when other smaller papers open source their tools so they can work collaboratively to build great things.<\/strong><\/p>\n Featured image via @iStudentConfTO on Twitter.<\/a><\/em><\/p>\n","protected":false},"excerpt":{"rendered":" Last week, I presented some research I worked on over the first year of my MI at the iSchool’s Student Conference. I gave a five-minute lightning talk on introducing custom content management systems (CMSes) in print news organizations as a means of facilitating a shift towards a digital-first newsroom culture. An edited version of my… Continue reading Going digital-first: content management systems in news organizations<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":203,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/posts\/202"}],"collection":[{"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/comments?post=202"}],"version-history":[{"count":10,"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/posts\/202\/revisions"}],"predecessor-version":[{"id":215,"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/posts\/202\/revisions\/215"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/media\/203"}],"wp:attachment":[{"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/media?parent=202"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/categories?post=202"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/danielleklein.ca\/index.php\/wp-json\/wp\/v2\/tags?post=202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Case study: The Star<\/h2>\n
![\"A](\"http:\/\/danielleklein.ca\/wp-content\/uploads\/2016\/03\/torstar-digital.jpg\")
Case study: Chorus<\/h2>\n
![\"Some](\"http:\/\/danielleklein.ca\/wp-content\/uploads\/2016\/03\/vox.png\")
Building\u00a0systems\u00a0that work for you, not against you<\/h2>\n
TL;DR<\/h2>\n