On Friday I viewed a demo of
the latest version of the Deki Wiki product from
MindTouch, with Co- Founders Steve Bjorn and Aaron Fulkerson. The latest upcoming release, called "Deki Wiki Hayes", is described as a wiki and platform for developing collaborative web applications. The company says it's similar to CMS web frameworks like Drupal, Mambo, Joomla and DotNetNuke, but a wiki in nature.
In a sense MindTouch is transforming the Wiki, from the Web’s best collaborative authoring tool into an open source service platform with a Wiki heart. Their Deki Wiki Hayes release is perhaps the most extendable Wiki tool available today. The product is OS and programming language agnostic. Deki Wiki Hayes allows developers, administrators and users to create or integrate Wiki capability into web apps.
We talked a great deal about terms like the semantic-web, aggregation, and interconnectivity. Wiki Hayes allows all users to benefit from nearly any Web service with Wiki style and simplicity. From a developmental standpoint Wiki Hayes adds both flexibility and standardization to new or existing services. Here is the short list for key features that aid users and developers:
Mindtouch has current deployments at Microsoft, BP, Stanford University and many others around the world. Transforming the simplicity and popularity of the Deki Wiki into a value added service platform aids developers by providing a more powerful, flexible and enjoyable downstream product for their clients.

Example of a nice Deki Wiki build
The big advantage to local administrators is the simplicity and flexibility of Wiki collaboration. Deki Wika Hayes also simplifies permissions and web extensions for users of any technical skill level. The Bi-Directional API function allows cross platform mixing and blending of services and enhanced control for administrators. In essence, anything the Deki Wiki can do is easily done by the site admin. Aggregating content, graphing, extension authentication and dozens of other features are resident out-of-the-box features for the Hayes release.

Editor and navigation of the Wiki hierarchy
Deki Wiki Hayes allows end users to participate on an unparalleled scale. Users can create, customize and utilize Deki Wikis and services like Flickr or YouTube without even learning Wiki markup. The WYSIWYG editor is the heart of the UI and has the power of a light word processor. Deki Hayes doesn‚Äôt use non-standard markup language, so users can simple copy and paste from office docs. or web pages. The editor also toggles between plain text and XHTML for experienced users. In short, any user can enhance existing services, create rich pages, find and organize content, communicate and aggregate content with ‚Äúsimpler than Wiki‚Ä? ease.

Sandbox creation I started for a project - note Digg widget
Mindtouch has done a fantastic job of creating a platform that simplifies and/or integrates the development, administration and end use of a wide range of Web entities. Wikis are one of the most widely used and flexible conduits for collaboration we have, and Deki Wiki tools add even more connectivity between the people from end to end. The Hayes release and the tools I tested are not ‚Äúdrop dead‚Ä? simple as far as discoverability goes, but extensive documentation is available and the learning curve is not overly steep. Ease of use for programmers, HTML users and Wiki aficionados should be a snap, and even I was able to turn one of my projects into a Deki Wiki easily. Hayes will be released today or Wednesday, but you can get a head start at OpenGarden.
Comments
Subscribe to comments for this post OR Subscribe to comments for all Read/WriteWeb posts
Hey Phil - thanks for the excellent writeup! :-)
Posted by: Amanda Wheatcroft | July 24, 2007 11:32 PMDeki Wiki Hayes...Whoa...Calling all naming gurus, here's a hot prospect for you ;-)
Posted by: PXLated | July 25, 2007 7:16 AM@PXlated,
LOL. Well, Deki is Japanes for "smart". Does that make you appreciate the name anymore?
Posted by: AaronF | July 25, 2007 7:32 AMI had the almost same idea back in 2006 and even did a basic prototype based on PHP + MySQL. Just wanted to make an easy to maintain - actually very much easy to maintain CMS in the flavor of a Wiki, that is, a CMS more like a traditional one but has the administration and development in the wiki fashion.
Without distinct differences between the back end and the front end, they play together in the same role.
This could really boost the productivity, I believe.
Posted by: ichsie | July 25, 2007 10:23 PMPhil,
They are spot on with biggest problem in WIKI's. Finding managing and associating the content created in a WIKI. Currently running a WIKI is somewhat of a mystery for the average user, and most are a little hesitant of doing it. Seems like the right direction, good luck guys!
Posted by: Jim Kern | July 26, 2007 4:30 AMThanks for the comments guys. Hayes is a powerful tool to be applied to Wiki's. I agree with Jim in that Wiki's one weakenss has been in connecting to a wider base of people/business.
As Aaron and I talked about, Wiki markup has a strange learning curve - where the text markup is rather easy and then more advanced things like graphics require a much more in depth knowledge.
Aaron spelled Japanese wrong - so you know he is on the cutting edge of technology! Super Geeks and programmers spell worse than I do. :)
Posted by: Phil Butler | July 26, 2007 7:46 AMLOL. Thnaks Pilh.
Posted by: AaronF | August 3, 2007 12:36 PM