Joomla is a CMS with tons of extensions.
Tiki is a platform that happens to have a CMS component. But lots of other ones as well.
Key advantage of Tiki for me: the ability to have user/group permissions is one thing but having object-based permissions and the new perspectives thing for creating workspaces is unbelievably useful when dealing with various communities. (e.g. I have been running extranets for banks on it, ran one of my startups with it with lots of partners having limited views on stuff, and socius manages all of their backend workflow on it as well).
The code is simple enough to understand so that you do not end up with piles of ubercomplex objects piling upon each other ala dotnet (read: when you are stuck, you can step through with a debugger without interceptors, proxies and other $XYZ wrappers and aspects-generated byte-code gremlins).
i may be biased. I am part of the marketing team for it (well, an unpaid volunteer promoting open source that is), so take my enthusism with a grain of salt.
If you need help, just tell. We also have a very helpful IRC channel on freenode: #tikiwiki - Also check "Tiki Essentials" and "Tiki For Smarties" web sites (both done with Tiki obviously - by our Ricks99 incredible and tireless writer). There is also docs.tiki.org but you are better off starting with essentials or for smarties.
And the crowd is as cheerful as here: people who love pushing things forward. That's essential for me.
<end of rant/>
|
