1 / 10

EET Website - Roadblocks

EET Website - Roadblocks. Our systems. Photo gallery. Running Main website Support platforms But have no content to feed them. Pod cast. Main EET website theepochtimes.com. Google News. Print archive. E-newsletter. Syndication. Social media. Our websites.

corbin
Download Presentation

EET Website - Roadblocks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EET Website - Roadblocks

  2. Our systems Photo gallery • Running • Main website • Support platforms • But have no content to feed them Podcast Main EET websitetheepochtimes.com Google News Print archive E-newsletter Syndication Social media

  3. Our websites • Our main website still brings in most readers…

  4. CMS -> Web transition • Articles • Posted on CMS (editors) • From CMS to web (web eds) • Problems • Long delays (few web eds) • Increasing number of reporters/ editors posting to CMS • No increase in web eds • Duplicate work; effort and time totally wasted CMS EET website Readers Reporters/editors Web Editors

  5. Lifetime of a typical news story We need to catch the story here if we want to get readers/traffic (which is what Project SOAR aims to do) • But because of • Workflow: • CMS/web • Articles written for print • we usually publish here. No more interest, no readers. Michael Jackson story

  6. Recent example • Story written on December 24th ; Published in print on Dec. 25th • Published on website on Dec. 27th • 3 days after the story!!!

  7. Time and effort • We are getting more and more reporters (and editors?) posting to CMS • But their articles are not being read because being published late. • Assume 1 article = 1 hour of effort • Our top 5 reporters write 1000 articles a year = 1000 hours of work • And no one to read them because we publish late!

  8. Pageviews and revenue - lost • Right now, our traffic • 1.2 million pageviews a month • $1600 + $250 = $1850 in affiliate ad revenue(not counting in-house ads sold by staff) • SOAR articles get 5x – 10x regular web traffic • If we published all articles on time • 1.2M x 5 = 6 million pageviews a month • $1850 x 5 = $9250 in affiliate ad revenue(without anyone selling ads!)

  9. How to solve this • Need more web editors • But no “added value,” they are only copy-pasting • No time to do anything else than check CMS • Might be the only way to currently solve problem • Have one integrated system for print/web workflow • So all reporters/editors can post on website • Web editors only need to check and publish • They can “add value” (pull quotes, multimedia, etc.) rather than just copy-paste and re-edit

  10. How to solve this - II • Improve workflow • Once reporters write an article: wait for editor? • Roles not clearly defined? Can web eds edit? • Cover web/news 24x7 • We need web editors who can cover 24x7 • And reporters too • Anything else?

More Related