<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:media="http://search.yahoo.com/mrss/"
><channel><title>CoPress &#187; Mustang Daily</title> <atom:link href="http://www.copress.org/tag/mustang-daily/feed/" rel="self" type="application/rss+xml" /><link>http://www.copress.org</link> <description>Building a Better Technical Ecosystem for Student News Organizations</description> <lastBuildDate>Mon, 08 Mar 2010 18:46:04 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.1.1</generator> <image><title>CoPress</title> <url>http://www.copress.org/media/2009/01/copress_100x100_notrans.png</url><link>http://www.copress.org</link> <width>100</width> <height>100</height> <description>Building a Better Technical Ecosystem for Student News Organizations</description> </image> <copyright>2006-2007 </copyright> <managingEditor>website@copress.org (CoPress)</managingEditor> <webMaster>website@copress.org (CoPress)</webMaster> <image> <url>http://host.copresshosting.com/~copress/main/wp-content/plugins/podpress/images/powered_by_podpress.jpg</url><title>CoPress &#187; Mustang Daily</title><link>http://www.copress.org</link> <width>144</width> <height>144</height> </image> <itunes:subtitle></itunes:subtitle> <itunes:summary>Building a better technical ecosystem for student news organizations</itunes:summary> <itunes:keywords></itunes:keywords> <itunes:category text="Society &amp; Culture" /> <itunes:author>CoPress</itunes:author> <itunes:owner> <itunes:name>CoPress</itunes:name> <itunes:email>website@copress.org</itunes:email> </itunes:owner> <itunes:block>no</itunes:block> <itunes:explicit>no</itunes:explicit> <itunes:image href="http://host.copresshosting.com/~copress/main/wp-content/plugins/podpress/images/powered_by_podpress_large.jpg" /> <item><title>How to break news the right way</title><link>http://www.copress.org/2009/12/08/how-to-break-news-the-right-way/</link> <comments>http://www.copress.org/2009/12/08/how-to-break-news-the-right-way/#comments</comments> <pubDate>Tue, 08 Dec 2009 18:15:56 +0000</pubDate> <dc:creator>Lauren Rabaino</dc:creator> <category><![CDATA[Reports from the Field]]></category> <category><![CDATA[breaking stories]]></category> <category><![CDATA[caching]]></category> <category><![CDATA[Google News]]></category> <category><![CDATA[Mustang Daily]]></category> <category><![CDATA[website performance]]></category> <category><![CDATA[WordPress]]></category> <category><![CDATA[WP Super Cache]]></category><guid
isPermaLink="false">http://www.copress.org/?p=3242</guid> <description><![CDATA[When news that a Cal Poly student had gone missing hit the Mustang Daily newsroom, editors knew they had a big story on their hands. The next morning when the student&#8217;s bike was found at the base of a local mountain, the implications for the story were larger. The editors were on the cusp of [...]]]></description> <content:encoded><![CDATA[<p><img
class="alignright size-full wp-image-3243" title="breaking-news" src="http://www.copress.org/media/2009/12/breaking-news.jpg" alt="breaking-news" width="221" height="161" /><br
/> When news that <a
href="http://mustangdaily.net/cal-poly-student-missing-since-monday/">a Cal Poly student had gone missing</a> hit the Mustang Daily newsroom, editors knew they had a big story on their hands. The next morning when <a
href="http://mustangdaily.net/update-missing-students-bike-found/">the student&#8217;s bike was found</a> at the base of a local mountain, the implications for the story were larger. The editors were on the cusp of a breaking news story and a potentially huge influx of traffic.</p><p>Then <a
href="http://mustangdaily.net/breaking-news-missing-student-found/">a body was found</a>. And like clockwork, the traffic spiked.</p><p>Was the Mustang Daily prepared? Strategically, yes. They had five editors on the scene of the incident. Technically? Perhaps not. Their site went down for a few minutes (and was quickly fixed when CoPress received the notification). Here are a few steps the editors could have taken to prepare. <em>(Full disclosure: one of the authors of this post, Lauren Rabaino, is a former editor of the Mustang Daily.)</em></p><h3>1. Keep your site delivering the story</h3><p>When you&#8217;re about to break major news, you will need to prepare your Web site for the upcoming onslaught of traffic. If you&#8217;re using WordPress, that will mean making your site as static as possible. <a
title="WP Super Cache" href="http://wordpress.org/extend/plugins/wp-super-cache/">WP Super Cache</a> contains a feature known as Lock Down that allows you to make your site completely static — in other words, posts will be saved as flat HTML files, dramatically decreasing server load and dramatically increasing the chance that when someone visits your Web site, they&#8217;ll be served something other than an error. There are two drawbacks to using Lock Down that you should know about up front:<img
class="alignright size-full wp-image-3254" title="Super Cache" src="http://www.copress.org/media/2009/12/Super-Cache.jpg" alt="Super Cache" width="289" height="204" /></p><ul><li> Comments will not show up until the page is refreshed, either manually or by turning off Lock Down.</li><li> Updates to stories will not be pushed without dumping the cache manually.</li></ul><p>These, however, are small prices to pay for making sure visitors can read the article at all.</p><p>If you don&#8217;t have WP Super Cache installed already, you should — it smoothes over spikes in traffic and reduces server load even when it isn&#8217;t in Lock Down mode.</p><p>To enable Lock Down mode, go to Settings -&gt; WP Super Cache.</p><p>Near the bottom of the page, you will see a button to enable Lock Down mode.</p><p>At the top of the page, you will see an option to Delete Expired and Delete Cache. If you update one of your articles or want newer comments to show on the page, you will have to hit Delete Cache.</p><p>If you are a CoPress client and you expect a huge spike in traffic, let us know ahead of time and we&#8217;ll be around to actively monitor your site and keep it delivering pageviews.</p><h3>2. Make sure your article gets read</h3><p>Google News is a great way to gain traffic, especially when big news breaks. If your site isn&#8217;t already on Google News, or if your site is incompatible with Google News, <a
href="http://www.copress.org/2009/11/19/using-google-news-to-drive-traffic-to-your-site/">fixing any problems</a> and <a
href="http://www.google.com/support/news_pub/bin/request.py?contact_type=suggest_content">submitting your site for review</a> should be the first step of optimizing your Web site.</p><p><img
class="alignnone size-full wp-image-3251" src="http://www.copress.org/media/2009/12/tamae-Google-News.jpg" /></p><p>When updating the story, the decision about whether to do a write-thru or post a new story goes a long way toward driving traffic to your site. Google News will not re-index a news story after it has been published, even if you use <a
href="http://wordpress.org/extend/plugins/google-sitemap-generator/">a sitemap generator like Google XML Sitemaps</a>. Therefore, if there is any sort of a major development in the story, and certainly if there is one big enough to warrant a change of headline, it is imperative the article is put into a new post for SEO.</p><p>Targeting your regular readership is also important. Plugins like <a
href="http://wordpress.org/extend/plugins/sms-text-message/">SMS Text Message</a> and <a
href="http://wordpress.org/extend/plugins/courier/">Courier</a> allow you to quickly and easily notify your readers when news breaks or when there are updates.   Be sure to use keywords in your tweets so anyone going to search.twitter.com can find your updates. For developing news, create a new #hashtag related to the topic for readers to follow throughout your coverage for example (#missingstudent or #polydeath).</p><p><img
class="alignright size-full wp-image-3247" src="http://www.copress.org/media/2009/12/facebook.jpg" alt="facebook" width="334" height="167" />Twitter can be an easy way to notify readers, but by far the best social networking site for you to focus on is Facebook. If there is a Facebook page or group concerning the news, post a link to your Web site. Have your reporters post links on their walls and Twitter accounts. Together, these two mediums can drive hundreds or thousands of visitors to your Web site. For example, the day news broke about the student suicide at Cal Poly, more than half of the Mustang Daily&#8217;s pageviews for the day were referred from Facebook (56.6 percent, to be exact).</p><p>All these strategies should be deployed within minutes of the article&#8217;s post. If you are one of the first media organizations to report on the news, you need to hook as many readers as possible and convince them that your newspaper is <em>the</em> ultimate source on this subject. This is only possible if they learn about it first from you.</p><p>When you update the article — which you should do, frequently — or when a big update comes in that warrants a new article — which should happen, though with less frequency — be sure to let your readers know. Don&#8217;t spam your readers, but find a point right before they start feeling harassed when they&#8217;ll be grateful for keeping you informed.</p><p>Finally, if you are expecting you might create a new story when a big enough update comes in, link your homepage on Facebook and in e-mails instead of the story itself, so when readers visit the site they see the newest news first. Also, when you create a new story, it is a good idea to link to it at the top of the old one.</p><h3>3. Develop an editorial strategy</h3><p>The best way to break news is to have <a
href="http://www.collegemediainnovation.org/blog/2009/03/game-plan-for-covering-breaking-news/">a game plan in place</a> so you&#8217;re not scrounging for reporters and photographers at the last minute. Here are a few steps you might want to try:</p><ul><li><strong>Designate a breaking news &#8220;leader.&#8221;</strong> This person can be in charge of delegating responsibilities to reporters and photographers when news breaks and posting Twitter and Facebook updates throughout the day.</li><li><strong>Have a breaking news emergency kit.</strong> The worst thing that can happen when news breaks is that the video camera is checked out or the batteries are dead. If you have the resources to do so, keep a spare camera, tripod and batteries in the newsroom solely for breaking news purposes</li><li><strong>Know the workflow.</strong> You don&#8217;t have to have a multi-sourced, 500-word article before posting updates to your site and Twitter. Break news as it happens and get your staff into the mindset of posting breaking news nuggets as it happens. Updates can always come later.</li><li><strong>Listen to your readers.</strong> Breaking news is perhaps one of the best opportunities to use reader feedback while reporting. Let your readers submit their questions and tips via social media so you can integrate it into the reporting process. If the breaking news event is a scene (fire, protest, etc.), seek user-submitted photos and video.</li></ul> ]]></content:encoded> <wfw:commentRss>http://www.copress.org/2009/12/08/how-to-break-news-the-right-way/feed/</wfw:commentRss> <slash:comments>3</slash:comments> </item> <item><title>Wiki software comparison for newspapers</title><link>http://www.copress.org/2009/06/04/wiki-software-comparison-for-newspapers/</link> <comments>http://www.copress.org/2009/06/04/wiki-software-comparison-for-newspapers/#comments</comments> <pubDate>Thu, 04 Jun 2009 21:28:46 +0000</pubDate> <dc:creator>Lauren Rabaino</dc:creator> <category><![CDATA[Leading Strategy]]></category> <category><![CDATA[collaboration]]></category> <category><![CDATA[collaborative reporting]]></category> <category><![CDATA[CoPress Wiki]]></category> <category><![CDATA[MediaWiki]]></category> <category><![CDATA[Mustang Daily]]></category> <category><![CDATA[reviews]]></category> <category><![CDATA[user generated content]]></category> <category><![CDATA[wikis]]></category> <category><![CDATA[WikiSpaces]]></category> <category><![CDATA[WordPress]]></category> <category><![CDATA[WordPress Wiki]]></category><guid
isPermaLink="false">http://www.copress.org/?p=1993</guid> <description><![CDATA[A review of three possible wiki software: MediaWiki, WordPress Wiki, or WikiSpaces. Lauren suggests WikiSpaces for its ease of use and simple setup process.]]></description> <content:encoded><![CDATA[<p>Wikis for news organizations have been a <a
href="http://www.copress.org/2009/02/18/whats-in-a-news-wiki/">buzzing topic</a> recently as both a means of spreading news and <a
href="http://mustangdaily.wikispaces.com">passing down information to future editors</a>. If creating a wiki is your summer plans, you&#8217;ll need to use software that meets your needs. </p><h3>MediaWiki</h3><p><strong>Rating:</strong><img
class="alignnone size-full wp-image-1997" src="http://www.copress.org/media/2009/06/4of5.jpg" alt="4of5" /></p><p><img
class="alignnone size-full wp-image-1998" src="http://www.copress.org/media/2009/06/media-wiki.jpg" alt="media-wiki" width="447" height="214" /></p><p>This is perhaps the most well-known wiki software, especially because of its use by Wikipedia. It&#8217;s the open source software that is used on the <a
href="http://copress.org/wiki">CoPress wiki</a>.</p><p>For your readers, this might be the functionality they&#8217;re most familiar with on the front end, but the complexity of the back end could intimidate and deter people from contributing.</p><p><img
class="alignnone size-full wp-image-2009" src="http://www.copress.org/media/2009/06/mediawiki-code.jpg" alt="mediawiki-code" width="447" height="214" /></p><p>If you put a helpful guide showing users how to edit the wiki and use the system&#8217;s formatting, they might be more likely to contribute. You have to be able to set up a MySQL database for your wiki, but it&#8217;s easily done. Setup is straight forward process that only takes a few minutes.<br
/> <span
id="more-1993"></span></p><ul><li>Price: Free</li><li>Open source</li><li>Requires installation</li><li>Requires database setup</li><li>Anyone can login to edit</li><li>Customizable skins using CSS</li><li>Must learn <a
href="http://www.mediawiki.org/wiki/Help:Formatting">MediaWiki markup</a></li></ul><p><a
href="http://www.mediawiki.org/wiki/Download">Download MediaWiki</a></p><h3>WordPress Wiki</h3><p><strong>Rating:</strong><img
class="alignnone size-full wp-image-1995" src="http://www.copress.org/media/2009/06/1of5.jpg" alt="1of5" /></p><p>If you want the wiki to match the brand of your site rather than the typical wiki look, you can use the WordPress wiki plugin  (assuming, of course, that you&#8217;re running WordPress).</p><p>Editing is straight forward because you edit the pages just like posts, and simply mark the &#8220;wiki page&#8221; option to designate wiki status.</p><p><img
class="alignnone size-full wp-image-1999" src="http://www.copress.org/media/2009/06/wiki-options.jpg" alt="wiki-options" /></p><p>The catch, though, is that for users to edit a page, an administrator must create a &#8220;Wiki Editor&#8221; user who has access to the backend of your site. That user is only allowed to edit pages designated as editable by an administrator, but the notion of having many users access the admin end of your site may make you uncomfortable.</p><p><img
class="alignnone size-full wp-image-2000" src="http://www.copress.org/media/2009/06/wiki-new-default-role.jpg" alt="wiki-new-default-role" /></p><ul><li>Price: Free</li><li>Upload and activate the plugin</li><li>Does not require database set up</li><li>Only designated users can edit pages</li><li>Minimally customizable</li><li>Updates are easy once a system is established</li><li>May be hard to organize once you start accumulating many pages</li><li>Users can&#8217;t create new pages, only edit existing pages</li></ul><p>If you do decide to go with this software, it would probably be best to create one account called &#8220;WikiEditor&#8221; and post the username and password at the bottom of each editable page. Create a separate page or category under which all wiki posts can fall.</p><p><a
href="http://wp-wiki.org/">Download WP-Wiki plugin</a></p><h3>WikiSpaces</h3><p><img
class="alignnone size-full wp-image-2001" src="http://www.copress.org/media/2009/06/wikispaces.jpg" alt="wikispaces" width="447" height="214" /></p><p>Rating:<img
class="alignnone size-full wp-image-1994" src="http://www.copress.org/media/2009/06/3of5.jpg" alt="3of5" /></p><p>If this is all too complicated, there is a free service that does the hosting for you. WikiSpaces is a simple solution to your wiki woes. All you have to do is sign up for an account.</p><ul><li>Price: Free</li><li>Doesn&#8217;t require installation</li><li>Does not require database set up</li><li>Anyone can make an account and edit pages</li><li>Can change colors; must pay to change CSS</li><li>Free version has advertisements</li></ul><p>This is the ideal option if you have no idea how to set up a new database or if you want something that feels more intuitive for your users to update. WikiSpaces doesn&#8217;t require users to learn complicated formatting language; it uses a clean WYSIWYG editor. The downside is that if you want full control over the look and feel and ads, you have to pay for a pro version.</p><p><a
href="https://www.wikispaces.com/user/join?goto=">Sign up for WikiSpaces</a></p><h3>Other options</h3><p>These are by no means the only wiki software out there. These are just the systems with which I have experience. Wikipedia has a <a
href="http://en.wikipedia.org/wiki/List_of_wiki_software">full list of wiki software too</a>. If you have any suggestions or experiences, please share.</p> ]]></content:encoded> <wfw:commentRss>http://www.copress.org/2009/06/04/wiki-software-comparison-for-newspapers/feed/</wfw:commentRss> <slash:comments>2</slash:comments> </item> <item><title>We Clicked On: Get to work</title><link>http://www.copress.org/2009/05/15/we-clicked-on-get-to-work/</link> <comments>http://www.copress.org/2009/05/15/we-clicked-on-get-to-work/#comments</comments> <pubDate>Fri, 15 May 2009 22:44:20 +0000</pubDate> <dc:creator>Daniel Bachhuber</dc:creator> <category><![CDATA[We Clicked On]]></category> <category><![CDATA[CoPress Wiki]]></category> <category><![CDATA[entrepreneurship]]></category> <category><![CDATA[ideas]]></category> <category><![CDATA[innovation]]></category> <category><![CDATA[Mustang Daily]]></category> <category><![CDATA[student newspapers]]></category> <category><![CDATA[summer 2009]]></category> <category><![CDATA[WordPress]]></category><guid
isPermaLink="false">http://www.copress.org/?p=1849</guid> <description><![CDATA[We&#8217;re changing things up! Our choice of the best links of the week are now at the top of We Clicked On (via the CoPress Publish2 Newsgroup): Owned? Legal terms of video hosting services compared &#8211; Joey Baker: Video sharing sites treat your copyright differently. Summary: the best sites are the most restrictive. 4 productive [...]]]></description> <content:encoded><![CDATA[<p>We&#8217;re changing things up! Our choice of the best links of the week are now at the top of We Clicked On (via the <a
href="http://www.publish2.com/newsgroups/copress/">CoPress Publish2 Newsgroup</a>):</p><ul><li><a
href="http://advancingusability.wordpress.com/2009/05/06/owned-legal-terms-of-video-hosting-services-compared/">Owned? Legal terms of video hosting services compared</a> &#8211; Joey Baker: Video sharing sites treat your copyright differently. Summary: the best sites are the most restrictive.<li><li><a
href="http://www.collegemediainnovation.org/blog/2009/05/14/4-productive-summer-projects-for-j-students/">4 productive summer projects for j-students</a> &#8211; Daniel Bachhuber: Proactive summer J project ideas from @laurenmichell. It would be sweet to see experimentation with the news wiki.</li><li><a
href="http://freepizza.cc/2009/03/14/10-ideas-i-want-to-try-at-the-newspaper-where-i-work/">10 Ideas I Want to Try at the Newspaper Where I Work</a> &#8211; Daniel Bachhuber: I dig the ideas Will has for community relationship management, as well as using data and APIs well.</li><li><a
href="http://ecorner.stanford.edu/authorMaterialInfo.html?mid=2242">Steve Ballmer, Microsoft &#8211; The Future of Microsoft, The Future of Technology</a> &#8211; Daniel Bachhuber: Steve Balmer makes a case for entrepreneurship in the economic downturn.</li></ul><p><embed
id='single' width='500' height='302' flashvars='config=http://ecorner.stanford.edu/embeded_config.xml%3Fmid%3D2242' src='http://ecorner.stanford.edu/swf/player-ec.swf' type='application/x-shockwave-flash'></embed></p><p>The most notable news of the week, however, is that Greg taught me the stylistic considerations of headlines and subheads.</p><h3>Activity around the network</h3><p>In the forum this week, Joey <a
href="http://www.copress.org/forum/weekly-discussion-topics/your-wordpress-workflow-may-11-2009/">asked the crowd about their editorial workflows within WordPress</a>. Lauren Rabaino left the lengthiest answer, <a
href="http://www.copress.org/forum/weekly-discussion-topics/your-wordpress-workflow-may-11-2009/#p147">explaining in detail how the Mustang Daily is currently operating their web-first workflow</a>. Writers upload their documents into WordPress, and then the editing happens within the CMS. The information about these interactions is managed in a Google Spreadsheet.</p><p><span
id="more-1849"></span>The wiki is where the real party was happening this week. Related to the Mustang Daily&#8217;s workflow, a few of us have been sketching out a spec to build functionality into WordPress to enhance editorial workflows, and enable newspapers like the Mustang Daily to conduct their entire operation within the CMS instead of having to add a Google Spreadsheet on top. These ideas have materialized in the form of the <a
href="http://copress.org/wiki/Edit_Flow_Project">Edit Flow Project</a>. Look for a more detail post on the project&#8217;s goals next week.</p><p>Also on the wiki, Lauren Rabaino has been doing a stellar job <a
href="http://copress.org/wiki/CoPress_Network">adding more student news organizations to the Network directory</a>. Late last night I had an &#8220;aha!&#8221; moment when I figured out you could apply meta data of a sort to these directory pages. The result? Sorting by <a
href="http://copress.org/wiki/Category:WordPress">CMS</a>, <a
href="http://copress.org/wiki/Category:Washington">location</a>, or <a
href="http://copress.org/wiki/Category:Daily_Newspaper">type of publication</a>. As we add more information to the system, hopefully with your help, this will become an increasingly useful database of what student news organizations across the nation are doing with their web technology. If your organization is missing, please feel free to add it by following the <a
href="http://copress.org/wiki/CoPress_Network">criteria at the top of the Network page</a>.</p> ]]></content:encoded> <wfw:commentRss>http://www.copress.org/2009/05/15/we-clicked-on-get-to-work/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>Online Editor: No longer a one-person job</title><link>http://www.copress.org/2009/05/12/online-editor-no-longer-a-one-person-job/</link> <comments>http://www.copress.org/2009/05/12/online-editor-no-longer-a-one-person-job/#comments</comments> <pubDate>Tue, 12 May 2009 20:23:30 +0000</pubDate> <dc:creator>Lauren Rabaino</dc:creator> <category><![CDATA[Leading Strategy]]></category> <category><![CDATA[Daily Tar Heel]]></category> <category><![CDATA[hiring]]></category> <category><![CDATA[Mustang Daily]]></category> <category><![CDATA[restructuring]]></category> <category><![CDATA[staff organization]]></category> <category><![CDATA[student newspapers]]></category> <category><![CDATA[team building]]></category><guid
isPermaLink="false">http://www.copress.org/?p=1777</guid> <description><![CDATA[As the school year winds down to an end, many news organizations are searching for the next online editor. If you already have your next online editor, then the summer is a perfect time for him or her to brush up on necessary skills that will make your news website flourish. Finding the balance Ideally, [...]]]></description> <content:encoded><![CDATA[<p>As the school year winds down to an end, many news organizations are searching for the next online editor. If you already have your next online editor, then the summer is a perfect time for him or her to brush up on necessary skills that will make your news website flourish.</p><h3>Finding the balance</h3><p><img
src="http://www.copress.org/media/2009/05/2v1rp84.jpg" alt="Balancing social media" title="Balancing social media" class="alignright size-full wp-image-1832" />Ideally, an online editor will have both the tech-smarts and the journalism abilities to present news content in web-friendly way. You can teach someone how to embed a video from YouTube or add a new article to a CMS, but teaching someone how to write a lead can&#8217;t be done through an hour-long training session. </p><h3>Splitting the job</h3><p>Increasingly, the responsiblity of maintaining the website is more than a one-man show.</p><p>As Andrew Spittle <a
href="http://www.copress.org/forum/weekly-discussion-topics/what-do-you-look-for-in-an-online-editor/#p127">suggested in the CoPress forum</a>, the best way to balance the job is to split the web position into a web developer and web editorial position.  Editing articles in addition to training the staff for multimedia year-round leaves little time to focus on developing new features. </p><p><span
id="more-1777"></span>As Andrew said <a
href="http://www.copress.org/forum/weekly-discussion-topics/what-do-you-look-for-in-an-online-editor/#p127">in the forum</a>:</p><blockquote><p>The web editor will be attending story meetings and will be functioning in a similar fashion to a section editor. This position is not requiring web skills. Knowledge is a bonus, but not a requirement.</p></blockquote><p>Max Cutler has <a
href="http://www.copress.org/forum/weekly-discussion-topics/what-do-you-look-for-in-an-online-editor/#p128">a similar take</a>:</p><blockquote><p>In my mind, the Online Editor should be someone with editorial and multimedia experience, who can direct editorial initiatives and help produce good multimedia content for the website. It&#8217;s my job as the developer to build out any infrastructure and code to support the Online Editor&#8217;s plans. Of course, that process is a give-and-take one, but it certainly helps to have that division of responsibilities.</p></blockquote><p>By splitting the job into a distinct content-based position and a developer position, both aspects can flourish together. The editor can train reporters and editors in multimedia skills and help produce multimedia and web content. The developer can work on long-term features and site functionality. Together, the two can produce long-term, multimedia-based projects. </p><p><strong>Requirements for the web editor position:</strong></p><ul><li>Copy editing experience</li><li>Reporting experince (especially on a deadline for breaking news situations)</li><li>Multimedia: video, audio slideshows, basic Flash, podcasting</li><li>Basic HTML</li><li>Writing for the web (links, keywords)</li><li>Familiarity with Facebook, Twitter, FriendFeed, etc.</li></ul><p><strong>Requirements for the web developer position:</strong></p><ul><li>Experience with your respective CMS (and the related language)</li><li>HTML/CSS</li><li>Video/audio editing</li><li>Flash</li><li>A portfolio of Web sites to prove he/she has all these skills</li></ul><p>Additional skills that would be preffered but certainly not required (since they&#8217;re easily learned) are:  live streaming, blogging, Google maps, and live chats.</p><h3>Going beyond basic skills</h3><p>Both the Web Editor and Developer should have a vision for the future of the site and an understanding of a newspaper&#8217;s needs during a time of immense change in the journalism industry.</p><p>Staying on top of trends in the journalism world will mean reading blogs, following innovators online, going to conferences, actively browsing through news sites — and then using all that information to brainstorm new ideas.</p><p>A few questions to put on the application to gague the potential editor on the aforementioned topics would be:</p><ul><li>What would you improve on the current Web site?</li><li>What are your thoughts on the use of social media in a news organization?</li><li>Which new media blogs do you read regularly?</li><li>What&#8217;s your vision for the Web site?</li><li>How does your background prepare you for a job as online editor/developer?</li><li>What are three projects you could start working on immediately? (<a
href="http://www.copress.org/forum/weekly-discussion-topics/what-do-you-look-for-in-an-online-editor/#p126">via Daniel Bachhuber</a>)</li><li>What do you see as the biggest challenge facing the newspaper &#038; how do you plan to address it? (<a
href="http://twitter.com/andrewspittle/status/1666486349">via Andrew Spittle</a>)</li></ul><p>An online editor needs to be patient and open-minded above all else. Even at the college level, there is still a lot of resistance to the web. Your team of webbies needs to be able to combat the nay-sayers in the newsroom with optimimism. </p><p>Training reporters will also require a large dose of patience. Despite the supposed tech-savviness of Generation Y, I&#8217;ve learned that just because you&#8217;re born after 1982 doesn&#8217;t mean you&#8217;re programmed with Final Cut skills. Repetition, hands-on learning and positive encouragement will keep everyone else on their toes. </p><p>The ability to learn and teach is also important; most of what the online editor teaches other reporters and editors will be self-learned. Thus, teamwork is a must.</p><h3>The next steps</h3><p>If  your news organization already has a functioning web editor/developer team, or a solid balance between well-trained reporters and a talented web producer, then this is all old news for you. It&#8217;s time to consider expanding your web team.</p><p><strong>Web Advertising Manager</strong> - This person&#8217;s job would be solely dedicated to finding ways to generate revenue online. This position would be highly experimental and, again, based on keeping up with trends, reading a lot of blog posts and generating new ideas. This person would<em> not</em> merely post regurgitated print ads onto the site.</p><p><strong>Community Manager</strong> - This person could promote content and connection with your readers over social media. <a
href="http://dunnreporter.com/">Andrew Dunn</a> from the <a
href="http://www.dailytarheel.com/">Daily Tar Heel</a> has already implemented this <a
href="http://twitter.com/andrew_dunn/status/1666823133">idea</a> by hiring a community manager (<a
href="http://www.scribd.com/doc/14814823/Community-Manager-Application">see the application</a>).</p><p>A concept I like from the Tar Heel&#8217;s job description is an aggregated news source:</p><blockquote><p>He or she (the community manager) will maintain a site hosted on <a
href="http://www.dailytarheel.com/">dailytarheel.com</a> that aggregates and highlights local online content, from blogs, Twitter feeds and other news sites.</p></blockquote><p>More responsibilities could include: responding to all at-replies on Twitter, keeping the Twitter conversation relevant and fresh, promoting content on Facebook by linking to articles with the newspaper&#8217;s Facebook Page, posting albums to Flickr and encouraging user-generated photo groups, and looking for new online outlets to reach out to the community.</p> ]]></content:encoded> <wfw:commentRss>http://www.copress.org/2009/05/12/online-editor-no-longer-a-one-person-job/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> <item><title>This Week in CoPress: The Mustang Daily&#8217;s Switch to WordPress</title><link>http://www.copress.org/2009/04/29/this-week-in-copress-the-mustang-dailys-switch-to-wordpress/</link> <comments>http://www.copress.org/2009/04/29/this-week-in-copress-the-mustang-dailys-switch-to-wordpress/#comments</comments> <pubDate>Wed, 29 Apr 2009 19:57:54 +0000</pubDate> <dc:creator>Emily Kostic</dc:creator> <category><![CDATA[This Week in CoPress]]></category> <category><![CDATA[discussions]]></category> <category><![CDATA[interviews]]></category> <category><![CDATA[Mustang Daily]]></category> <category><![CDATA[podcasts]]></category> <category><![CDATA[website launches]]></category> <category><![CDATA[WordPress]]></category><guid
isPermaLink="false">http://www.copress.org/?p=1711</guid> <description><![CDATA[Hosts: Greg Linch and Emily Kostic Guests: Lauren Rabaino, Web Editor and Marlize van Romburgh, Editor in Chief of The Mustang Daily Summary: Lauren Rabaino and Marlize Van Romburgh swap stories with Greg and Emily as the four discuss each of their college newspapers transitions to WordPress. Subscribe: iTunes &#124; RSS]]></description> <content:encoded><![CDATA[<p><strong>Hosts:</strong> <a
href="http://www.greglinch.com">Greg Linch</a> and <a
href="http://www.emilykostic.com">Emily Kostic</a></p><p><strong>Guests:</strong> <a
href="http://www.laurenrabaino.com/">Lauren Rabaino</a>, Web Editor and <a
href="http://marlize.me/">Marlize van Romburgh</a>, Editor in Chief of The Mustang Daily</p><p><strong>Summary:</strong> Lauren Rabaino and Marlize Van Romburgh swap stories with Greg and Emily as the four discuss each of their college newspapers transitions to WordPress.</p><p><strong>Subscribe:</strong> <a
href="http://phobos.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=299105930">iTunes</a> | <a
href="http://feeds.copress.org/copress/twic">RSS</a></p> ]]></content:encoded> <wfw:commentRss>http://www.copress.org/2009/04/29/this-week-in-copress-the-mustang-dailys-switch-to-wordpress/feed/</wfw:commentRss> <slash:comments>0</slash:comments> <enclosure
url="http://www.copress.org/podpress_trac/feed/1711/0/copress20090429mustangdailywordpress.mp3" length="15671905" type="audio/mpeg" /> <itunes:duration>0:28:58</itunes:duration> <itunes:subtitle>Hosts: Greg Linch and Emily KosticGuests: Lauren Rabaino, Web Editor and Marlize van Romburgh, Editor in Chief of The Mustang DailySummary: Lauren Rabaino and Marlize ...</itunes:subtitle> <itunes:summary>Hosts: Greg Linch and Emily KosticGuests: Lauren Rabaino, Web Editor and Marlize van Romburgh, Editor in Chief of The Mustang DailySummary: Lauren Rabaino and Marlize Van Romburgh swap stories with Greg and Emily as the four discuss each of their college newspapers transitions to Wordpress.Subscribe: iTunes &#124; RSS</itunes:summary> <itunes:keywords></itunes:keywords> <itunes:author>website@copress.org</itunes:author> <itunes:explicit>no</itunes:explicit> <itunes:block>no</itunes:block> </item> <item><title>Designing a Better Editorial Workflow for WordPress</title><link>http://www.copress.org/2009/04/22/designing-a-better-editorial-workflow-for-wordpress/</link> <comments>http://www.copress.org/2009/04/22/designing-a-better-editorial-workflow-for-wordpress/#comments</comments> <pubDate>Thu, 23 Apr 2009 00:40:55 +0000</pubDate> <dc:creator>Daniel Bachhuber</dc:creator> <category><![CDATA[We Clicked On]]></category> <category><![CDATA[code projects]]></category> <category><![CDATA[editorial workflow]]></category> <category><![CDATA[Mustang Daily]]></category> <category><![CDATA[web-first publishing]]></category> <category><![CDATA[WordPress]]></category><guid
isPermaLink="false">http://www.copress.org/?p=1663</guid> <description><![CDATA[Lauren Rabaino published a constructive blog post a couple days ago on how the Mustang Daily is adjusting to a web-first workflow. From the looks of it, they&#8217;re asking and answering a number of questions that other news organizations will behaving further along the line: Who copy edits when? Does the section editor look at [...]]]></description> <content:encoded><![CDATA[<p>Lauren Rabaino published a constructive blog post a couple days ago on <a
href="http://rabaino.com/lauren/blog/?p=767">how the Mustang Daily is adjusting to a web-first workflow</a>. From the looks of it, they&#8217;re asking and answering a number of questions that other news organizations will behaving further along the line:</p><blockquote><p>Who copy edits when? Does the section editor look at the article first or last? Can an article be posted to the Web without the section editor’s approval?  These are the questions we’ve asked ourselves these past few days. Section editors (news, arts, sports) have a huge problem with articles being posted to the Web without their approval. Gradually, we’re figuring it out.</p></blockquote><p>Related to this, several of us had a conference call this morning to <a
href="http://inside.copress.org/2009/04/22/improving-wordpresss-admin-for-newsrooms/">discuss ways in which the WordPress admin could be enhanced for editorial workflow</a> (and address many of the technical issues organizations like the Mustang Daily are facing). For instance, I think it would be useful if editors could receive an email when a post is ready for their reading, as well as different types of statuses if, for instance, the editor needed to send the post back to the reporter for a rewrite.</p> ]]></content:encoded> <wfw:commentRss>http://www.copress.org/2009/04/22/designing-a-better-editorial-workflow-for-wordpress/feed/</wfw:commentRss> <slash:comments>0</slash:comments> </item> <item><title>Behind the Scenes of Mustang Daily&#8217;s New WordPress Website</title><link>http://www.copress.org/2009/04/13/behind-the-scenes-of-mustang-dailys-new-wordpress-website/</link> <comments>http://www.copress.org/2009/04/13/behind-the-scenes-of-mustang-dailys-new-wordpress-website/#comments</comments> <pubDate>Tue, 14 Apr 2009 04:20:25 +0000</pubDate> <dc:creator>Lauren Rabaino</dc:creator> <category><![CDATA[Team Announcements]]></category> <category><![CDATA[College Publisher]]></category> <category><![CDATA[CoPress Hosting]]></category> <category><![CDATA[Mustang Daily]]></category> <category><![CDATA[website launches]]></category> <category><![CDATA[WordPress]]></category> <category><![CDATA[WordPress Plugins]]></category><guid
isPermaLink="false">http://www.copress.org/?p=1595</guid> <description><![CDATA[Today &#8212; four months after first learning about CoPress through Twitter &#8212;  the Mustang Daily launched its new WordPress site, hosted and supported by CoPress. The Mustang Daily, a 2008 Online Pacemaker Winner and 2009 Pacemaker Finalist, had been with College Publisher since 2006.   Website Design We went with the Gazette Edition from WooThemes because [...]]]></description> <content:encoded><![CDATA[<p>Today &#8212; four months after first learning about CoPress through Twitter &#8212;  the <a
href="http://www.mustangdaily.net">Mustang Daily</a> launched its new WordPress site, hosted and supported by CoPress. The Mustang Daily, a <a
href="http://www.studentpress.org/nspa/winners/opm08.html">2008 Online Pacemaker Winner</a> and <a
href="http://www.studentpress.org/nspa/winners/opm09.html">2009 Pacemaker Finalist</a>, had been with <a
href="http://www.collegepublisher.com">College Publisher</a> since 2006.</p><p
style="text-align: center;"><a
href="http://www.mustangdaily.net/"><img
class="size-full wp-image-1605 aligncenter" title="Mustang Daily" src="http://www.copress.org/media/2009/04/mustangdailyhome_h500.jpg" alt="Mustang Daily" width="500" height="341" /></a><br
/>  </p><h3>Website Design</h3><p>We went with the <a
href="http://www.woothemes.com/2008/02/the-gazette-edition/">Gazette Edition</a> from <a
href="http://www.woothemes.com">WooThemes</a> because it gave us all the basic capabilities we were looking for:</p><ul><li>Prominent ads</li><li>Wigetized sidebar</li><li>Slick, rotating slideshow</li><li>Auto-generated thumbnails</li></ul><h3>Advertising</h3><p><img
src="http://www.copress.org/media/2009/04/mustangdailypagepeel_h500.jpg" alt="Page Peel" title="Page Peel" class="aligncenter size-full wp-image-1608" /></p><p>During a time when revenue is falling, having full control over priority ad space is a must. We have a top banner (468 x 60 pixels), a sidebar ad (300 x 250 pixels) and up to four square ads on the lower sidebar (125 x 125 pixels).</p><p>We installed a WordPress plugin that allows for a &#8220;page peel&#8221; style advertisement in the top corner of the site. Although probably annoying to some, people like playing with it.</p><p><span
id="more-1595"></span></p><h3>Plugins Used</h3><p>The following plugins give us functionality that College Publisher would never allow for (or at least not easily).</p><p><strong><a
href="http://wordpress.org/extend/plugins/twitter-tools/">Twitter Tools</a></strong> lets us easily post new articles and tweets straight from the admin end of WordPress. Why this is great: We don&#8217;t have to give every reporter the Twitter password and it streamlines the process of tweeting a new article. Posting links to articles is acceptable in moderation and when it&#8217;s supplemented with plenty of converstaion.</p><p><img
src="http://www.copress.org/media/2009/04/iphpnen.jpg" alt="iphpnen" title="iphpnen" class="alignright size-full wp-image-1609" width="200px" /><strong><a
href="http://www.bravenewcode.com/wptouch/">WP-Touch</a></strong> generates a mobile version of our site. If you don&#8217;t have a smart phone, you might not care, but this fall at Cal Poly, six hundred students on campus used iPhones &#8212; 500 more than in the spring, according to Ryan Matteson, the university&#8217;s technical security officer. My point: mobile is on the rise.</p><p>Another mobile plugin we&#8217;re excited about is for the non-smart phone users who want to get SMS updates. <strong><a
href="http://wordpress.org/extend/plugins/sms-text-message/">SMS Text Message</a></strong> is a plug we&#8217;re excited about, but have yet to use. It allows users to subscribe for text message alerts and lets us send out those alerts from the dashboard.</p><p>We&#8217;re using the <strong><a
href="http://wordpress.org/extend/plugins/add-to-any/">Add to Any</a></strong> plugin for users to share our content over any social network. Although Share This is more widely recognizing for sharing, I chose Add to Any because it lets us customize the look of the button.</p><h3>Structural Changes to the Daily</h3><p>On a <a
href="http://www.collegemediainnovation.org/blog/2009/04/13/mustang-daily-leaves-college-publisher-launches-wordpress-site/">CICM post</a>, I briefly mentioned the structural changes that came with the switch. To elaborate, this is how our workflow will function from here on out:</p><ul><li>Reporters save their articles as a WordPress draft (instead of e-mailing articles to editors)</li><li>The reporter contacts copy editors when the article is in the CMS, copy editors will edit from the newroom or home (wherever they happen to be)</li><li>We&#8217;ve hired an additional copy editor and switched up the shifts so there is always a copy editor on-call during the day</li><li>There is an ongoing Google Spreadsheet of most recent articles posted. After editing the article, the copy editor signs off on the article on the spreadsheet</li><li>The third editor to read over the story pushes &#8220;publish&#8221; if they think it&#8217;s ready. If it still needs work, it can go through the process again</li><li>In the evening, designers pull already-edited articles from WordPress for page layout</li></ul><p>The delay time between when a reporter writes the article and the editor posts it is about four hours. Right now, it&#8217;s not to efficient because our reporters are new (and therefore their articles need much editing) and the workflow is still slow. It will only get better from here.</p><h3>The Back End</h3><p>The hierarchy is broken down as such:</p><ul><li>Three administrators (not including CoPress) who have full access to all features</li><li>About ten editors who can publish articles</li><li>Ten contributors (reporters) who can save drafts, but not publish</li></ul><h3>New Features</h3><p><img
src="http://www.copress.org/media/2009/04/policelog.jpg" alt="policelog" title="policelog" class="alignright size-full wp-image-1610" />Although we certainly didn&#8217;t need WordPress to implement the following new features to our website, having WordPress has made it way easier to execute <a
href="http://www.collegemediainnovation.org/blog/2009/04/13/three-easy-features-that-add-value-to-your-site/">these ideas</a> we&#8217;ve had:</p><ul><li><strong>Crime map:</strong> WordPress pages make adding new, easily-accessible features very easy. Within a few minutes, we were able to throw together a <a
href="http://mustangdaily.net/police-log/">Google Map of the police log</a> that we plan to update daily.</li><li><strong>Hot topics</strong>: We&#8217;ve always wanted to re-ignite an old feature called &#8220;What&#8217;s the Buzz?&#8221; but creating and maintaining pages was always a headache. Again, within minutes we were able to <a
href="http://mustangdaily.net/hot-topics/">generate pages around controversial issues on our campus</a>. Eventually, we&#8217;ll have a wiki to supplement each topic.</li></ul><h3>What&#8217;s Next?</h3><p>Now that the process of posting is more streamlined (or, it&#8217;s getting there), the goal is to produce better multimedia. My efforts can be focused on training reporters one-on-one instead of copying and pasting articles at the end of the night.</p> ]]></content:encoded> <wfw:commentRss>http://www.copress.org/2009/04/13/behind-the-scenes-of-mustang-dailys-new-wordpress-website/feed/</wfw:commentRss> <slash:comments>4</slash:comments> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 25/56 queries in 0.162 seconds using disk

Served from: www.copress.org @ 2012-02-08 22:22:00 -->
