Learn about the best (and worst!) features Netlify CMS has to offer, as determined by TrustRadius' reviewers.
Based on 4 ratings of Netlify CMS's features
Top Performing Features
9+14%
WYSIWYG editor
What-You-See-Is-What-You-Get editing tool allows users to build pages without writing code.
Category average: 7.9
9+8%
Code quality / cleanliness
Code generated by WYSIWYG editor is clean and validates according to W3C standards.
Category average: 8.3
9+10%
Publishing workflow
The software allows users to set up a custom workflow for updating the website, including approval processes.
Category average: 8.2
Areas for Improvement
3-62%
Page templates
The CMS has standard webpage templates or types of web pages (e.g. homepage, article page, interior page, blog page, etc.); users can also build custom templates.
Category average: 7.9
2-71%
Availability / breadth of extensions
There is a broad library of extensions, plug-ins, modules or add-ons that allow users to easily customize their websites without building custom code.
Category average: 6.9
1-85%
Library of website themes
A library of website frameworks or themes is available as a starting point for building a website.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
UI Developer in Information Technology at Thoughtworks (10,001+ employees employees)
Use Cases and Deployment Scope
When there is a very low-cost solution needed for managing content on the website and the users are not really tech savvy, but they have a need for a WYSIWYG editor with some basic features. Many other solutions might exist for this problem but you might also need a customized schema for the content being stored and more control over infrastructure and access to data, and also a free and open-source implementation.
Pros
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
Cons
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
Return on Investment
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
Alternatives Considered
Jekyll, Strapi, Contentful, Ghost, Forestry CMS and WordPress