Decap CMS vs. Umbraco CMS

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

Umbraco is well suited for websites that are looking to do a wide range of activities that require complex technoligies. An example of this is a company with several different products or services. Umbraco would be overkill for simple sites that are mostly static. It is also difficult to find developers who have Umbraco experience, as it's market share is not all that high

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

• Quick to learn. For most if cases, developer needs to know Razor coding.
• Doesn't require back-end programming.
• Has build in users management (developers, content managers) and members management consoles (users of the site).
• Clear admin tool (especially in version 7)
• Fast.
• Creating code from scratch, so it is easier to create clean code.

• 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

• Migration of data between servers. There are tools that you can pay for that help facilitate this, but like any CMS system, there are still some tricks to getting it to work correctly.
• Running as a Web Project instead of a Web Site. Umbraco does not run compiled code, but instead compiles it on the fly. I find this to cause some performance issues that would otherwise be resolved with a compiled code base.

Incentivized

Umbraco CMS effectively addresses enterprise content management needs. It's quite mature .NET based CMS, standing out as a leader among its competitors. Websites built with Umbraco are blazing fast. Extensive customization capabilities, and user-friendly content publishing interface makes it an ideal choice for businesses looking for a mature CMS solution.

Incentivized

Occasionally, errors will appear in the admin that make it impossible to work without developer support.

Incentivized

Working in the admin panel (adding / reviewing / editing content) is very slow. The public facing site speed is dependent on what the pages are doing and how well the code was written (whether it is optimized for speed).

Incentivized

Support for Umbraco-owned paid plugins is nonexistent.

Incentivized

Online training is often based on older versions of the platform. So, you'll have to fill in the gaps on your own.

Incentivized

Spend the time to wireframe the content structure prior to diving in. This helps speed the process of implementation and it serves as documentation for end users.

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

We previously used WordPress, however this was not easy to use, it was a complicated system and was limited in what we could achieve, there was a big outlay in buying bolts on and ensuring the system was safe. We found we where spammed loads, we tried to make it work however after a year we decided to leave WordPress behind. The company did evaluated Adobe but the dev team decided that Umbraco was the best tool to meet our own needs.

Incentivized

Without significant development, the product does not scale well.

Incentivized

• 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

• CMS is free
• Support form Umbraco HQ is not expensive, can include Courier or other functionality
• For most cases does not need back end developer
• For trained Umbraco developers (Razor coding, using admin tool), developing medium site, takes a few weeks max