Group items tagged

EtherPad also allows revision saving coupled with restoration from stored versions, something not found in SubEthaEdit

chronological archived discussion alongside the live space

backchannel discussion about what's being written that doesn't belong in the document itself

Wiki Etiquette

Build structure:

Take it personally: Yes, colleagues will edit your work and you might not agree with every change, but that's the nature of collaboration. It doesn't mean that your co-workers dislike you or think you're stupid. Ignore questions: Colleagues may disagree with your changes and ask why you made them. If so, be prepared to give concrete reasons for your edits. Delete useful content: Many times a posting can be improved by amending or editing it, but deleting content upsets people, and they may feel they've wasted their time. Be chatty: A wiki shouldn't be used as a chat room. Any discussions related to a wiki subject should take place on the discussion or talk page, not on the actual content page. Keep it secret: If you find valuable content on your company's wiki, tell others about it. Wikis benefit from a wide range of contributors.

Mugshot makes it easy to keep up with what your friends are doing online at different sites, all in one place.

Best Practices Learn how the pros achieve higher productivity through enhanced collaboration. Attention Management - Reduce time wasted in the Inbox. CC to Wiki - Get around the curse of Reply-to-All. Collaborating on a non wiki page using a wiki page - Use the attachment feature to collaborate on presentation files, etc. Designing Spaces - Key considerations for creating new spaces. Developing a Public Blogging Strategy Distributed Document Review Gardening and Wiki gardening tips Index Pages - create starting points for navigation around topics of interest. Lightning Editing - how to co-edit a document with a collaborator Securing buy-in - getting others to shift perspectives on wikis Sparking participation at events Using the workspace as a document repository

Best Practices Learn how the pros achieve higher productivity through enhanced collaboration > . > Attention Management > - Reduce time wasted in the Inbox CC to Wiki > - Get around the curse of Reply-to-All. > Collaborating on a non wiki page using a wiki page > - Use the attachment feature to collaborate on presentation files, etc. > Designing Spaces > - Key considerations for creating new spaces. > Developing a Public Blogging Strategy > Distributed Document Review > Gardening > and > Wiki gardening tips > Index Pages > - create starting points for navigation around topics of interest. > Lightning Editing > - how to co-edit a document with a collaborator > Securing buy-in > - getting others to shift perspectives on wikis > Sparking participation at events > Using the workspace as a document repository > Doing a demo Create tagging structures - Develop a core list of tags for your wiki Wiki Structure - Create a page which outlines important elements of the wiki Stop creating Word documents - The first rule of integrating wikis effectively See also Bonnes Pratiques for a chart of best practices and French translations.

But most important for me is the large volume of very interesting news that will not become "news." This is the kind of material that is more interesting than random pages but which lacks an appealing hook to place it on the front page of a magazine or even a news website. Often these items are timeless; they don't make the front page because they could be run at any time. But they are more valuable than odd curiosities. Because of the voting, tagging, bookmarking process enough people find the item worthwhile that they rise to notice.

I have encountered no other process in the world that is better at surfacing "news that stays news" and "news that will be news" better than these collaborative filtering sites.

Some of them provide a ranking of most popularly bookmark pages of the moment. I use this ranking function without bothering with the tagging part of sites.

Stack Overflow has rapidly become the best place for programmers to get answers to technical questions

there's a way to get the same kind of site

a knowledge exchange, running the same software as Stack Overflow