I’ve mentioned before the problems with the website of Trinity News. Essentially, we don’t have the staff to manually copy-and-paste the 45,000 or so words per issue, and when we’re lucky enough to have someone willing, they inevitably get bored and quit after a few sessions doing this mind-numbing, repetitive and uninspiring task. That’s why, apart from the PDFs of every issue this year, the site is out of date. So that needs to change.

The problem is that there is no easy, all-in-one non-technical solution. The elements that need to be incorporated are:

• XML export from InDesign
• Import of print content to website
• A quality, reliable Content Management System
• User-friendly backend for web-only content
• Backward-compatibility with existing archive (in MySQL databse)
• Accessible enough to be passed on to my successor without too much difficulty
• Multimedia capability
• Staff blogs

Now, there are a number of ways to go about this. ExpressionEngine uses custom fields that could be paired up with specific XML tags. Drupal has an entire open-source project on newspapers with a lot of work being done to integrate print design exports. And the Daily Tar Heel has a very interesting project called The Magic Bullet where they’re hiring an outside web developer to create their “magic bullet”: a customized, tick-all-the-boxes solution for their particular setup.

I don’t have those kind of resources available to me. I do have a summer, a lot of dedication, and a committed staff. I need to find my own “magic bullet” and I’m looking for input. Should I go with Drupal, with their open information? ExpressionEngine, which I currently use for this blog, and their paid professional support? Or some other solution I’ve never heard of? If anyone has experience or success with a small college newspaper (small compared to the Daily Tar Heel, anyway) integrating their print and online workflows, get in touch. I’ll update over the summer as this project progresses, and, if successful, maybe other student papers can benefit too.

Posted by Dave Molloy in •Journalism •Tech
(0) Comments | Permalink