ManageWP vs. Netlify CMS

If you are a WordPress development shop, or host a number of WordPress websites, this is for you. Even if you only have one website but are looking for an easy way to make updates, schedule backups and keep track of the maintenance of your site, this would be a great tool. The cost is reasonable and it saves time, while adding peace of mind with "Safe" updates.

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

• Managed Wordpress Updates - ManageWP allows you to update all out-of-date themes, plugins and core files on all your websites with the click of a button.
• Automated Backups - ManageWP allows users to setup an automated schedule of backups (including free monthly backups).
• Maintenance & Development Mode - ManageWP allows users to place a specific site into Maintenance or Development Mode, allowing them to block users from accessing the site with a click of a button.

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

• The reports could be prettier, more templates in order to avoid having to customize for each client so heavily.
• It would be nice to see if recommended plugin updates are actually production and not beta versions.

Incentivized

• 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

It's very straightforward for basic use, but less you dig in more for advanced use. Seems like it would be approachable to the average person.

Incentivized

Prior to ManageWP, we utilized InfiniteWP, a free (with paid extensions), self-hosted alternative. We found the interface to be unwieldy, and the paid extension pricing to be a bit confusing. The headache of maintaining the software and server infrastructure to run the platform, overshadowed the cost savings for us.

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

• High positive ROI as it has saved us doing manual updates on multiple website
• It has helped us scale our careplan offerings to service more clients
• Helps with automation and admin time

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