Netlify CMS vs. Progress Sitefinity

Netlify CMS is well suited when you have very less frequent updates to your content, maybe once a day and very few people need to access your data. You can connect it to Netlify, GitHub, or any platform and have multiple people access it and do as many updates as you wish, but the process is not well-defined and you need to build your own system for that. It is well suited for projects you need to pull off with very low cost, it is essentially free as the software is open source and free to use, and all you need to do is set up your schema correctly and find a deployment pipeline where you can build your static site/API to redeploy whenever the content changes. I personally used a GitHub Login -> Netlify CMS -> next app consumer of content -> GitHub pipelines to run next SSG -> GitHub Pages to deploy the built static site. It might not be appropriate for large teams where users themselves need no-code tools to modify the schema of the content.

Incentivized

Progress Sitefinity remains a little heavyweight for sites that require basic text content, or a limited number of pages. However, its flexibility (including the range of different content types if supports) make it a good choice for any organization requiring advanced content management capabilities at an affordable price.

Incentivized

• Storing content data in customized schema without a database
• Full control over your content and infrastructure where it is deployed and stored
• Very low-cost way for building your own CMS and CDN

Incentivized

• '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.

• Linking between different schema types, i.e. having some relations between content
• Better ways to define content schema, like how TinaCMS would handle using a JSON

Incentivized

• Diagram or illustrate more use cases for server setups, and managing of upgrades.
• I'd like to see the ability to synchronize from one server to multiple others at once.
• Implementation assistance as part of the purchase rather than farming out to 3rd party, although they did answer every question we asked in order to determine our best architecture setup.

Incentivized

Pricing makes this a no brainer. Not the best CMS, but with work arounds and some fumbling around we are able to make it do what we want it to do

Incentivized

Very big fan of this CMS, as it allows scalability, performance, and everything else. The support is great whenever we need it. As a marketer, the digital/marketing side of things is very easy to use and we've seen strong results from an SEO and marketing perspective. I can't speak to the developer/creative side too much, but in talking with these teams, they do recommend the tool as well.

Incentivized

Has been solid for us on availability

A bit sluggish sometimes as the compiler works.

Support can be pretty good, even though, depending on the level of licensing, it can take longer to hear back from their team. They do have a phone option, which works well. Overall, they are knowledgeable, and helpful when needed. At times, support is able to access the system directly and troubleshoot critical items when needed.

N/A - I was not part of the implementation team. We have had this internally for over 5 years. Based on my experience, ensure that you have documentation on the initial implementation and subsequent upgrades. I would also recommend to have all the documentation on how and why the system was implemented the way it was

Incentivized

We really can't compare it to full-fledged CMS software, like WordPress, which has a lot of community and support with widgets, plugins, and whatnot. It's not built for that, but you can compare it to Contentful, Ghost, Strapi, etc., which provide similar functionality to a headless CMS with custom schema options, but even among them, it still lacks a lot of functionality, ease of use, and support. But Netlify CMS pros would be of the opinion that compared to other platforms where most schemas need to use their own tools and frameworks, it's very cost-effective. Something new called TinaCMS has come up to compete with Netlify CMS by covering most of its shortcomings, but it's something new being built by the same team that built Forestry CMS and comes with many modern features, yet currently only supports NextJS SSG.

Incentivized

It is hands down just easier for our customers to use. The interface and the page builder experience is much better than what we have used in the past and has many enterprise features even in the lower price-point

Incentivized

Seems pretty scalable.

• Helped us inject dynamic content into existing site very quickly
• Wasted a lot of time to implement when something complex, such as querying content, was needed

Incentivized

• Sitefinity has reduced the amount of time it takes to edit and publish content, which has enabled us to get information out more quickly.
• Sitefinity allowed us to establish a consistent and modern brand identity and apply it across multiple websites.

Incentivized