How To Plan A Code4LibCon/ContentPlan

From Code4Lib
Revision as of 14:52, 14 August 2015 by Moneill (Talk | contribs) (Goals)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Content Plan

Internal Communications


External Communications


Conference Lead-Up:

  • The community knows about/knows the timeline for the following as soon as the timeline is available (in chronological order):
 * Conference/Pre-Conference dates
 * Keynote Speaker submission dates
 * Conference and hotel registration dates, information
 * Keynote Speaker voting
 * Talk submission guidelines and dates
 * Talk voting
 * Conference schedule
 * Last-minute conference details
  • It might be worth considering whether to create a conference email list of attendees, vendors, etc. so as not to clog the listserv with emails not relevant to the folks not at the conference? Was there discussion about this last year?
  • Decide who counts as the internal audience -- just the local planning committee? What about conference management and/or hotel staff? Others?

During the Conference

  • Conference attendees, and possibly the community at large, are informed as quickly and efficiently as possible about:
 * Events (especially social events)
 * Schedule changes
 * Issues with the livestream, if any
 * Other breaking news

After the Conference

  • Communicate any wrapping-up news, including:
 * Video of talks posting to YouTube
 * Community thanks as relevant

Roles and Responsibilities

During the conference:

  • Official information Tweeter
  • Official information IRC chat-er
  • Official information emailer