-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git Powered CMS #15
Comments
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! |
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 |
Correct, data is stored in KV. |
Correct, that's great. Looking forward for the initial version. |
Full SaaS application running on Cloudflare is great. But are there any plans to build a CMS that commits to git to keep the content in the repo only and build with the CI/CD on Cloudflare?
Also if the website content is stored in the KV and a static JAMSTACK site is built, direct way to access KV from the API in the build phase, and CMS can direct save in KV would be great.
The text was updated successfully, but these errors were encountered: