When comparing Hugo vs Netlify CMS, the Slant community recommends Hugo for most people. In the question“What is the fastest CMS for web content (news website with some static pages) ?” Hugo is ranked 1st while Netlify CMS is ranked 8th. The most important reason people chose Hugo is:
Code can be viewed [on GitHub](http://github.com/spf13/hugo).
Ranked in these QuestionsQuestion Ranking
Pro Open-source and free
Code can be viewed on GitHub.
Pro Single Binary - Cross Platform
Pro No dependencies
All other SSGs expect you to have a full toolchain setup for their language. Hugo is written in Go and distributed as an executable for unix, linux, windows and mac. Just download and run.
Pro Clean workflow
Create your new site, run the Hugo server, edit. Lather, rinse, repeat. Hugo stays out of the way.
Pro Good documentation
Pro Many themes available
Pro Draft mode
Allows you to see changes in real time.
Pro Very active community
Pro Easy to add new content types, data files, and taxonomies
Pro Experimental support for GitHub's GraphQL API
Experimental support for GitHub's GraphQL API is now available for the GitHub backend. Without mutation
Pro Easy Creating Custom Widgets option
The NetlifyCMS exposes a window.CMS global object that you can use to register custom widgets, previews, and editor plugins. The same object is also the default export if you import Netify CMS as an npm module. The available widget extension methods are:
Pro Built in React.js
Con No tutorial on how to create a theme from scratch
Con a lot of configuration
Example: a few plugins and some code are needed for gatsby-img or markdown to work