Sitecore CMS: when platform extensibility is a must
Anonymous | TrustRadius Reviewer
Updated November 26, 2014

Sitecore CMS: when platform extensibility is a must

Score 10 out of 10
Vetted Review
Verified User
Review Source

Software Version

6.4.1

Overall Satisfaction with Sitecore Web Content Management

At Promega, we use Sitecore as the content management system (CMS) for our public website (http://www.promega.com). The content management environment is used by a fairly diverse set of content editors who work together to create, manage, curate, and maintain our website content.

My team (Web Team) supports the content editors by creating new page types and templates, as well as extending the default Sitecore behavior to more appropriately match the needs of the organization.
  • Extensibility
  • Performance
  • User friendliness
  • Developer community is still evolving and growing
  • Learning curve for some operations (content editor or developer) can be steep
  • Reduced time spent on simple web page changes
  • Increased ownership of website areas by the appropriate subject matter experts throughout the business
  • Improved responsiveness to requests for large-scale website changes
We use Sitecore for our public, externally-facing website. I don't see that changing any time soon. It would require a very significant effort to replace Sitecore with another system, since this website has been actively developed for over 4 years.
Sitecore is perfect for an organization that needs the ability to perform a lot of customizations to their website and the data that is exposed there. It allows for "chunking" of data, so that these smaller chunks can be reused across various areas of the site. In the hands of competent .NET and web developers, Sitecore is an amazing platform.

Sitecore is probably too much for a company that just needs a simple website with a few pages. If your pages are not changing frequently and you don't need automated integration to other systems or processes, Sitecore may not be the best fit.

Sitecore Implementation

We implemented Sitecore on an Agile project team, which worked very well. We worked closely with the stakeholders for each feature and all features and user stories were prioritized outside of the development team. Anyone trying to implement a website of this magnitude should definitely attempt to do so in as much an Agile fashion as possible.
  • Implemented in-house
  • Professional services company
We worked with Horizontal Integration.
  • Developer learning curve
  • Time constraints
  • Large website that needed to be implemented

Sitecore Support

Sitecore Support is very knowledgeable and helpful. We have raised a number of issues with them and they rarely fail to come up with an acceptable solution.
ProsCons
Quick Resolution
Good followup
Knowledgeable team
Problems get solved
Kept well informed
No escalation required
Immediate help available
Support understands my problem
Support cares about my success
Quick Initial Response
None
Yes - Yes; it was resolved in a future release of the software.

Using Sitecore

Mostly, it's great for developers and content editors, but due to the flexibility of the system it can also be complicated at times.
ProsCons
Like to use
Relatively simple
Easy to use
Technical support not required
Well integrated
Consistent
Quick to learn
Convenient
Feel confident using
Familiar
None
  • Content editing
  • Development customizations
  • Presentation detail changes
  • Internal search engine usage