Sitefinity's usage from small project to large scale factory approach
June 12, 2020

Sitefinity's usage from small project to large scale factory approach

Jochem Bökkers | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Progress Sitefinity

As part of a modernization, our current CMS is being replaced with Sitefinity as an organizational product.
Serving both as the main CMS for several regions and HQ - as well as a departmental application CMS for standalone portals and platforms in a multi-tenant, multi-cloud approach. The main reason for standardizing on Sitefinity is its flexibility and its omni-channel capabilities, allowing us to write once and use across platforms, channels and APIs throughout the organization and externally.
  • 'Low-code structured content' (dynamic content types) is one of Sitefinity's most powerful features that allows you to structure content according to business needs, while at the same time dampening editorial freedom to ensure accessibility, meta enhancement, SEO and API consumption can be achieved.
  • Sitefinity's content provider model allows us to flexibly (by means of admin interface) easily aggregate or separate content sharing within a multi-site instance.
  • This proofs particularly powerful in emerging situations where there suddenly is a demand for content sharing across countries or regions.
  • Adaptability at its core.
  • While there's never a perfect fit for everything, it allows for easy code customization and extension being a .NET application at heart. Giving it a corporate edge over other custom solutions, whether it is on the development side or deployment side (on premise, IaaS or Azure DevOps Paas). And it has enabled us to put the system to use in its core feature - which is to manage content, where on other occasions we were able to take full advantage of its features such as A/B testing and personalization.
  • Roadmap visibility could be better.
  • Being a publicly traded company, long term roadmaps will have commercial impacts, however it would be great to see future visions expressed more clearly.
  • Video improvements.
  • While accessibility and concepts like 'low-bandwidth' are key these days, rich experiences are equally important. When it comes to 'videos', Sitefinity is trailing behind the current use cases where low/high-bandwidth versions, captions and subtitles are a requirement.
  • Sitefinity's Microsoft Machine translation integration will allow us to cut production of localized content down from days to hours.
  • Sitefinity's architecture and adherance to industry standards of development have allowed us to re-use components, functionality across the various instances.
  • Sitefinity's responsive and scalable implementation allows us to build a design system and future digital economy of shared elements reducing the need of constant front-end implementations from scratch for every new initiative, site or application launched.
My main experience has been with Drupal and SharePoint besides Sitefinity.

And while many people swear by Drupal because of its open-source nature, often the hidden TCO, its lack of intuitive usage and limited functional implementation (CMS for Web Publishing) has made us choose Sitefinity.
It's one of the easiest to use, easiest to customize CMS system available on the Microsoft technology stack.

Whenever there's an application need for user management, role-based permissions, workflows and page-content, it is simply not done to start custom development from scratch.

For complex 'factory-approaches' its architectural implementation shines brightest and allows for hybrid deployments, full Azure DevOps integration and ensures security and governance are not sacrificed.

Progress Sitefinity Feature Ratings

WYSIWYG editor
Code quality / cleanliness
Admin section
Page templates
Library of website themes
Mobile optimization / responsive design
Publishing workflow
Form generator
Content taxonomy
SEO support
Bulk management
Availability / breadth of extensions
Community / comment management
Internationalization / multi-language
Role-based user permissions

Progress Sitefinity Support

Mission critical support allows us to have 24/7 support on the software, but while 24/7 also means multiple agents across various continent, Progress provides us with a unifying 'customer success manager' ensuring that all tickets and escalations are handled and communicated in a uniform matter.
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
Yes - We prefer mission critical support as we utilize Sitefinity cross-organizational where up-time is considered mission critical.
Yes - Yes, in general bugs are treated beyond satisfaction with quick resolution.
In a few cases, fixes are delayed until a patch release (which is normal behavior) in which case we were offered work arounds.
During a recent switch of functionality in output caching (with a version upgrade) we were seeing infrastructural problems arise. Progress supported us beyond their scope and assisted us in the investigation to determine a custom piece of code that was affected due to the external dependency library upgrade. The previous implementation, from our side, was actually never correctly done - however the symptoms only appeared after this upgrade.