Page actions

In the Tiki Community, we use Tiki's features to manage our processes and to solve our challenges. This is one of the reasons we've arrived at a phenomenal, tightly integrated and robust set of features. It's a central point of the Tiki model.

Some people could think or say that we are suffering from NIH syndrome. But that is misinformed as Tiki reuses a lot of code (Zend Framework, jQuery, etc.), so this reduces our workload. We have offloaded a lot of work to these components and avoided new work by reusing what they offer. In fact, more than half the code shipped in Tiki comes from an external library and we don't have to maintain. We just upstream fixes when we have some. Please see: Source Lines of Code.

Examples

Since July 2003, the Tiki community started eating its own DogFood, used only Tiki to manage the official site (not just a demo site). Tiki 1.7 ran through 4 release candidates and this has produced a great improvement in stability and usability.

During 2003-2004, tiki-forums.php started being used more & more and eventually, the Tiki forums at SourceForge were closed down.

In April 2005, the Tiki community started using dev.tikiwiki.org to manage all trackers (bugs, feature requests, etc).

In May 2005, mobile.tikiwiki.org was started to speed up development & integration of the excellent HAWHAW toolkit to make Tiki useable on cell phones, PDAs, Lynx text browsers and via VoiceXML.

In fall 2006, an internal system to get help was implemented for the documentation site: doc.tikiwiki.org. Our documentation development is full-on wikified and as good as any volunteer based open source project out there.

Latest Page Changes

Why Register?

Register at tiki.org and you'll be able to use the account at any *.tiki.org site, thanks to the InterTiki feature. A valid email address is required to receive site notifications and occasional newsletters. You can opt out of these items at any time.