Progress Sitefinity

- Reduced infrastructure management - Improve automation - Increase efficiency

I particularly like the usability of the CMS from both an administrator and an editor's point of view. The power given to an administrator to control how a website is built via the CMS itself, rather than entirely relying on developers, has always been a big positive. Extensibility is also good, especially in view of much of the code being available on GitHub which helps with understanding how things fit together.

It was easy to negotiate our specific needs with the vendor, especially around licensing issues that confused us during the initial deployment. It's also been fairly easy to stand up, and has performed consistently well since it's been in production.

- Requires time and effort - Steep learning curve - Can not handle large amount of traffic

The support process can be frustrating, and hit or miss. It can take weeks of back and forth to get to the bottom of an issue and often not in a very constructive way. Certain elements of extensibility could be better in terms of documentation and available integration points. Documentation in general is not kept up to date in places and often does not go into enough detail.

There was some confusion about how the concurrent back-end editor licenses worked that almost got us in trouble, but we were able to work with the sales team to get that resolved. There has been a few bugs that my dev team has found, and I was hoping for a bit more stability. I'm also a bit concerned about the roadmap for future features. Is it true that old version has an end of life date, but new version isn't available yet?