Community Project Community lives in the spray of this information flow. People will be sharing resources in their blogs, facebook, etc, yet these can end up as just lists of links. We will explore having the teams responsible for “curating” from this flow into something that provides context for the resources (e.g. “why is it valuable?” “how does it apply to our work?”).
Nancy and I are exploring ways for the #ProjComm15 to generate a community built resource. There are many ways to group curate content yet most involve asking you to Sign Up For Another Tool And Go There All The Time. We want to try something easier that works into the flow we are already asking you to do– use your team blog.
When you find a resource really worth sharing, most typically people push it to a social media stream, our facebook group, maybe even twitter with our hashtag more or less saying “here is something neat”. That works if you happen to see it, but it just rushes on by. We still encourage you to do this as a stream of raw information resource just include a #projcomm15 tag in it; it will flow into our tagboard.
But go one step farther. If the resource is really useful, write a short blog post on your blog. Make sure you add a tag (a box for tags is on the side of your composer and add the tag coolstuff (one word, no space), and any othe useful descriptor tags. When published, all of these post will show up on our site via http://2015.projectcommunity.info/tag/coolstuff Automatically. Without using another new tool.
When you blog, be sure to write more than “This is cool”. Explain why you chose it, what is its value/relevance to our community. Or maybe its an opinion you disagree with. Our resource collection is much more useful when you provide context.
One tool we also considered we Storify. It creates a space you can choose media and links from many places, specify the order, add context, and share back.
For example, here is what Nancy collected recently: