SDL Tridion Sites Review: "Administrator supporting marketers - I am the person they go to when content isn't appearing on the site :)"
- 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)
- The user management and permissions can be confusing, especially since you have to add users directly in the database before adding permissions (I believe this was resolved with version 2013)
- The publishing queue can easily get clogged, and it can be difficult to fully restart and get pending items published out
- If a user has an item checked out and publishes it, it will act like it went through successfully, but actually hasn't. It can be misleading and difficult to troubleshoot why changes haven't appeared on the site.
- Blueprinting and reuse of content
- The front end or delivery application can be .net, java or php.
- Personalization of content.
- Image repository/manipulation within the system.
- Experience manager can be improved on.
- Content porting between publications is not possible.
- Tridion gives you full capability to build content pages through the use of their component sections that can be used as a building block approach.
- The publishing pipelines were very effective when dealing with various environments of dev, qa, staging and production.
- I found the internal newsletter management to be very helpful to customer and engagement outreach right within the CMS platform.
- I thought the upgrade process was a little involved going from one major version to another.
- Additional Cookbooks could also improve implementation and development of the later versions of the CMS
Tridion is used globally by our content owners as they build their country websites, in their own language, using the same branding.
- Multilingual functionality by effective blueprinting really does it's job.
- Re-usability of templates and building blocks across different projects works really well.
- The interface makes it easier for developers to navigate around the tool.
- Workflow needs to be addressed and worked on. We've tried implementing it back in R5 and it kept hanging the pages in between steps.
- SiteEdit appear to be a problem in our setup. I would expect the functionality to be "plug and play" but we end up custom coding parts of it to make it work.
- It would really be nice if they offer free "plug and play" add ons to the tool, i.e. polling widgets, commenting widgets, social networking, etc, without having to do too much coding to integrate.
- Enable for easy portability and re-usability of content with other CMS.
- The blueprint concept is great, helps facilitate the sharing of code and content.
- Separation of content and presentation makes it easy to share content across multiple properties, even publish to mobile and gaming platforms a possibility.
- Workflow and the workflow Visio tool is very powerful. It can be used for various customizations.
- Content Porter, is your friend and at times can be a pain, but mostly it's your friend
- Moving between environments, dev, qa, uat and production is simplified.
- Oh that Broker db.
- Installations, do you have a month. I'm joking, but yes it is quite complicated to install SDL Tridion and its many parts.
- Personalization with Smart Target, requires a PHD in software science. The integration between the products is just not there.
- SiteEdit 2012 and the new Tridion UI, is a bit outdated. The UI can use a little help from a user experience perspective. It is not tablet friendly.
- Tridion does a great job at supporting multiple websites in the enterprise
- The ability to have multiple environments with a single instance of the CMS.
- The content porter is really bad, we have basically stopped using it.
- The data connector is neat but very slow, we have created a solr core to replace it.
- Site Edit sucks!
- This product addresses the Why, What, Who and Now, and Where of Content Management to allow simplicity.
- SDL Tridion has a simple functional design that allows users to stay organized and streamlined.
- At first glance, Tridion can be overwhelming with the introduction of the SDL Tridion functional design.
- The content versioning of this product is fairly average, and meets basic requirements.
- It allows for creating a variety of page layouts
- It supports SEO management
- It has good back-end to front-end integration
- It would be great to have an ability to reuse images in the components of different proportions
- It would be good to have an internal tool that helps to find if a component is linked to another component or is used on some pages
- Sometimes it takes too long to propogate changes even the small ones
- File organization clear and concise
- Ability to tweak html code in wysiwyg windows
- You don't have to have any programming experience to use
- A lot of steps to link components with pages
- Ability to delete PDFs from server very cumbersome, unlike regular pages
- Having difficulty manipulating images and special text such as bulleted lists next to each other -- they don't play well together!
- Our organization was able to customize the implementation of SDL Tridion so that it would fit our unique needs for a CMS; it is flexible in this regard, and we are adding new elements all the time to fit changing requirements and marketing goals.
- The user interface for SDL Tridion is very clean, and easy to use. This makes it easier for users with less web experience to navigate and use the CMS tool.
- SDL Tridion integrates well with our back-end organizational systems and applications, making the customer front-end experience seamless, and our back-end processing as smooth as possible.
- The search tool is really helpful when you have a lot of content to manage. We use the search feature all the time to find things we need if we don't immediately know where it is stored; it is a major time-saver.
- 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.
- Multi-language website content
- Well architected API that exposes all CMS functionality via Web Services
- Solid CMS and Content Delivery architecture that scales well for highly visited sites
- Solid security and roles setup to easily configure access to folders and features in the CMS
- Customizable GUI
- Great active community with dedicated Tridion site on StackExchange
- More training courses and information about integrating new products, such as Fredhopper and SmartTarget, with existing Tridion implementations
While Tridion does give business more functionality to edit some parts of the website that were previously not editable, I feel that Tridion is completely out-dated as a CMS and there are lots of better alternatives.
- Tridion has a blueprint (hierarchy) where you can inherit items from a higher structured website or publication
- Tridion has version control built-in to the application so you don't need to use a separate SVN
- You can write custom plugins or extensions such as one to minify all JS and CSS files automatically
- Doesn't work well in all browsers. Tridion is a Microsoft product so they really push IE; however, now-a-days it SHOULD work in all browsers. Even though they say to use IE, Chrome actually functions the best with Tridion.
- It uses Dreamweaver Syntax. Dreamweaver syntax is completely out-dated and SDL really needs to come up with a better way of looping through content by using it's own structure or using .NET syntax to loop through items - Dreamweaver syntax is not the way to go
- Component Templates and Page Templates. Tridion uses Component Templates and Dreamweaver templates to display content and store the content that is to be displayed. These 2 items could easily be converted into 1 group of items, but SDL chose to keep them separate therefore increasing the complexity of Tridion
- Steep learning curve. Tridion has a very steep learning curve and it will take some time to train people on it. We had to hire 4 Tridion experts (at probably around $1000 / day) to get everyone trained on Tridion and then build the structure for Tridion
- Reusability. It uses a lot of modules that can be used in more than one location.
- Deployment of source code. A sites dll's, JS and CSS can all be managed within SDL Tridion. This gives the power to an Admin to deploy new versions of the site without as much need for a systems engineer to assist.
- Extremely flexible. A feature can be made in many ways. So if one doesn't work, try another.
- User interface is very confusing unless you take classes on how to use it. Not very intuitive and hard to figure out how to do things on your own.
- Due to the high flexibility there is a high risk of having sites without uniformity. every feature can be created in different ways. This can make troubleshooting extremely difficult for a developer to fix a bug or add a feature that will not break existing features. It can also cause duplicated code or features because a developer needs to create a feature and creates a new one that already existed elsewhere in the site simply because he/she could not find it or was unaware of it.
- Content authors can be very dangerous. SDL Tridion has the potential to give Content Authors great power over their sites. Mistakes can be made that are difficult to recover from and take many hours to recover from.
Scale of site(s) you will need?
Complexity of site(s) you will need?
Number of Content Authors, from how many locations?
- Content used as "modules". This allows for one module to be created but then used across the site. Allows for more accurate content site wide.
- Content is responsive and can be viewed on any device.
- Allows for more SEO driven content through tagging of modules and pages. Easy to update content makes web crawlers see that content is being updated more often which is great for SEO.
- Learning the content management tool may take some time.
- Although having many options for types of modules, this is sometimes confusing to learn where certain modules can and cannot be used.
- Publishing can sometimes be cumbersome.
- Provides an extensible framework for building a web infrastructure
- Allows reuse of content across multiple websites
- Documentation is very weak. SDL makes it impossible to learn without spending a fortune on training. Additional resources are extremely limited.
- Publishing can be very slow.
- Very few Tridion developers are available who aren't consulting or working for SDL.
- Easy to build components
- Data from external systems can be migrated into Tridion SDL with proper tools
- HTML does not convert well into Tridion and causes many problems
- Tough to migrate data into Tridion SDL
- Very few Tridion experts on this planet and are very costly.
SDL Tridion Sites Scorecard Summary
Feature Scorecard Summary
About SDL Tridion Sites
SDLTridion is a content management system that targets global businesses attempting to enrich their customers’ experience through the entire customer journey. It is used by businesses of medium to large size for reaching out to a diverse customer base. The software helps predict what customers want and engage with them across multiple languages, cultures, channels and devices. It features a WYSIWYG editor and simplified interface to automate content creation and editing, and touts mobile-accessibility for visitors without duplicating assets and pages. It possesses analytic features to help integrate visitor behavior into targeted outreach efforts. Compliance technology aids adherence to regulatory and accessibility standards. Monitoring and quality management ensure comprehensive archiving and audit trails are present. It presents a decoupled architecture, supporting Java and .NET environments or hybrids.
As with most content management systems, pricing can be quite complicated and thus will vary a great deal depending on implementation, feature breadth, and how many users will need access. It is available as a cloud-based or as a local-hosted option. Technical training and support are both offered for an additional cost, should these be desired.
SDL Tridion Sites Technical Details