It's meant to be implemented by a developer, but it doesn't take much skill, and can be hosted for free on a number of services. I was a champion of Netlify well before I became an employee, so I still shamelessly plug them as the way to host static.
Regarding what we're committing, it's definitely human friendly, mostly markdown, or else json/yaml/toml/etc, nothing crazy. It's a completely legitimate use, same kind of data that GitHub's own Pages product uses.
I wonder though, if a developer needs to find/provide hosting, then why not use a local db (or even a local git-repo) instead of github? With current data storage solutions, installing could be as simple as one line of code.
The CMS is specifically made to work with Git, because so many developers are already using it for the rest of their site development. That said, it's not impossible to write a non-git backend, but it's heavily bent that way at the moment.
Regarding what we're committing, it's definitely human friendly, mostly markdown, or else json/yaml/toml/etc, nothing crazy. It's a completely legitimate use, same kind of data that GitHub's own Pages product uses.