http://www.mediabistro.com/10000words/the-new-convoluted-life-cycle-of-a...
Always start in a blog form — i.e., your quickest way of publishing.
If the update is significant enough that, in print, it would merit its own new headline, then create a new blog post, rather than an update to an older post.
Try to build in an automated way of linking to the most recent coverage. In our CMS, this would mean building an ESI. In WordPress, you could use a shortcode. Some other CMSes will probably have an equivalent component that could be updated universally across stories.
There should be no rush to point to the print story unless it provides a significantly different angle than what the blog posts said. Ideally, in a crazy world that many newsrooms might not be ready for yet, the entire web CMS is the same as the blogging CMS, and story types don’t differ based on “posts” and “print stories,” and the print stories don’t necessarily have to be on the web because they’re not made for the web– they’re made to be read on a piece of dead tree with no additional context.For big news items, there’s more incentive to build out some kind of landing page that pulls in all the content related to a certain topic, but doing that for all the day-to-day stories isn’t sustainable. However, it is these small day-to-day stories that need to have the threads connected because these stories constitute a bulk of the coverage at our news organizations. Ideally, we’d need to create a way to institutionalize the interconnectedness of our coverage.