Duda vs. Netlify CMS

Duda is great for small to medium sized websites building, where some level of animation is ok and mostly for presenting online information, and its SEO performance is very good then. But for very large or heavily interactive websites it may not be the best choice.

Incentivized

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

• Ongoing Education for agencies and users. Anton has done what he does best and turned Duda into a go-to-source for information, ideas, and practical implementation.
• UX - The ability to create simple yet highly customizable sites.
• Speed - Sites take much less time to build and maintain, allowing agencies to scale and business owners to spend more time on growing their core revenue channels.
• Reliability - From technical reliability, reduced down-time to support, Duda is a reliability option.

• 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

• Ecommerce can use some improvement--but this should be taken care of in 2023
• A more robust app marketplace
• More custom widgets

• 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

Upon using the builder for the first time, I found Duda to be extremely intuitive and easy to figure out, but also has a high skill-ceiling. After 5 years of building in the drag-and-drop builder, I continue to teach myself new tricks and methods to continually improve my process and design capabilities within the platform. I've built dozens of Duda sites and each one is better than the last.

Incentivized

Duda lets me customize the entire page. With Squarespace, many of the templates were limiting on editing the header and footer. Also in the past, I couldn't change the page title and page header to be different in Squarespace. This was not good for SEO. Wix is good but also a little bulky and glitchy.

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

• Duda has allowed our team to function quicker
• Duda has allowed us to have more clients
• Our clients are happier with their sites now

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