Stack Overflow for Teams vs. RWS Tridion Sites

In my opinion, Stack Overflow for Teams is well suited for an organization that is on a hiring spree for the engineering teams. The reason for it is because instead of catering to doubts of new joinees individually, they can be asked to refer to the Stack Overflow and hence will save a lot of time for both new joiners as well as the existing employees.

Incentivized

SDL Tridion works well for organizations with a large website with a lot of content to continuously create and manage. The use of page templates and component presentations makes creating new pages fairly straightforward. It can be a little cumbersome when it comes to trying to "break from the norm" and build web pages that are outside of the template-driven format; however, there are ways around this to create pages that break away from the normal page-template format of the website. In this regard, SDL Tridion can be pretty flexible, allowing us to create a lot of custom functionality to keep up with constantly changing web trends.

• Sharing technical solutions to problems we encounter in our internal development environment.
• Sharing best practices we find in external resources.
• Discussions on design patterns and conventions we can use in our projects.

Incentivized

• 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

• I don't like it when I'm searching in the company's private account and the search automatically goes to the public SO search, I would prefer to be asked if I want to search in the public SO.

Incentivized

• If you are hoping to orbit the planet with a CMS, Tridion is built to leave the solar system. It is a very very powerful solution built for very serious enterprise businesses in hope of robust capabilities, which could be good or bad.
• Supporting business users is a hefty lift and requires significant training and regular retraining, and support.
• It's a niche solution that originally came out of Europe and was largely unknown in America. But today it's growing in popularity across the United States.
• Finding capable support, and developers specializing in Tridion capabilities isn't always easy. And 8 years ago it was nearly impossible, involving finding European developer support shops in order to get the assistance needed. This is changing though and American developer firms are becoming more widely available.

Incentivized

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's easier to use Stack Overflow for Teams Q&A to maintain our knowledge base over time, over the Confluence wikis that we also maintain. You don't need to bother about folders, filenames, templates - just ask a question and answer it or get it answered. It feels less formal, so developers feel more free to add content.

Incentivized

Interwoven teamsites, Documentum, Adobe - teamsites and documentum are old and limited. Adobe rocks but I like where I am and Tridion does a lot of the same things. No need to reinvent the wheel or move to a lateral product.

• Positive impact by saving us time to solve our needs.
• Negative impact by allowing for overly competitive people to game the system.
• Soliciting upvote from you coworkers simply for points.

Incentivized

• 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