Consolidating Netlify CMS
Netlify CMS is a powerful, pluggable content management system for static site generators that removes the need for building your own backend. My favorite way to utilize it is combined with Netlify and GatsbyJS; that both provide even easier ways to get up and running.
With the power of a centralized
config.yml file, you are able to pass through information to the CMS that prescribe repo integration, permission settings, collections, fields, and more.
With the config above, we're able to populate the Netlify CMS with a CRUD interface for creating blog posts that can talk to our GitHub repo.
Unfortunately, this all starts crumbling alongside complex projects with a myriad of collection and fields. A recent project had reached almost 1,500 lines of config; which presented a few issues:
- Was incredibly hard to visually grep.
- Since YAML is indention-dependent, complex collections were fragile to modify and add fields.
- Extending from or creating reusable partials is not an option.
- Extending the Netlify CMS with additional plugins/custom widgets is unclear and/or impossible.
When it was time to add yet another collection-type, I decided to take a step back and look into alternative options. Enter Manual Initialization. This allows us to write our CMS init with standard JS that gives us more flexibility on "how" we write our configuration. Let's take a look at how we might accomplish the same thing using manual initialization.
What are we able to solve with the above?
- Consolidated init file that can continue to grow as project complexity does.
- Utilize packages like eslint and prettier to maintain code-quality.
- Create reusable partials by using native JS object functionality.
- Open platform to modify core behavior and add in custom widgets/plugins.
Why would Netlify CMS have
config.yml then if manual initialization gives us so much power? Because not all projects will be complex. Not all projects will have needs that extend from what a single-file config can provide. The single-file config also removes a barrier to entry for users that may not want to add this complexity to their project. What it means for me, is having a platform that provides me with either option.