@mojitane Thanks! This is a good question, and an increasingly popular pattern. Both git-based (CMS makes changes to content in your git repo) or API-based (CMS gives you a UI and content into your build via an API) work well with JAMstack sites & @Netlify.
See: https://headlesscms.org/
My tweets and posts live here on my own domain these days.
You can explore them here and follow me on Mastodon instead of Twitter where I'm not currently active.