pbr

TW is a single html file, containing just enough really-well-written javascript to implement a self-contained wiki. YES - it's a wiki in one single file. Once the document's loaded into your browser, there's no page-reloading, waiting for the server, or any of that. It's the exact opposite of most websites - it's a CLIENT-side website rather than a server-side website.

To get started, visit http://tiddlywiki.com and download and save that file. Open it via file:// then make some changes and hit "save". Give your browser permission to write files to your own hard drive, and you're good to go.

Soon you'll want to start playing with the myriad of plugins that are available; the de-facto hardware store for these is http://tiddlytools.com

There's outstanding support for TW available as well, just surf over to: http://groups.google.com/group/TiddlyWiki

OK, now go get one; why are you still here? :-)

TWiki rocks. Pure and simple. I use TWiki for both personal and professional projects, and for both internet and intranet based solutions.

It's a mature wiki, with extremely powerful capabilities. It has a reasonable learning curve, a large installed base, and many developers worldwide know the technology.

You might have heard about 'foswiki'. They seem to be making a lot of noise about TWiki, so I'll make some noise about them:

Foswiki is to TWiki as Fedora is to RedHat.

You use Fedora if you want to experiment with the latest bleeding-edge innovations, and you use RedHat if you want a stable product release cycle and proven, vetted components.

Similarly, you can use Foswiki to experiment with the latest plugins and capabilities, and use TWiki for your stable production wiki needs.

There are some within the Foswiki community who seem to be quite upset that, rather than killing TWiki, their fork has only made it stronger.

Well, that's one of the hallmarks of a solid open-source project; it can survive competition and, indeed, thrive in a competitive market.

Features of TWiki that rock:

- separate webs for separate needs

- private, public, protected webs

- powerful search, include, and statistical functions

- variables, templates, skins

- extreme customizability

- solid topic management; great data integrity. All changes to topics are tracked.

- boatloads of documentation

- over a decade of development and refinement

- framework is solid and virtually bug-free

- built using solid, reliable supporting technologies

So by this point I'm guessing you can tell I'm a pretty big proponent of TWiki. Let me tell you some of the ways I've used it:

* I first used TWiki in the late '90s as the 'corporate knowledgebase' for my startup, Open Country. TWiki was used at Open Country for the entire life of the company.

* I've installed, configured, populated, or otherwise supported TWiki installations for dozens of corporate clients over the past decade

* I use TWiki myself, in both public and private installations.

* I tried foswiki, and just didn't find it compelling compared to TWiki; it wasn't much different, and some parts just broke. Those with more patience and tolerance for pain might appreciate it more than I did.

Feel free to contact me if you have any questions or comments about TWiki. I'm happy to help people get past hurdles and otherwise better use and understand the tool.