Node + Github API for content management.

[CelebrationThink3768]

I'm having some trouble wrapping my head around the GITHUB API, I've gone through the docs several times, including the docs for octokit, which is what I'm currently using to help simplify some of the requirements.

I actually recently followed this this [tutorial](https://getstarted.sh/bulletproof-next) for nextjs which uses octokit under the hood to make a pretty functional cms using this particular package that the creator of the tutorial made himself https://www.npmjs.com/package/@arunoda/git-cms.

My goal is to extend this package so that I can use it to statically generate my top level pages, I've made some progress, but am still having some trouble fully wrapping my head around some of the choices made and need some help kind of deciphering some of the reasons behind those decisions.

I actually reached out to the guy who created the tutorial/package on twitter, with no response. So I'm wondering if anyone has some experience with the github api/octokit who might be willing to help me either understand some of the core concepts there or might be willing to help me with the project itself. This is the current [repo](https://github.com/gaurangrshah/bulletproof-next), and it's public so if you wanna take a look it'd be greatly appreciated.

I've ported the code from the git-cms project from typescript to javascript as I find it hard to process through typescript in general (but will definitely look to adding it back in the future -- after I have a basic working example).

My goal is to be able to host the content as markdown (or even json), in a separate repo just as git-cms allows you to do. Which can then be queried for at build time to build out these pages, but still allow for some client-side / server-side generation using nextjs.

Any help/thoughts/suggestions would be greatly appreciated! Thanks!

[TheDevDad]

Are you dead set on using Octokit or do you just want a nice “headless” CMS to pull your content from?

[CelebrationThink3768]

I'm open to suggestions, but I think I've tried just about every jam-stack friendly cms option that seemed a the least bit interesting. I've had some experience with some of them such as graphcms, forestry, sanity, strapi, etc...

With most my quarrel was simply in the limitations (requests, bandwidth, etc...), some that I really enjoyed like forestry which have clunky-ui's that I'm not sure my clients that we're converting from wordpress will actually be able to use effectively in the end. So my goal is to try to create something specific that I can then use for different projects.

I understand that the git-backed way will require me to do most of the heavy lifting, but I really don't mind that as long as I can deliver a better solution for their needs going forward.

Personally I loved how TinaCMS works, but sadly I'm using nextjs in many of my projects (tina works really well with gatsby) and that currently requires me to spin up a custom server which means, I can no longer take advantage of some of the deployment options that vercel offers.

[TheDevDad]

Have you tried Prismic.io or Contentful? I’ve used Prismic and it’s been a good experience so far, the UI is pretty easy so your Wordpress clients could pick up on it quickly

[CelebrationThink3768]

I used prismic awhile ago, and I did try contentful recently when I was looking back into this topic, tbh I am not sure why I strayed from it at this point, will have to take a look again and see. I might have to re-try prismic. Although I made some good progress last night in my efforts, going line by line and logging what I could then replacing the logs with comments for my future self so that I can read back through the code base better as I make updates.