CoPress

The Texas Tribune, an innovative news start-up located in Austin, is a non-profit that seeks to cover news in the entire state using features like extensive databases, blogs, calendar, an elected officials directory (and an iPhone app for it), a state newswire,  a slick mobile site and much more.

There’s a lot student media can learn from the web-centric setup of the Texas Tribune newsroom, from its use of open source software, to its strong development team, to its depth and excess of useful content.

Yesterday I spoke with Brandon Taylor, the lead developer for the Texas Tribune. He said the Texas Tribune development team built the entire site in four weeks, during which time Brandon pulled a few all-nighters in the newsroom and even broke a keyboard because he was typing incessantly — in other words, it was an intense turnaround. Read more →

Standard Podcast [ 30:23 ] Play Now | Play in Popup | Download (350)

Max Cutler, Web developer at the Yale Daily News and Courant News, recently started a forum topic about presenting multimedia on a student news site that we’ve been meaning to start a conversation around. The YDN recently launched a new landing page for their multimedia that offers a much more graphic view. What’s your reaction to how the page presents different type of media? Is it better to have content organized by topic or content type? What’s your ideal multimedia browsing experience? Weigh in on the thread!

This week, CoPress directors Daniel Bachhuber, Andrew Spittle, Lauren Rabaino and Adam Hemphill are attending the National College Media Convention in Austin, Texas. These are reports from the field. For more updates, follow the conversation on Twitter.

In the “Townsquare” session, led by Arvil Ward and Anthony Pesce, the Populous Project was demoed. The Populous Project is a Knight News Challenge funded project that is working to build a content management system for student news publications based on Django.

Among the technologies demoed were the Digital Newsroom, which is a system of tracking story assignments that is currently implemented by the UCLA Daily Bruin. As Arvil said, “this provides a communication tool with the ability to manage the newsroom online.” It has threaded commenting for story ideas and notifications for when an assignment changes. Interestingly, it is not yet integrated with the content management system and how closely it will be able to manage content is to be determined.

Also demoed was Campuswalk, UCLA’s project to create a unified, cohesive, and searchable campus gateway. The current system is not up to the task in the eyes of Arvil and they’re working hard at building something better. It will make professor reviews, housing reviews, and swapping books more social.

The final piece of the demo was Localresearch.com. Arvil described this as focused marketing to small local businesses that seeks to reinvent the decreasing value of print advertising. They provide a database of local business listings and for $45 a month they work with companies to create more full-featured listings that include links to social media, reviews, and more.

On September 2nd, the Yale Daily News published its first issue of the fall 2009 semester. Although appearing to the casual observer to be just another issue, there was one huge difference: it was running on the new Courant News online publishing platform. Just one week later, Yale graduate student Annie Le went missing. The following ten days resulted in enormous national and international coverage of the case and a record surge in traffic to our Web site. Courant News played a huge role in our outstanding coverage and lack of downtime during the traffic spikes. Read more →

A few days back, Max Cutler posted a hefty spec for the administration side of Courant News, code named “Nando.” I’ve finally had the time to start reading through it and boy am I impressed. Most notable thus far are: the pitch system, a genuine workflow based around statuses and user roles, and a heavily customizable dashboard for all of this activity. All of these are features I think most people would find useful if they had access to them; Courant will be in a good position to deploy and then refine usability based on feedback.

Speaking of feedback, Max is still very interested in getting other’s opinions for a few more days. I’d encourage anyone interested in seeing this develop to read through the conceptual section and send him feedback via the Google Group. I’m still working through my notes and will be sending them later tonight.

Also related, Mo is making significant progress on the Edit Flow Project; there should be a working prototype of stage one in the next couple of days.

A round-up of the student news organizations running Django in April 2009 as part of our end of the school year retrospective.

The Maneater

Your name (or the Web Editor’s name): We have two online editors. Currently, I [Justin Myers] am the online development editor and Esten Hurtle is the online content editor; after Tuesday’s issue comes out, though, we’ll be handing those jobs over to James Vestal and Erin Kaplan, respectively.

How Often Do You Publish (Online): Continuously, though mainly with our print issue (see below)

How Often Do You Publish (Print): Twice a week (Tuesdays and Thursdays)

In your opinion, what’s the most unique feature or piece of functionality on your website? We spent a fair amount of time this past summer working on our campus guide, which we intend to be a resource for students to be able to find useful contact information for various departments and administrative offices; filterable maps of residence halls, computing sites and other kinds of places on campus; and upcoming events taking place on campus and around Columbia. That said, it could still use quite a bit of work; this year was definitely one of transitioning for us from being a simple shovelware site to one with a bit more content and utility to it.

What does your editorial workflow look like? Does it involve the Django admin? Our print workflow actually consists of a well-established directory structure of text files until they reach our design staff, which places the text and other content into InDesign. (Not at all elegant–but it works, it’s cheap and we can work on it from anywhere.) Our online workflow then consists of copying the same text and other content into the Django admin.
Read more →

Hosts: Greg Linch, Emily Kostic, and Miles Skorpen

Guests: Max Cutler and Robert Baskin

Summary: A question and answer session with Courant News, an open source Django CMS for student news organizations. The idea to build a Django CMS specifically for student newspapers came from discussion at an Ivy League news conference last April when people saw that no one had a CMS with the feature set they needed. Max and Robert, along with Paul O’Shannessy, decided they needed to fill the void. The conversation covers a bit of the history, and then goes into the specifics of the CMS. For more information, please check out or add to the wiki show notes.

Subscribe: iTunes | RSS

Standard Podcast [ 31:54 ] Play Now | Play in Popup | Download (211)

Clarification: Courant News is being developed as a side project of Max Cutler, Robert Baskin and Paul O’Shannessy — independent of the Yale Daily News. It will eventually become the Yale Daily News’ CMS.

Tomorrow at 5 p.m. Eastern (Tuesday, May 5th) Emily and I will record a new episode of This Week in CoPress with Max Cutler and Robert Baskin, discussing their Courant News CMS project. Courant is an open-source Django CMS that Max has blogged about extensively on his site. We’ll talk about main features, the installation process, theme capabilities, and what their vision for the future is.

We’ll be hosting the call on Skype. If you wish to call in, please contact me with your Skype name or phone number at greg [at] copress [dot] org. You will be added to the call and be able to ask questions.

We’re trying this as a higher quality alternative to BlogTalkRadio. Let us know what you think. We’re also still looking at ways to stream it live, so please leave ideas in the comments. Thanks!

As always, the full podcast will be available here on the blog on Wednesday.

If you missed the tweets earlier today, interspersed between BarCamp NewsInnovation Philly updates, Max Cutler announced that Courant News now has a live project website. From the first blog post, it sounds as though the project began in a very similar environment as CoPress:

It all began last summer, when we came up with an idea for a startup company: an online publishing platform for college news organizations. We wanted to be a better alternative to College Publisher – a content management system for college news organizations designed by college news organizations.

They’ve built a CMS, we’ve gone the community organizing route. Because we consider CoPress platform agnostic, it will be interesting to see how our paths intersect.

Max Cutler says that Courant News should be out by BarCamp NewsInnovation Philly, however:

Courant will not really be ready for actual use or consumption upon its open-source-ing. The core set of functionality is essentially complete, which means you can build a news website which functions well for the visitors. However, we still haven’t had time to implement our vision for the admin interface, which is really the whole point of doing a specialized “news CMS.” It’s currently just a more-or-less stock Django admin, which, while functional, is far from ideal and really only marginally better than using Drupal with CCK or similar options.

As I’ve said publicly and privately in the past few days, the acronym “CMS” stands for Content Management System. That implies that the purpose of the system is actual management of content, which for a website would be through an admin interface. So I claim that the most important part of a CMS is the admin interface, and thus I can’t consider Courant ready for an actual site until we’ve taken at least our first pass at a news administrative interface.

Needless to say, we’ve very excited to see a nearly final product of what Max and company have been working on for 9+ months. There should be a spec out for community review later this week.