Group items tagged

Being a CalDAV reference implementation is not a priority.

we will not be implementing CalDAV scheduling

misperception in the press

Create web-based presentations at Preezo

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.

Corporate Wikis reviewed: Confluence, JotSpot, WetPaint, Socialtext by Troy Angrignon on Mon 10 Jul 2006 06:30 AM PDT  |  Permanent Link  |  Cosmos Wikis are on the rise in corporations. And it's about time. One of the principles of Web 2.0 is that your user community can generate content that is better, faster, and probably easier to read than you can as a vendor. One way to enable them to contribute would be to build a wiki and let them flesh it out. Some good examples are coming up in this article: "Corporate wikis breaking out all over: MSDN Wiki" by Dion Hinchcliffe. (He has another great post as well called "Exploiting the Power of Enterprise Wikis") Quote of the day: "Not leveraging the contributions of a company's most impassioned and enthusiastic customers is starting to be seen as a significand oversight in many business circles." It appears in the article that eBay is using Wikis to better communicate between their users, partners, and suppliers. Now MSDN (Microsoft Developer Network) is using their pages to improve the quality of their developer documentation with the MSDN Wiki. THAT is a great usage. Your users often know your product better than your engineers and product managers because they have to live with it day to day. And guess what? If they tell the truth about some part of your product being broken - that's a GOOD thing.

Atlassian's Confluence is the best of them so far. Pros: the overall design is clean, it has advanced management tools, good security, and simple attachments.Its email function has to pick mail up from a POP box which makes it a little bit less ad-hoc but still functional. And most importantly, it also has great tools for moving pages around. Cons: Text editing, like with most apps these days is a bit dodgy, and pasting in blocks of text from Word is likely to cause problems. The pricing model is reasonable but for some reason (possibly because they're from Australia), they still don't have a directly hosted option so you have to use somebody like Contegix or deploy it on your own box. This seems to be a big and obvious oversight on their part these days. Also, their pricing model doesn't encourage small deployments right off the bat. I think this is the one that we'll use more of internally at the company where I work. Summary: The best of the enterprise wikis today, and one of the best options for scalability.

WetPaint is a newcomer that is doing some interesting stuff and that might be a better bet than JotSpot. Pros: The design is beautiful, the tool is very easy to use, the text editor is one of the best I have seen. Cons: I'm not clear on their entierprise suitability and it's not really their target market. It didn't appear that they had much in the way of administration tools, granular security, or any way to integrate into a back-end authentication system. Summary: I met one of the WetPaint guys at Gnomedex but he didn't seem to know the product very well. Hopefully next time, they'll put somebody more knowledgeable at their booth who knows the product in more detail. I think they're worth watching to see what they do in the next few months.

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.