Reliable solution for content management
April 28, 2017
Reliable solution for content management
Score 7 out of 10
Vetted Review
Verified User
Overall Satisfaction with Progress Sitefinity
We use Sitefinity as the content management system for our main website. Only one department has access to the system, but it's viewed by many. We needed a non-open-source CMS system that was cost-effective and that would provide workflow permissions in order to eventually open the system up across departments.
- Responsive layouts
- Easy to use for non-HTML users
- Versioning
- The inline editor adds so much junk HTML. We don't use it at all.
- The workflow approval process is flawed. You have to explicitly turn off the process for the administrators and approvers in order for those users to not have extra steps in having to submit their own changes for approval to themselves. And by allowing those users to skip approval, it turns off the ability to reject changes with comments. We would also like our users to be able to go back in and edit something they sent for approval.
- There should be a way to specify messages for empty data sets. So if there are no events, a message could be set that says "No upcoming events." The same would be good for blogs, lists, etc.
- Upgrades are cumbersome, especially since we've used the database for media/file storage and it's extremely large. We're in the process of moving to the file system for storage, but that is a tedious process as well. Another reason our database is so huge is the revision history. We save as we go so there are LOTS of draft versions out there. Would be nice to have a way to clean out versions that were never published.
I originally started working in Sitefinity with another company because we were a .NET shop. I did not choose Sitefinity for my current company, but they chose me because they needed someone with Sitefinity experience. I would always choose Sitefinity over WordPress because I'm a .NET developer and find it easier to use. I haven't used DotNetNuke in so long, I can't really compare. I think it's easier for custom development, but I'm not sure how it stands up to built-in functionality.