January 20, 2011 § Leave a comment
- JLab JLab – So you want to start a local news site? News Site in a Box, a learning module written by @markbriggs, will show you how http://bit.ly/9IHfO9
- ryanjz Ryan J. Zeigler – Hundreds Of Dead Birds In South Dakota Were Killed By U.S. Government (VIDEO) http://bit.ly/huQo3H
- scarequotes James Callan – In Seattle? Want a #contentstrategy jump start? Don’t miss @ticjones‘s workshop at @svcseattle: http://bit.ly/eFQWle
- NiemanLab Nieman Lab – Boston.com welcomes in the hackers and unveils its digital test kitchenhttp://nie.mn/eZ48Nf
- BenLaMothe Ben LaMothe – Usernames vs. Real Names on Your Online Community: Pros and Conshttp://feedly.com/k/f4qtil
- Poynter Poynter – Somebody call the Plagiarism Police on the Daily Mail. (Many passages appeared first in NYT.) http://journ.us/fmF10I
- SarahDayOwen Sarah Day Owen – Great resource! RT @webjournalist: Here’s a page I maintain listing tools – updating soon: http://bit.ly/f7kyNt
- BrentDPayne Brent D. Payne – SEO Tip: If your site’s homepage ONLY has your company name in the HTML Title tag, you are doing it wrong. Pick 3 keyphrases to work in.
- pottsmark Mark Potts – Recovering Journalist: Newspapers Still Not Out of the Woods—If Ever:http://bit.ly/eLEFsI
- craignewman Craig Newman – The online pay model not as catastrophic for newspapers as predicted?http://craig.mn/hhJK7V Depends on model, most likely.
- hbillings Heather Billings – Great tip! RT @jeffsonderman: How to customize the way @Storify looks when embedded in your site http://bit.ly/exN3Xh #hackshackers #wjchat
January 20, 2011 § Leave a comment
A new year gives me the opportunity at work to create new
resolutions goals that are tied to my duties as online manager (MBO). There are the obvious ones
like finally launching a mobile version of Union-Bulletin.com without spending much money and without hiring a mobile developer. I’ve got some ideas on how to do that using WordPress but I’ll leave that to another post.
Another obvious one is a slight redesign of our website and registration/log in forms. Which leads me to my not so obvious goals. I’ve decided to read some tech books and/or take a number of NewsU online courses/webinars. As part of my goals I will then write a short proposal on how to integrate what I learn into our online products.
First up, I’ve enrolled for Friday’s NewsU webinar Programming for Non-Geeks: Easy Interactivity which hopes to teach:
- How to get started: which software you need and where to get it
- Some basic techniques to enhance your content, even as a non-programmer
- What plugins are and which one plugins to consider when creating news-oriented content
- About tools to make your jQuery development easier
- About top resources to know and bookmark
And I’ve got a small library of books I plan to read, including:
- Don’t Make Me Think – A Common Sense Approach to Web Usability by Steve Krug
- Advanced Web Metrics with Google Analytics by Brian Clifton
- The Yahoo Style Guide
- Mediactive by Dan Gillmor
- Content Strategy for the Web by Kristina Halvorson
I’ve started reading all of them and I am most excited about Don’t Make Me Think since it will a great resource for our planned redesign of our forms. I will blog over the next several months about my “takeaways” and implementation plans based on what I learn.
Oh, and I also plan on blogging regularly again. That may be the most daunting goal!
January 31, 2009 § 10 Comments
This idea is not new. But it has been bubbling in my head for a few months: how to incorporate a wiki or wikis into our online content. We’ve tried a couple of wikis in the past couple years as part of our in-depth series but we struggled with how to allow contributions. We ended up only allowing comments/threads. Not what most people would consider a wiki.
About 2 years ago Amy Grahan wrote a column over at Poynter about the idea of news org wikis. She wrote:
Most notably, wikis can transcend the short attention span and fragmented view of issues and events inherent in traditional story-format reporting. With a wiki, no topic ever really “scrolls off the home page.” Wiki pages are forever active — even if they lie fallow for long stretches of time. And interested people can continue to watch and edit these pages indefinitely.”
In her post Amy asks for examples of wikis implemented by news orgs. As far as I can tell there were no examples given of implementation as I envision it.
A number of experiments with wikis have already shown its potential to both reach out to a readership – and to fall flat on its face. An example of the latter was the LA Times ‘wikitorial’ – an editorial piece on the Iraq war which the newspaper allowed readers to edit. After only a day the newspaper had to pull the feature due to readers flooding the site with inappropriate material.
On the positive side, however, was Wired’s experiment with the form late last year, when they allowed readers to whip an unedited article about (yes) wiki technology into shape. Over 300 users made edits, with one interviewing a Harvard expert, and another suggesting a contact – and when one user complained about some quotes from an interviewee, the original journalist, Ryan Singel, posted his interview notes so that users could pick a better one.
Paul also posted a more in-depth examination of possible uses of wikis in news orgs. In that post he wrote:
Internally, wikis also allow news operations to coordinate and manage a complex story which involves a number of contributors. News organisations interested in transparency might also publish the wiki ‘live’ as it develops, so readers can view as it develops, and look at previous versions, while the discussion space which accompanies each entry also has the potential to create a productive dialogue with users.
This refers to the idea of using a wiki to develop a story online.
Typically a story is posted on a news org website which occasionally generates a list of related stories. Perhaps a photo or two are posted as well. If there is a video, that might be embedded into the story. And usually that is the end of context.
My wiki/archive idea would work like this:
A story posted on a new org website would also have a link to its wiki/archive page. The wiki/archive page would display all related content in a chronological thread (maybe utilizing some nifty AJAX coding so that you don’t have an endlessly scrolling experience.)
- related stories including any comments posted by the public
- multimedia including slideshows, etc.
- related tags
- a timeline
- annotations by editors and reporters
- Online vandalism. Shane Richmond wrote a piece on this for the Telegraph UK. Shane wrote:
The trouble is Wikipedia, as ‘the public face of wikis’ is frequently derided for inaccuracies and vandalism. Will the mainstream media be able to surmount those problems?
…will the wiki dream be killed off through the fear of cyber vandals treating our news websites as virgin walls for virtual graffiti?
- The NY Times recently reported on Wikipedia incorporating a new system to keep those types of edits off. We could have a stringent registration process but I’m not sure that it would be a wiki at that point.
- Too much transparency. In my opinion this isn’t a reasonable concern. Strike-throughs and footnotes should be included in stories on news org websistes to alert the reader to errors or edits. Many news orgs are already doing this.
- Information overload. This feature may not be useful for many stories or even for many news org customers. But with a well designed interface it would be a great resource for community members to follow stories that have developed over months or years.
- Not many users know what wikis are. Paul Bradshaw sites some statistics:
Finally, one of the biggest disadvantages may be readers’ lack of awareness of what a wiki even is: only 2% of Internet users even know what a wiki is, although similar statistics were once applicable to blogs.
So maybe calling it a wiki is the wrong thing to do. Maybe it would be more precise to call it a contextual archive of news stories. Although I think incorporation wiki conventions such as public input via comments and edits (after a reasonable registration to preclude trolls) should be a big part of this feature.
What do you think are the pros and cons of something like this; for journalists and consumers of information? Are there news orgs already doing this?
January 24, 2009 § 2 Comments
I’ll answer that. I think I should gain some web programming skills. But what?
Flash/Action-script? That would come in handy to produce some slick multilmedia packages like this one.
Drupal/Django/Joomla/Ruby on Rails? This would help in developing a custom CMS or a slick community calendar app. But it looks like that is time and programming intensive. Maybe a bit over my head. Definitely intimidating.
PHP? That would help us customize and tweak WordPress plus if I add some XML in there we could do some database driven stuff.
I hate being in the position where I see a great web app and not being able to duplicate it or tweak it or customize it. For instance all the great APIs out there made available by Google, Twitter, Facebook, etc. As a news organization we do not have the personnel to do much of any of this. And we mostly likely will never have the staff to do it. So I feel like it’s up to me and in addition I develop a bigger skill set that will make me a more valuable employee/freelancer/entrepreneur.
Or should I just stick to content creation via video. Maybe I need to just expand my FCP skills. I admit my FCP skills are pretty limited – color correction is a big weakness. What to do? What to learn. My time is so very limited between work and family. I need to be prudent with what I pursue. What would you suggest?
I mean, what skills do I need to build something like this video player that lets you navigate to a part of a video by picking a spot on a transcript?