Git Powered CMS about production-saas HOT 4 CLOSED

This is more of a static-site generator feature and not something a SaaS would offer. With git-based systems, there's no reason to use anything over the network since the entire content & assets are already available and managed locally.

Your second paragraph is definitely possible and is the intended usage. Any existing jamstack site would be making API requests for its content at build-time. The requests made are determined entirely by the user, so they have full control. The usage will match existing headless CMS platforms (eg, Sanity or Contentful) if you're familiar with them

Closing, but please let me know if I misunderstood anything!

from production-saas.

Got your point. I was asking if we could build something that will store data in KV instead of the Sanity... So your CMS would be saving changes in the Workers KV (instead of Sanity) and using KV API to get data at build time

from production-saas.

Correct, data is stored in KV.
But at build-time, you'll make HTTP calls for your data from the deployed demo (or your own hosted version). This is common to all headless CMS integrations.

from production-saas.

Correct, that's great. Looking forward for the initial version.

from production-saas.