We actually have various CMSs for content like blog posts and human readable text.
We use the solution in the article for things like the current delivery estimate, which changes twice a year and is a Python timedelta object (example, but more complex than that) or adding new tags to our support ticket system (not user facing). For those, we don’t want or need to spend the overhead of making an editing interface.
As for integrating another CMS, the whole point is that it’s just Python files in the repo, zero effort for developers, very little effort for everyone else, when editing is infrequent.
I find it interesting that you mention you are using Django, since my feeling has always been that easy/dumb/quick CMS CRUD interfaces has long been its bread-and-butter, especially the Django Admin.
That said, I don't question the benefits of version controlling data, and the usefulness of GitHub's web interface for quick and dirty commit work.
I am surprised that a quick search doesn't seem to turn up someone already trying to build a NetlifyCMS-like tool for inside the Django Admin. That seems like a natural fit for Django's CRUD philosophies.
We use a Django admin based CMS for part of our product, but most CMS solutions are about things like blog posts or knowledge bases, not for complex data models and changing configuration of an application (like our current shipping estimate). Building editing interfaces in Django is relatively straightforward, but by not doing it we can save hours, maybe a day, and that’s worth it if we’d only use the editing interface for 5 minutes a month, or are testing a new thing that we might throw away in a week.
We use the solution in the article for things like the current delivery estimate, which changes twice a year and is a Python timedelta object (example, but more complex than that) or adding new tags to our support ticket system (not user facing). For those, we don’t want or need to spend the overhead of making an editing interface.
As for integrating another CMS, the whole point is that it’s just Python files in the repo, zero effort for developers, very little effort for everyone else, when editing is infrequent.