But performance issues aside, there’s still a problem with complex static site generators: you’re dependent on the SSG to compile your site. If the SSG company decides to do a big backwards breaking change to better support the needs of a lucrative client, you’re stuck having to either rework your entire blog or never get any more updates.
If your goal is to truly own your content, the way to go is to write your own basic build step
, and then ship the compiled HTML to a tool like Netlify
. While you are still depending on an outside service to serve your content, at least you have full control over how your content is built. And, if your hosting provider decides to do something you don’t like, it is much easier to switch static site hosting providers than it is to switch out the build system for your entire site.
For example, check out masteringjs.io’s GitHub Repo
. No established static site generator, just ES6 template literal layouts and a `for` loop that compiles markdown. Granted it is far from “perfect”, but perfect is the enemy of good. And this setup has been good enough to achieve our goal of not spending any more than 1 hour per quarter on the build system.