Tiki is the Free/Libre/Open Source Web Application with the most built-in features
- FLOSS -> http://en.wikipedia.org/wiki/Free_and_open_source_software
- Web Application -> http://en.wikipedia.org/wiki/Web_application (This includes Wiki, CMS, Groupwares or any application comparable to Tiki)
- most built-in features: Some other FLOSS Web apps may have more features when you count all the extensions. However, the Tiki model is to have all-in-one for better integration, easier upgrades and increase collaboration and productivity of developers.
This means that you can turn every single feature on and it’s going to work. You will have a dizzying number of elements in the menu but everything works. Now, in a core & extension architecture, try installing and activating every single extension and you’ll likely break your system because of conflicts between extensions!
Since when? Perhaps 2005 or 2006? There is no formal way to count features (an option of a feature counts, right?) But in any case, all other major FLOSS Web apps (in recent years) such as WordPress, Joomla!, Plone, Drupal or Typo3 have the small core and thousands of extensions model.
Is having so many features a good thing? Well, certainly if you need a lot of features or you want to have them readily available if/when you need them in the future. It’s also nice to be able to address diverse use cases.
How often are new versions released?: Tiki has a time-based, “Release early, Release often” approach with Long Term Support (LTS) versions, to balance the needs of stability and innovation. Please see: Version Lifecycle
How will I know where to start?: Features are tagged “basic”, “advanced” or “experimental”.
Isn’t this more complex?: Read here about how we are Coping with Complexity
What about in the future?: It is very unlikely that other major projects will change their model, and integrate all the features in the core. This would require a major change of philosophy, and be a politically tricky situation as the core team decides to pick one extension over another. A newer / smaller project could indeed adopt the all-in-one strategy, but given the velocity of Tiki development, it is unlikely to catch up in terms of number of features. Inversely, will Tiki ever change its model? The model is working really well for us and we already found ways to deal with the inherent challenges. There could be minor adjustments such as packaging translations or themes separately (so far not worth the trouble just to save a bit of disk space), but this won’t change the “big picture” . Thus, it is expected that for the forseeable future, Tiki will remain the FLOSS Web Application with the most built-in features.
How about the release schedule?
See: FLOSS Web Application with the fastest release cycle
Who does this?
People just like you: https://tiki.org/article370-Tiki-reaches-500-contributors-with-commit-access
There is also a great deal of Interoperability with other applications and services.
And for features which are beyond the scope of a PHP / MySQL application, please see: WikiSuite (Integrated Web and desktop suite).
What is missing? Please see: Major Features Missing in Tiki
See also: Benefits
- CMS with most features
- Groupware with most features
- Open Source Web Application with the most built-in features
- Free Web Application with the most built-in features
- Free and open-source software Web Application with the most built-in features
- Free and open source software Web Application with the most built-in features
- Free and Open Source Web Application with the most built-in features
- Free and Open-Source Web Application with the most built-in features
- FOSS Web Application with the most built-in features