Administrator supporting marketers - I am the person they go to when content isn't appearing on the site :)
June 30, 2015

Administrator supporting marketers - I am the person they go to when content isn't appearing on the site :)

Kirsten McGlone | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Software Version

2011 SP1

Modules Used

  • Experience Manager (Site Edit)

Overall Satisfaction with SDL Tridion

SDL Tridion is being used across the majority of our organization for our marketing websites. We implemented it as a multi-site platform, making it easier to have localization and mass publishing/inheritance options.
  • 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.
  • Has been a good tool for our marketing content editors to work in parallel with each other
  • Has made it easy to spin out microsites
Tridion is much better for multi-site installations, though Sitecore is a bit easier for content editors to know content types are being used based on visual icon indicators. We've had content editors pick the wrong templates by accident, but Sitecore's visual indicator typically mitigates that. Sitecore API is MUCH easier to use, too. It is the one primary way to work with content, and the documentation is much more consistent. I've found multiple ways to to communicate with the Broker and CM database, but found it hard to get a consistent approach for working with the API (plus, it didn't work with our upgraded servers, so I was forced to look into alternatives).
I think it is really well suited for users who have multiple sites that need to inherit from a parent site, and want easy mass publishing options with the opportunity to also localize/personalize content to a lower level site.

Tridion Feature Ratings

WYSIWYG editor
Code quality / cleanliness
Admin section
Page templates
Publishing workflow
Form generator
Not Rated
Content taxonomy
SEO support
Bulk management
Availability / breadth of extensions
Community / comment management
Internationalization / multi-language
Role-based user permissions