Yes! git-bug is the closest prior art, I reference it in the README's Prior Art section.
Three key differences:
1. Plain Git primitives — git-bug uses CRDTs with JSON operation logs. git-native-issue uses commits as events, Git trailers for metadata (same format as Signed-off-by), and merge commits for conflict resolution. No custom serialization.
2. Standalone format spec — git-bug's "format" is whatever its Go code produces. git-native-issue ships ISSUE-FORMAT.md, a standalone specification that any tool in any language can implement. The spec is the deliverable, not the CLI.
3. Simplicity — CRDTs are powerful but overkill here. Git already solves distributed conflict resolution with three-way merge. Why rebuild that in userspace?
git-bug validated that storing issues in Git refs works. I built on that lesson with a simpler data model and a spec-first approach.
I remember reading The Twelve-Factor App [1] from the Heroku folks back in the day, and was blown away by how well they understood the problem. Not only that but they had great taste.
I moved things to Render a while back, and then to my own Hetzner server (I built kind of an open source Vercel clone for that reason [2]).
I'm not quite sure any of these platforms are going to be relevant 5 years from now when you can summon your own DevOps AI agent. At the very least it's going to be incredibly difficult to justify the premium on top of AWS.
Appreciated. That's pretty much what I was going for.
The only thing I think is missing is a proper full text search which I'll add later on this week using lunr.js [1]. I just didn't have the time to get it done for this release.
It's pretty much as advertised: a really simple documentation template built with 11ty [1] and Tailwind.
I've been releasing a few projects in the past year: Basecoat [2], Pages CMS [3], and lately /dev/push [4]. Each one of them needed its own documentation.
Sure, I could have used stuff like Mintlify or Docusaurus. But I really wanted something fast, modern, simple, and good-looking. And if possible: no React.
Since it's using Basecoat, you get a shadcn/ui compatible design system, so pretty easy to style.
I'll be rolling it out to all my projects, but maybe some of you find it useful.