Full audio of the hour-long call can be heard below.

During the debrief, each team member wrapped up a significant takeaway that they’ve gained from being involved with CoPress:

Andrew Spittle, Hosting Director:

“I think the biggest takeaway I’ve found both from working with CoPress and also starting out as the web staff at the Whitman Pioneer is that a lot of things seem sort of intimidating at first … the best thing to do for yourself as an individual and the news organization you work for is to just jump in.”

Lauren Rabaino, former Creative Director:

“The power of collaboration… Aside from the annual conferences we go to, newspaper editors we meet once, we brainstorm and then never see each other again. CoPress provided the platform for us to actually continue that interaction beyond the face-to-face meeting. The community we built was something that didn’t exist before and I think it will continue to exist after CoPress the organization has gone away.”

Albert Sun, Hosting Associate:

“This stuff, it’s not that hard. The best way to go and try something … We didn’t come in just knowing a huge ton about what we’re doing now. It was just a learning process through the same thing, the same sort of process anyone can go through. Don’t be afraid.”

Will Davis, Hosting Associate:

“What I’m really proud of is just really being able to delv into projects and set my sights on finer problems … and really take time to delv into that problem and solve it. For example, Courier was the answer to a problem we had on our website and it was something that CoPress allowed me to do.”

Daniel Bachhuber, Executive Director:

“What I most wanted to see come out of CoPress and what I’m most happy to see happening now is people taking initiative, but then having this community discussion/place/area where people can convene and share knowledge … I’m happy to see that starting to happen finally. That’s what it was all about in the beginning.”

Why is CoPress shutting down?

The question that we received on Twitter and that was echoed in the call boiled down to the cut and dry: Why is CoPress shutting down now?

As Daniel noted, the honest truth of why we’re closing down operations is because the money-making side of our business wasn’t covering the effort we were putting into it and the business wasn’t scaling.

We encourage innovation. We encourage experimentation. We believe that the best way to learn how to code is to build something and break it — and CoPress would have your back to save it. While it’s a great philosophy, it’s not a business model.

“As it turned out, we were answering a lot of stuff for free, meaning we weren’t billing people for it,” Daniel said. “The way we structured our turnkey hosting is that you get full access to the server, you get full access to the software, install whatever plugins you want, and break the site as much as possible and we’ll answer your questions and help you bring the site back up. Our pricing strcuture didn’t reflect that offering in a logical way.”

What services will fill the void?

We’ve learned that the biggest challenge in moving to open source software is how to transition site data and archives from proprietary software. After that process is complete, organizations have the ability to be largely independent.

One option is to open source our transition process and allow other entrepreneurs to sell those services as independent contractors to set up newspapers on third-party hosting.

Even with CoPress’ operations terminated, we’d like to see the network that formed around CoPress continue to rally for innovation. Whether that looks like a Google Group, weekly conference call, forum, etc. is yet to be determined.

It’s time for the community to take ownership.

First, we’ve struggled with making our business financially viable while at the same time offering prices that reflect an understanding of the financial situation many student news organizations are in. This is even more apparent in that we’ve had to change our pricing structure twice in the past months.

Secondly, without the revenue to pay our team full-time, we’ve become dependent on the generosity of committed students to offer our 24/7 support. In addition, the nature of our hosting and support business is such that we encouraged publications to tinker as much as they want with their site. What this ultimately meant was a rapidly growing number of emails for us to answer. Needless to say, it’s become difficult to make this scale in any meaningful way. Our eventual goal was to build software for distributed support, but the resources required for hosting and support severely challenged our ability to make headway on the project.

By now, we’ve contacted all of our existing clients about this decision. Because of the way we’ve structured our Managed Hosting since August 2008, the transition for most will be as easy as changing the credit cards on their third-party hosting account. We intend to migrate the other sites from the servers we maintain to third-party hosting services like WebFaction and Slicehost.

Going forward, we also intend to reopen our list serv as a place for the community to ask and respond to more general support questions. We also hope to put together a list of WordPress consultants you can hire to help with more technical issues or extended projects. Lastly, we’re going to open source our database conversion script which makes it a lot easier to get archives of various form into WordPress. If you’re interested in being on this list of consultants, please contact us.

We think that story of CoPress highlights some of the most important needs for college media, and the news industry in general. Primarily, this is a willingness to experiment, iterate, and try new things. As such, we’d plan to post in the coming weeks as much as we can about what we learned along the way with the sincere hope of teaching what lessons we can to the next round of entrepreneurs.

If you have any questions, please don’t hesitate to ask them in the comments or contact us privately. We’ll be holding a public Skype conference call that anyone is welcome to join sometime early next week.

On behalf of everyone on the team, I’d like to thank everyone for the support of our efforts. We couldn’t have accomplished any of this without the tireless contributions of too many awesome people in the community to count.

Daniel Bachhuber
Executive Director, CoPress
daniel@copress.org

We want to find an answer.

For those of us in the college media industry, understanding how students find, share and consume news is an important part of reaching that audience.

There are general assumptions, of course. We all say that print is dying among generation y and that students get their news online. But how is it being replaced?

Even among the CoPress team there’s huge diversity in the way news is consumed, from Daniel Bachhuber, who reads 250 RSS feeds a day, to Will Davis who reads three broadsheet newspapers a day. We want to find out what goes on beyond our circle so that you — the college editors, reporters and developers — can better structure your news for that audience.

So we’re asking for your help. We’ve compiled a survey of questions about the way college students consume news, and we need you to spread the word. Pass this link along to your classmates, retweet it, blog about it. It won’t be a scientific survey, but it will tell us more about our community and the students associated with our community.

Our goal is to get 200 responses in two weeks and we can’t do it alone. Have at it and keep an eye on the blog over the next few weeks where we will publish the findings.

…or click here to fill out the survey

The everyday user will notice improvements to the latest version of the plugin. A few weeks ago I pushed out Courier 0.3, and in the intervening few weeks have pushed out minor updates to add a few new functionalities and fix a few typos and errors.

Courier 0.3 includes major improvements to both stability and functionality. The biggest and most important improvement is queuing support. Instead of sending all e-mails at once when you click the send, the plugin instead queues the e-mails and sends them at a rate you determine. Not only does this protect you in the case the script hangs up when you’re sending e-mails (such as when you have thousands of subscribers), but it also makes sure the e-mail script doesn’t take down the entire server.

This new feature uses WP Cron to minimize setup time. You can schedule a test e-mail in the Courier dashboard to make sure WP Cron works. If it doesn’t you have a few options: you can disable queuing in the dashboard, which I don’t recommend if you have a number of subscribers, or you can set up Crontab to visit wp-cron.php every minute. I would recommend finding the root cause of why WP Cron doesn’t fire, though — otherwise you might have bigger problems than Courier not working correctly.

Courier 0.3 integrates with WordPress users, allowing you to manage subscriptions within the WordPress profile. It still supports users outside of WordPress, and I have no plans to phase out that support.

Courier 0.3.5 includes a sidebar widget, so you can now add the registration form to your sidebar.

I should note that if you upgrade Courier outside of WordPress (i.e. through FTP) you will need to deactivate and reactivate Courier before many of the new features will takeeffect.

If you’re testing Courier and run into any problems, please feel free to e-mail me (will@copress.org), and I will be glad to help. I am hoping to have a major (1.0) release out within two weeks, and if you encounter any errors or anomalies it’s important they be fixed before then.

Finally, Courier now has a new website, wpcourier.com, where you can stay attuned to all Courier news and updates. The site will include best practices for create e-mail editions and curating users. You can also follow Courier’s updates on Twitter @wpcourier.

This idea for a distributed network of support is still a very real dream for us but we soon realized, thanks to Bryan Murley, that there were intermediate steps we needed to cover first. Most importantly, this included supporting student news organizations with a turnkey hosting solution they could experiment with. We started our Managed Hosting program in January 2009 and launched our first site, The Whit, shortly after that.

Since then, we’ve migrated and launched more than 35 WordPress-powered websites, including The Red and Black, the UWM Post, and the QU Chronicle in the past week. It’s a learning experience for us as much as it is for the news organizations with which we work. For instance, as the largest site we’ve worked with thus far, The Red and Black has offered unique performance challenges that I had the fortune to work on during my wifi-enabled flight back from our team meetup in Philly this weekend.

As a part of our goal to increase the number of opportunities for collaboration and knowledge-sharing in 2009, we also held regular workshops throughout the summer and fall, published reports from the field on our blog, started development on the Edit Flow Project, and connected with the network at conferences including BarCamp NewsInnovation Philly and ACP/CMA in Austin.

We’re committed to executing our vision for the future of journalism. Our original philosophy for hosting and support, though, involved a one-size-fits-all solution that we’ve come to realize isn’t the best long-term approach to scaling our efforts. As such, we’ve relaunched our hosting and support plan again (we did it once in August too) with four tiers of service: basic, standard, full, and premium. Based on our experiences of the last year, we think the offerings better reflect the needs of different types and sizes of publications; for some, it’s fine if theme changes are made on the production site whereas others should have a development sandbox and deployment process. The new prices will be applicable to all of our new sign-ups, and existing publications will be guaranteed their current prices through the end of their invoice plus three months.

For the spring and into the summer, our goal is to ramp up the collaboration opportunities. That’s the true value of having a well-connected network of student webmasters and developers.

Let’s do it.

Nando

First up Max gave us an update on where development on Nando stands. As Lauren mentioned last week, Nando is the administrative side of the Courant News CMS. Max and Rob Baskin will be developing the templates for the interface and I’ll be working with them on designing the user interface and experience. The project is in the early stages right now but wireframes for the interface will be released soon so stay tuned to the Google Group for updates.

Edit Flow

Daniel also recapped what will be happening with Edit Flow over break. Work will be ramping up on version 0.3 of the plugin which will include more granular control over email notifications and user groups. Other features include some bug fixes as well as visualizing posts through a calendar-like interface.

Courier

Will Davis also filled us in on some of the work that will be done on Courier, his plugin for better email notifications. Courier already has support for custom templates and will be gaining further subscription options. The plugin update should be released before the end of break so stay tuned for updates.

Tar Heel iPhone app

Finally, Andrew Dunn talked a bit about The Daily Tar Heel’s iPhone app that he announced on Thursday. The app includes their Housing Guide as well as all the news, classifieds, and radio that you’d expect. It also has a feature that Andrew talked about on the call: a drink specials mini-app.

To hear more about all of the above projects listen to the full audio below.

We want to extend a very special congratulations to the College Heights Herald, winner of the best Publication Website among large schools.

This past Thursday we ran the first of what will become a bi-weekly series. We’re calling it “Hacking the Student Newsroom.” Each session will lead you through a specific skill related to WordPress and college news that you can implement immediately. We’ll also do our best to record the workshops for those who can’t make the scheduled date. This week’s session was on setting up a sandbox in WordPress.

A sandbox provides a great test environment where you can experiment with both ideas and code without having to worry about breaking things. Your Web staff and any others that are interested in learning about WordPress can also use a sandbox to teach themselves some great new skills.

We covered everything from creating a subdomain for a sandbox to the proper way to configure your development version of WordPress. For those who want a test site to test edits that will be made to the production site, we went over how to transfer your theme and plugin files so that everything is as similar as possible.

On the wiki, we started a cheat sheet of how to set up your own sandbox. We’ll be adding to it, and you’re more than welcome to contribute as well.

Why a sandbox?

The advantage to having a sandbox is that these sites can be a great way to test out those ideas that you’re not sure quite how to implement or design. They provide a great test environment where you can experiment with ideas and code without having to worry about breaking things. Your Web staff and any others that are interested in learning about WordPress can use it to teach themselves some great new skills.

Thursday’s session is open to everyone, and we’ll be leading you through from start to finish on how to set up a demo instance of WordPress. We’ll show you how to create a subdomain on which to install WordPress plus lead you through each step of configuring the software. From creating the database to installing themes and plugins or getting some dummy content in there, we’ll cover it all.

If there’s time left over, we’ll also be open to discussing any and all questions you may have.

This is a great opportunity if you’ve ever wanted someone to show you how to start hacking a WordPress theme. CoPress team members will be there to answer your questions in real time — no more clogging up your inbox!

Sound interesting? Head on over to the Facebook event to RSVP and we’ll get the details out to you. Let’s start hacking!

CM Life

Brian Manzullo, Editor in Chief

After a summer-long process of transitioning from College Publisher and building a new design, Central Michigan Life launched its new WordPress-powered site on Aug. 20. One aim for this site was to create a more simple, clutter-free look that was visually appealing but also straightforward enough that readers don’t have headaches trying to find what they’re looking for. Our photos and social networking elements are more prominent and the different story subtopics that people might want to follow exclusively are visible (e.g. football, money). Most of all, though, we wanted freedom with our Web site. We have control of all advertising and all of the different elements on our site, meaning we can try new things quite easily if we wish. My hope, however, is that we don’t stop with the makeover. The real goal is to keep readers engaged with our online presentation, whether it is through live chats, Twitter, Facebook or story comments. We feel that we can better connect them to issues that matter, and we will work hard to utilize our site in doing so.

Daily Titan

Chris Ullyott, Webmaster

We launched our new Web site, www.dailytitan.com, on Aug. 10. It was a task to learn WordPress from the very beginning but, in short order, we began to see how the theming system worked and were able to successfully make fundamental changes to the software. With the help of the nice people at CoPress, brilliant plugins, and some elbow grease, we were able to customize our WordPress theme to suit the specific needs of both our editorial and advertising staffs. Now we have a much more attractive, intuitive, and useful online presence.

The biggest advantage over our previous system is the amount control we now have over both the visual and technical aspects of our site. We now have complete control over:

• Roles and privileges of staff user accounts for a better workflow
• Sizes and placement of advertisements for more revenue opportunities
• Distribution of content with RSS feeds, accommodating for breaking news
• Integration of third-party services like Twitter and ISSUU
• Linkage throughout the site for a better user experience

We can see major opportunities for university media using open-source content management systems. The amount of control one can have takes a little getting used to! However, WordPress is fairly simple to learn, and any committed media student can quickly learn the HTML, CSS and PHP coding techniques needed to make improvements to a WordPress theme without re-inventing the wheel.

Currently on our site, we’re particularly proud of the “stay connected” widget bar we added, which lets users immediately connect with our social media presence and use other distribution channels like podcasts and email subscriptions. We also can’t get over how cool our new media kit is, courtesy of our talented design staff. The Issuu viewer makes the presentation sing.

The custom navigation bars proved a fruitful project for us as well. By rewriting the header navigation code with plain old HTML and CSS, we strictly separated editorial from advertising content and gave special pages more appropriate homes. Users clearly now have it easier in finding what they need. Since we launched, our bounce rate has dropped a whopping 30%.

We have already received very positive response both in online traffic and personal comments. We look forward to seeing what our experience will be like once the school semester starts this year. New additions we’re working on include section forums, dining and housing guides, creative online use of editorial columns, and integration of a gutsy “furlough edition”…

Thanks to CoPress for all of your help. Let’s show our campuses what news is really all about!

UA Traveler

Jon Schleuss, Web Developer

It’s better to teach someone a skill rather than do a task for them. Our move to WordPress allows for more control by the individual students rather than lumping the responsibilities onto one Web guru. Choosing the Gazette theme, we followed similar steps taken by the Mustang Daily and implemented a custom header logo different from our print edition to make a distinction between our products. This year’s staff includes students focused on the print edition and others focused on the Web. That’s not to say the content doesn’t intermingle, however. We’re now prioritizing content based on the delivery method. Moving forward, we’re strategizing an innovation of Web advertising and diversifying our Web delivery methods. Expect a mobile version of our new site and one that’s delivered in an e-mail sent each week.