graphql-api VS RSS-Link-Database

I created an open source library that turns structured text data (YAML) in a Git repository on the fly into a GraphQL API with CRUD queries / mutations.

All that is needed in the repository is a plain text GraphQL schema file that defines what the data structures look like. The Git repository itself can be located on GitHub, GitLab, or in the local filesystem.

https://github.com/commitspark/graphql-api

I'm working on https://commitspark.com , a headless CMS where all data is stored in a GitHub repository with branching/merging workflow support for content.

Reading/writing content from/to GitHub happens through an Open Source API library I released. For the content data schema, I simply require a plaintext GraphQL type file inside the repository. The schema then automatically determines the API structure as well as the editor-friendly UI that I can generate on the Commitspark website when you log in via GitHub.

Even though Commitspark is already publicly available, it is still 100% a side-project that doesn't earn me any money (yet).

Hi HN,

I built Commitspark, a Git-based headless CMS that runs on top of GitHub.

The primary purpose is to enable non-technical content editors to take advantage of Git workflows based on branches, pull requests and merges, without them having to learn Git.

Behind the scenes, everything content-related is driven by GraphQL and an open source library I released ( https://github.com/commitspark/graphql-api ), and for all the workflow features like PRs, commenting and diffs, I built a CMS-centric view onto GitHub using the GitHub API.

For content editors, this should feel the same as working in any other headless CMS, except now with support for much more powerful workflows. For developers, this means all the strengths of Git and GitHub can now also be applied to content (pipelines, tags, commit hashes for caching, branches for migrations, etc.).

There are many other things I am also excited about here that I'm happy to discuss, so please leave your questions below.

Have you considered that content might come from Git? If so, how would content branches fit into this?

(Disclosure: I'm building a library that turns a Git repository into a branch-enabled GraphQL content management API. See https://github.com/contentlab-sh/contentlab )

On the other hand it is not 1995. Time has moved on. I wrote a Simple RSS feed, that also serves as search engine for bookmarks.

I am able to run it in attick on raspberry pi. We do not have to rely so heavily on google.

https://github.com/rumca-js/Django-link-archive

It is true that it does not serve me as google, or kagi replacement. It is a very nice addition though.

With a little bit off determination I do not have to be so dependent on google.

Here is also a dump of known domains. Some are personal.

https://github.com/rumca-js/Internet-Places-Database

...and my bookmarks

https://github.com/rumca-js/RSS-Link-Database

Some more years, and google can go to hell.

[4] https://github.com/rumca-js/Django-link-archive

These are exported then to github repositories:

[5] https://github.com/rumca-js/RSS-Link-Database - bookmarks

[6] https://github.com/rumca-js/RSS-Link-Database-2023 - 2023 year news headlines

[7] https://github.com/rumca-js/Internet-Places-Database - all known to me domains, and RSS feeds

My own repositories:

- bookmarked entries https://github.com/rumca-js/RSS-Link-Database

- mostly domains https://github.com/rumca-js/Internet-Places-Database

- all 'news' from 2023 https://github.com/rumca-js/RSS-Link-Database-2023

I am using my own Django program to capture and manage links https://github.com/rumca-js/Django-link-archive.

That is why I wrote [1] for myself. It stores links in database, which I can query. Everything is later on exported, like in [2] and [3]. I can browse history, I can find useful data. I do not say it has replaced google for me. It is a nice addition that helped me gather data I encounter on the Internet.

It is a link database, at first glance resembles Reddit clone, but my focus is on creating link database, not on providing social media experience cancer.

Links:

[1] https://github.com/rumca-js/Django-link-archive

[2] https://github.com/rumca-js/RSS-Link-Database

[3] https://github.com/rumca-js/RSS-Link-Database-2023

- https://github.com/rumca-js/RSS-Link-Database-2022 - all captured links in 2022

- I think newsboat reader does not provide advanced search mechanism

There is also a repo in which I store entries which I find interesting, useful: https://github.com/rumca-js/RSS-Link-Database