Tiki Wiki comparison chart with others (Tiki Wiki VS ... )
Our point is not to claim Tiki Wiki is the best CMS Wiki or the best system to share and handle online content. We just want you to compare, to check to learn and to decide what system is good for you now... and tomorrow.
When you come to build an internet/intranet project where user and data are involved there are things that will be important for some and critical for others. You will look at the features, you will check if the administration look clear or if it is confusing. You may look at security setting and permissions and at the technology used. We just want to remind you that you have also to think a little ahead. That doesn't mean you have to imagine an unpredictable future when we talk about the Internet and the new technologies coming one after the other. It means you have to think EXTENSIBILITY. You have to prepare ongoing or even exit strategy and be sure that the system or the tool you select don't come up on your way.
Tiki Wiki has an all-in-one concept and approach to features. It work like a suite of applications aimed to manipulate, control and distribute and manage content and access. Tiki Wiki has more built-in features than any other Web applications (there are several bets about this in our community, if you find one, tell me ! ).
All The built-in features are optional and not 3rd party modules/extensions/plugins is required. Tiki Wiki is one of the leading CMS Wiki open-source projects. The community building this web application is open and it is easy to commit improvements or new code. We use a Quality Team to check commits and be sure that every thing has been done the right way. We call it the Wiki Way ! Hard to define it properly, but one thing is sure it is here and it is working ! The code is simple and has community coding in mind. We take the time to comment, explain, compare, discuss with the others.
Marc Laporte one of the Tiki Wiki project admin say it better:
The TikiWiki community eats its own dog food and this is a great thing. 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. We are quite lucky to be a community that is building a community management system. Some people could think or say that we are suffering from NIH syndrome. TikiWiki offers a large number of interactions with services, standards, data format, etc., however, it is designed to be great as an all-in-one standalone application....
At Shocksite it took us times before we select the right tools. We tried dozens of CMS, Wikis and other CRM/ERP or content management system. We decide to run mainly with Tiki Wiki and to participate to the community effort for very good reasons and we would like you to do the same.
Select your tool, by checking carefully and compare some of the most popular system on the market.
We focused on the most popular system to built this chart.
There are dozens of website that exist just to compare the existing CMS or Wikis, feel free to use them too.
Tiki Wiki vs DokuWiki
- DokuWiki is Wiki-Centric, Tiki Wiki is a full-featured CMS.
- DokuWiki uses files for storage whereas, Tiki Wiki uses a database, such as MySQL.
- DokuWiki is focused on being a great Wiki (which it is!), Tiki Wiki is a Content Management System.
- DokuWiki doesn't offer forums, bug tracker, blogs, etc, Tiki Wiki has more features out-of-the-box.
Tiki Wiki vs MediaWiki
- MediaWiki is focused on Wiki projects such as Wikipedia, Tiki Wiki is an out-of-the box Content Management System.
- MediaWiki doesn't offer forums, bug tracker, blogs, etc, Tiki Wiki has more features out-of-the-box.
- MediaWiki (like Joomla) is the small-core-and-add-what-you-need model, Tiki Wiki is all-in-one model.
- The MediaWiki community is well organized but needs several other tools (Bugzilla, vBulletin, etc), Tiki Wiki community is using Tiki Wiki to complete and manage any task of the project.
- MediaWiki sites, will have different modules installed depending the use case, Tiki Wiki has all the features built-in (every Tiki instance of a given version has the same code base), update is smooth.
- In MediaWiki, some of your plugins/extensions may have become abandoned or be incompatible with the new version, when Tiki is upgraded, all the features are supported and the transition is controlled.
- MediaWiki usually handles multiple languages by having separate installs while Tiki Wiki uses the cross lingual wiki engine(external link) for synchronized translations.
- MediaTiki is not very flexible when it comes to design, Tiki Wiki can look like MediaWiki in a minutes (no way you can do the same with MediaWiki).
- MediaWiki don't (and won't) use permission to control content access, Tiki Wiki has a very elaborate permission system.
Tiki Wiki vs Joomla
- Joomla (like MediaWiki) is the small-core-and-add-what-you-need model, Tiki Wiki is all-in-one model.
- Joomla sites, will have different modules installed depending the use case, Tiki Wiki has all the features built-in (every Tiki instance of a given version has the same code base), update is smooth.
- Joomla counts millions of installs and is very popular, Tiki Wiki count ten thousand of installs and over 200 contributors.
- Joomla is web publishing-centric, Tiki Wiki use an http interface and wiki syntax to manage content and datas.
- Joomla uses MediaWiki for its own wiki, Tiki Wiki is the core of the Tiki Wiki project management.
- Joomla uses Mootools while Tiki Wiki uses jQuery.
Tiki Wiki vs Drupal
- Drupal is more of a Content Management Framework, whilst Tiki an out-of-the box Content Management System with all the features built-in.
- Drupal use its own code, Tiki Wiki uses Zend Framework and the Smarty Template engine.
- Drupal is released "when it's ready". Between Drupal 6.0 (Feb 2008) and Drupal 7.0 (Jan 2011) nearly 3 years, Tiki Wiki has a 6-month release schedule, with Long Term Support versions.
- Drupal (like Joomla) is the small-core-and-add-what-you-need model, Tiki Wiki is all-in-one model.
- In Drupal, there can be more than one "contributed module" for the same feature so they have different names. Whereas in Tiki, there is only one and thus, the name is descriptive.
- In Drupal, there is a clear distinction between core and contributed modules developers. In Tiki, everyone works on the core.
- Drupal sites, will have different modules installed depending the use case, Tiki Wiki has all the features built-in (every Tiki instance of a given version has the same code base), update is smooth.
- While Tiki is a very large and popular project (over 200 contributors to main code base), Drupal is several times larger when you count the contributed modules.
- The Wiki engine in Tiki is mature, very powerful and versatile and has features hardly any wikis have such as Wiki Page Staging and Approval and the cross lingual wiki engine(external link), whereas, the Wiki modules(external link) for Drupal are more modest and less actively developed.
Tiki Wiki vs SharePoint
- SharePoint is a Microsoft Products (with all what it means), Tiki Wiki is based on internet community.
- Sharepoint is a commercial product, while Tiki Wiki is a community-managed open source project.
- SharePoint is is designed to run on a Windows Server, Tiki Wiki is a LAMP application whereas.
- SharePoint comes from the Document Management System (DMS) world where things are based on files/desktop-apps, Tiki comes from the web app/wiki world (where everything is browser-based) where as. Editing and sharing is a process on SharePoint, it is natural on Tiki Wiki.
- Sharepoint is upload-and-forget oriented, while Tiki Wiki is write-it-online-and-maintain-it-there oriented.
- SharePoint as a well-know reputation of having hanging times when openig/closing sessions and documents, Tiki Wiki speeds depend on your server or your computer.
Tiki Wiki vs TWiki
- TWiki is written in Perl whereas Tiki is written in PHP.
- Tiki Wiki hosting requirements are lighter.
- TWiki uses files for storage whereas Tiki uses a database, such as MySQL.
- TWiki has less completed languages than Tiki Wiki.
- TWiki is not rtl (Right-to-Left for Arabic or Hebrew), Tiki Wiki is Right-to-Left.
Tiki vs Wordpress
- Wordpress is blog-centric, Tiki Wiki is CMS/Wiki-centric.
- Tiki Wiki has features WordPress doesn't have (and won;t have), a strong wiki engine, for example.
- WordPress (like Joomla and Drupal) is the small-core-and-add-what-you-need model, Tiki Wiki is all-in-one model.
- Wordpress add tons of features via plugins, Tiki Wiki has all the features built-in, update and maintenance is a headache. If you maintain dozens of WordPress sites, they will have different modules installed depending the use case.
- With WordPress, some of your plugins/extensions may become abandoned or be incompatible with the new version, When Tiki Wiki is upgraded, all the features are supported and the upgrade is smooth.
- WordPress counts millions of installs and is very popular, Tiki Wiki count ten thousand of installs and over 200 contributors.
- Because of use of PHP in templates, WordPress themes actually come with added functionality. Thus, if you change themes, you can lose some functionality. In Tiki Wiki, switching themes never makes you lose functionality and only affects the presentation (colors, layout).
Links of Interest