Shhh…it’s because we haven’t announced it yet…

Keep in mind, Deki Wiki is a wiki interface to a distributed application platform. What is meant by this is that users of Deki Wiki get the immediate value of a wiki: improved collaboration around text, file, and email, but also are able to connect and mashup systems, databases, external services, and Web 2.0 applications by creating composite applications and data mashups. This is achieved while still allowing a site administrator, presumably someone within enterprise IT, to provide governance of the data and services that users can access. The end result is a user-centric interface to data that is dynamically generated from traditional data silos.

Stay tuned, in the next couple weeks we’ll have some news about that site you mentioned and some other new announcements from MindTouch.

Also, I tried several times to “infect” my team and coworkers with wikies, but they proved to be surprisingly resistant. :-( I guess that there are two classes of people around: the majority resistant to wikies, and the minority fanatical about them.

My dream is to find a wiki (that is easy to set-up, ala wxwikiserver) that supports scientific/math notation (TeX). I know that Mediawiki (as implemented at Wikipedia) can do that, but all business of having to install database and to learn PHP (and have a dedicated machine hogged by them) did not work for me.

Mainly because people are afraid of wiki markup and also because we hardly think in another way than MS-Word flat organisation of documents.

We have tested for about one year now http://www.clearwiki.com , which is a hosted one. We loved it, it has many of these features we want to have as intranet editor : WYSIWYG editor, tagging system, map of the wiki, export as HTML features and much more. Unfortunately, we didn’t find a way to convert it into internal intranet.

If some of you have ideas on how to make a wiki successfull, it would be of great help to me.

Best Regards
Anne

We also use wikis extensively internally for information sharing related to operations, projects and client management. We have tried several intranet tools over the years, but the wikis are fast to update and are getting a much higher adoption rate.

It is a little frustrating to learn yet another markup language, but once there are page templates set up it gets a lot easier.

I am considering using that service to set up a page for the final preparations for my <a href=”http://www.pushing50.net”<Just Over 50 and Not Dead Yet panel at South by Southwest Interactive on March 8.

It would give me a chance to get my feet wet (and reduce the e-mail back and forth).

I would be happy to meet those of you who make it to Austin.

Have a good day.

Serge
‘The French Guy from New Jersey’

Every company that I work for that doesn’t have a wiki will have one when I’m done. It’s such a useful concept for companies and departments. It enables content creation without the need for a pre-defined structure (or approval to publish, it’s really democratizing as well).

I prefer wiki implementations with the least number of features, as to Keep It Simple. The lower the threshold to participate, the more successful your wiki will become.

My startup is developing a wiki-based product and when I explain it to friends I have been surprised how few people actually know what a wiki is. These are generally non-technical people, but nonetheless frequent users of computers and the web.

I am convinced that wiki use is on the rise, but it does not yet seem to have reached the mainstream.