This document summarizes experiments with online communities conducted by the Knight Foundation. It describes the roles of a community manager, the workflow for releasing content, and two specific online communities - the News Challenge Garage and Knight Pulse. The News Challenge Garage hosted projects, meetups, and mentoring. Knight Pulse launched as a beta site about news and information innovation, featuring video conversations. Next steps discussed include gathering feedback and integrating Knight Foundation's online presences.
1 of 14
More Related Content
Presentation for OSI of Knight Online Communities
1. Experiments in Online Community
from the Knight Foundation
presentation to OSI 1.21.09
3. roles the community manager 鍖lls
Web producer
video producer
video editor
video personality
video researcher
marketing/promotion
community moderator
blogger
4. work鍖ow for a release
press release for internal prep; community manager reads
research, create video/images
edit & upload video/images (send to team for preview, inclusion in press release)
press release goes up, KF home page public (uses video/images)
Knight Pulse upload post and video to other sites
Knight Blog post up with video, link to press release
@knightfdn tweet and link to Pulse and blog
@knightpulse tweet and call out (@) speci鍖c Twitter users
5. News Challenge Garage
1620 users
445 projects
3 months
6 weeks to design and build
accompanied by meetups in NYC, SF, Seattle, Vancouver, Austin,
Chicago, D.C. by Susan Mernit and Kristen Taylor
8. Big Draw:
Anyone in the Garage could apply
for a mentor (mostly past winners)
to work through the idea in the
Garage (publicly)
10. Knight Pulse launched in beta
Nov. 10, 2008
community site
about future of news and information
highlights projects in media innovation and active information (50% KF)
features video conversations as new content in Phase 1
articles from Tor with video commenting featured
planning for Phase 2 now
13. whats next
gathering feedback on Phase 1 of Pulse
better help text on Pulse
de鍖ning user actions on Pulse that could also happen elsewhere
integrating across Knight Blog, Pulse, Twitter account, external services