Published: 25 July 2018
When choosing the right CMS for your business it’s important that you take into consideration all of your objectives and what your roadmap looks like. It’s also a decision all of your key stakeholders should be included in as it moulds the future for the brand.
With that in mind it’s essential to compare the key elements of different platforms, so we’ve taken some time to do a direct feature comparison of some of the world’s leading CMS. This week we’re looking at Sitecore vs OpenText.
With over 10 years of Sitecore experience and having worked at OpenText for a period too, I felt that it would be a good idea for me to explore these platform heavyweights and help you weigh up their similarities and differences.
First, let’s take a look at the platforms at face value
OpenText as a company is very successful in the digital asset management and content management; not to be confused with CMS systems; content management in this instance is a lot wider and is about email, CMSes, SharePoint, document management and more. For the purposes of this article, we’ll be looking at one of the OpenText CMS systems - TeamSite.
TeamSite is a Java-based CMS, which has good integration points, especially when looking at other OpenText products, such as OpenText Media Manager.
Sitecore is a .Net based platform that takes a much more object-based approach than TeamSite which is more geared towards page-based. Sitecore also boasts itself as a customer experience platform designed to put all of your marketing efforts under one roof with the ‘suite offering.’
OpenText’s TeamSite is a very complex product and requires an add-on, such as OpenDeploy to publish the content to a live server. There is also a distinct lack of documentation available and some features are not documented at all.
Sitecore gives you the complete package all in one instance, with a very easy-to-use interface the platform caters to the needs of everyone, from developer to content editor. In recent years, Sitecore’s documentation has gone from okay to simply amazing, with the community stepping in where the documentation team stops.
With OpenText, you have to use TeamSite for the core CMS functions, in a similar way to the Content Management environment within Sitecore’s interface. However, to get content from TeamSite to a public-facing server you would need another product: OpenDeploy, whereas, with Sitecore, the publishing engine is already there.
With OpenText you would also need something to render the request to the browser. For Sitecore you would use a Content Delivery server, which is simply another instance of Sitecore, but with OpenText you would need another product called LiveSite. So, where CM, CD and publishing is all simply in an instance of Sitecore (and can be installed altogether) this is very different in OpenText.
Sitecore comes ready with testing capabilities including analytics, personalisation, marketing automation and more. It’s possible to get the same functionality in TeamSite, but would mean using additional bolt-on products.
OpenText has very good integrations with its other products including Optimost for A/B testing and OpenText Media Manager for DAM integrations. However, both systems are very extensible and can integrate with any other platform, providing they have public APIs.
There have not been any major releases since TeamSite 8.2, in 2016. To me, there is no (public) clarity on the roadmap, making it more of a risk to start new projects.
Sitecore has recently changed their release cadence to have a spring and fall release, meaning they’re constantly looking forward to providing better, more advanced software solutions to help ensure your website is the best-in-business.
Other things to consider
Let’s start with an obvious one: I’d highly recommend reviewing the roadmap before making any decision.
Both systems are enterprise level products, and while Sitecore has a lot built into the system in terms of testing, analytics and the like, those tools are more ‘best of need’ rather than ‘best of breed’ meaning you might still want to purchase additional products and integrate them depending on your use case.
Which product would I recommend?
Definitely Sitecore. Sitecore’s pipeline approach allows users to granularly tell the platform what it needs to do at each stage of the rendering process. It lets you hook anything into it with an API, and the community is a great environment where developers are constantly interacting and sharing ideas, problems and solutions.
The platform also offers lots of free open-source modules that have been built by other developers meaning there’s a lot more creativity and options when it comes to building your website.
Want to find out more about how we could support your website development? Speak to a member of our team on 01233 467800 or via email@example.com