Tiki vs Confluence
When comparing Tiki vs Confluence, the Slant community recommends Confluence for most people. In the question“What are the best multi-user wikis?” Confluence is ranked 3rd while Tiki is ranked 18th. The most important reason people chose Confluence is:
Confluence offers a highly intuitive and user friendly experience without sacrificing the advanced feature set of a typical wiki.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro It's a full featured CMS
Tiki supports user-account management, permission management, allows managing menus, customizing layout, etc.
Pro Bitnami stack
Bitnami stack available for Cloud or install as Virtual machine.
Pro Lots of built-in features
Tiki includes tracker, chat, newsletter, forum and much, much more functionality out of the box.
Pro Free and open source
Tiki is licensed under LGPL.
Pro LDAP support
Pro Upgrades are smooth
Because all features of Tiki are supported by core developers, compared to a model where the wiki relies on third-party extensions that may or may not get upgraded along with the core codebase, the upgrades are a lot easier.
Pro Easy to use
Confluence offers a highly intuitive and user friendly experience without sacrificing the advanced feature set of a typical wiki.
Pro Integrates well with other services
Confluence integrates well with other Atlassian offerings like Jira, a bug tracking system.
Pro Keyboard shortcuts support
There are a lot of shortcuts to speed up the interactions with the editor, viewscreen, workbox, etc.
Pro Hierarchical page tree
Most wikis don't have a page hierarchy, but Confluence has one, and this is very helpful for a lot of people.
Pro Great plugin ecosystem
Confluence offers a huge selection of paid and free plugins across all kinds of different categories that extend the functionality of the core software.
Pro Document and inline commenting offers low-commitment opportunities to contribute
Often someone that is not an expert/owner of a process is hesitant to edit documentation of someone that is. The ability to merely comment on the existing material helps elicit improvements without requiring as much boldness.
Pro LDAP integration
Confluence provides built-in connectors for:
- Microsoft Active Directory
- Apache Directory Server (ApacheDS)
- Apple Open Directory
- Fedora Directory Server
- Novell eDirectory
- OpenDS
- OpenLDAP
- OpenLDAP Using Posix Schema
- Posix Schema for LDAP
- Sun Directory Server Enterprise Edition (DSEE)
- A generic LDAP directory server
Cons
Con Can feel bloated
Since there's so much stuff in Tiki already built-in, it can be overwhelming if all you need is a simple wiki.
Con Pretty slow
The hosted version feels slow and can be annoying to use regularly.
Con Search is utterly terrible
It requires having to put in almost exactly what's needed to get a result on the front page. Defeats the purpose of the problem it's supposedly solving.
Con Many unresolved bugs
Atlassian is notorious for not resolving bugs for months or even years in Confluence.
Con Costs money
Although inexpensive, starting at $10/mo for 10 users, many other solutions are free.
Con WSIWYG editor is broken
Markup is not saved and complicated to use.
Not suitable for dev teams.
Con Redesigns are rolled out without thorough testing
There were two major redesigns for Confluence (cloud version) in the last couple of years, and both of them were released in a very immature state, causing a lot of trouble for existing clients.
Con No full Unicode support (no real emoji support)
Confluence has a limited number of "emoticons" but doesn't support emojis as defined in Unicode.