> you never own the codebase as it's frameworks and libraries all the way down. Frameworks and libraries aren't really necessary for JAMstack. JAMstack really

> you never own the codebase as it's frameworks and libraries all the way down. Frameworks and libraries aren't really necessary for JAMstack. JAMstack really just means relying on external services for dynamic content. You don't have to use Gatsby or Hugo or whatever. A JAMstack site can be a single HTML page with a script tag (and all mine usually are). I built my own static site generator and I feel so much more ownership over the code. You should try it. Not only is it my code all the way down, but it only runs on my machine. All the generated assets will remain functional and security bug free as long as browsers understand HTML, CSS and JS, even if I never update the code again.