advancingu

Six years after its last edition, our volunteer team brought back Ring on Feier – Festival des Lichts, a cross-border light festival in Germany.

I built the festival website as a real-world proof of concept for Commitspark, an open source Git-based data management tool I’m developing.

The site had to be multilingual (German, Czech, Polish, English), reliable for thousands of visitors, and easy to maintain without expensive hosting or tooling.

In this post, I share lessons learned about using Git for structured content, what worked well (branch workflows, no extra backend), and what still needs work.

Thanks for the pointer. Did you have a specific scenario in mind where this would be helpful?

Tailcall looks like something that could go in front of my library as an orchestration gateway.

However, as my library intentionally does not include any transport mechanism, you'd first have to expose it over HTTP (e.g. https://github.com/commitspark/example-http-express ). In my case, I actually have a couple of Next.js web apps where I load the library directly into the code instead and pass my queries to it without first going through HTTP.

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

Hi Jared, I'm currently working on Commitspark, a headless CMS that uses vanilla GraphQL to define the content model and GitHub for storage and workflows. With this approach I can already today use ChatGPT to not only generate a website content model from a user prompt (e.g. "I want a component-based website with a hero component with title and image, a product component with article number, ...") but also entire web page content from user prompts (e.g. "I have this marketing text here, turn it into content data for a web page using the components in my content model: ...").

The perfect addition here would be to also enable users to generate React components that visualize each content component (I was able to prototype that already with ChatGPT, but I assume what you're doing is more advanced).

Wrap all of this up into a Git repo with Vercel deployment workflow for GitHub and it should be possible to go from prompt to CMS-driven website in a really short time.

So, my question: Would it be possible to get access to V0? Also, feel free to reach out if you see potential for collaboration.

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).

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 )

As I commented in yesterday's thread, this is not the first time Docker is pulling the plug on people with very short advance notice: See https://news.ycombinator.com/item?id=16665130 from 2018

Someone back then even wondered what would happen if such a change happened to Docker Hub https://news.ycombinator.com/item?id=16665340 and here we are today.

It seems to be a habit at Docker to give incredibly short notice before service shutdowns: See the 2018 shutdown of some Docker Cloud services which had a two month notice period ( https://news.ycombinator.com/item?id=16665130 )

I got bit by that back then as a commercial customer and sent a complaint to them. Response was an offer for tickets and travel to a just upcoming Docker Con. Well, thanks but no thanks. I don't need to go to their conference when I'm busy migrating my org to a different service provider.

There is a fantastic English language podcast called "How To F#€k Up An Airport" that goes into great detail about the many failures that let to this debacle. Highly recommended.

http://www.radiospaetkauf.com/ber/

I've set up a public issue tracker on Github for the XPS 13 (2015) developer edition: https://github.com/advancingu/XPS13Linux/issues

It should contain descriptions and some workaround for the most obvious issues that currently exist for running Linux on these machines.