RWS Tridion Sites vs. XWiki

Love the product and I really like how we use it for public sites. The only negative aspect is that it is just hard to find Tridion devs that understand the tool, grasp .net, react, and understand the blueprint, etc.

XWiki is very well suited for a very wide range of web collaboration and web development.

• Makes it easy to spin up a new site quickly
• Allows for numerous users to work on the same site without conflicting with each other's changes
• Allows you to unpublish changes or revert to old versions if you make a mistake
• Allows you to time publishing actions (for example, you can set it to happen overnight)

Incentivized

• XWiki makes it easy to manage semi-structured information, which is at the heart of every knowledge nexus of organizations. It makes it easy to manage in a single system both structured data (such as memberships, projects), and unstructured data.
• XWiki offers a very rich API for creating enterprise applications quickly that are easy to maintain and evolve collaboratively.
• XWiki templating and skinning system is extremely flexible and powerful.

• Tridion is complicated in enough ways that it makes it difficult to train new users. Therefore, we have to limit the number of people with access to the system since we have not yet implemented Workflow.
• When something goes wrong (items fail to publish, or there is unexpected behavior with components), there is little explanation provided that would point us in the right direction to troubleshoot. As a result, content Authors and Editors have to frequently ask for IT assistance.

• While the basic pieces are available for turning XWiki into an advanced semantic system, some features could be made available more prominently to the user for easing the use of faceted and typed links, paving the way for a new era of collaborative knowledge sharing.

I am giving this a semi-high rating because we have already got Tridion up and running and we are still in the process of moving the sites over to Tridion. It is unlikely we will be moving things to a new CMS AGAIN in the near future as the cost to get Tridion was high.

The editor user interface is very user friendly and in-site editing makes simple updates fast and easy. The extensibility of Tridion is a big plus and the ability to add our own options into the default Tridion interface helps us integrate with external systems. Finally, the user permissions and security system helps us deploy it within our large organization.

It is a nuclear missile compared to the other handguns and knives on the market today. But it also requires nuclear technicians and expertise that a handgun doesn't require. Do you need to decimate your competition and you have the investment capabilities necessary to put a nuclear missile into the sky? Then definitely do it. Especially if you need a very good multi-lingual blueprint provider like Tridion.

Incentivized

XWiki key differentiators in my opinion:

• Fast app development framework with very rich API
• Open-source strategy, opening the way to collaborative innovation

• SDL is a very complex system. Creating custom components by external vendors turned out to be expensive.
• The learning curve is very slow, so training takes a lot of time and cost.
• The revamped corporate site looks clean, modern, and is mobile-friendly.

Incentivized

• XWiki has a positive impact on the OW2 communication and collaborations strategies. It saves time when developing applications.