digraph VS exhibitor

My own purpose in using it is to be able to get back to any link that I've read or have potentially wanted to read at a later point in time.

You scan see screenshots here: https://github.com/emwalker/digraph.

I have the same habit and wrote a web app to catalog the links I come across:

https://digraph.app/

This was kind of the idea behind a side project I started a few years ago:

https://digraph.app/

https://blog.digraph.app/2020-06-13-democratization-of-searc...

I definitely think crowd-sourcing and a well-conceived reputation management system that can influence results are good next areas for exploration.

> I think building search vertical that are hand-curated would be very interesting to see.

That was my inspiration behind a side project I made a few years ago — a decentralized, hand curated "search engine" [0]. Never got beyond the side project stage. But I see promise in this in the future. Eventually we'll figure out that human and moderated curation is better than the best machine learning.

[0] https://github.com/emwalker/digraph

TL;DR: A React front-end component workshop, a simple version of Storybook.

So around 5 months ago, I needed a tool to preview front-end (React) components whilst I create them for a personal project of mine. There were two options: Storybook or Ladle.

Storybook is the tool everybody knows. I've used it before quite a lot. It's very big, full-fat, supports loads of use-cases, etc.

Ladle comes out of Uber. It's very small, lean, and doesn't support that much. After trying it out for a while, it just gives me a feeling like it's a 20% project to learn some new tech.

So I realised that I wanted something kind of in the middle. Something that's a bit more customizable than Ladle, but something much simpler and less intrusive than Storybook.

This led me to create Exhibitor (https://github.com/samhuk/exhibitor) (https://demo.exhibitor.dev).

I worked on it on-and-off for a couple months, and it ended up being something that I'm quite proud of. It's not perfect, and supports only a fraction of what Storybook does, however for a tool made by 1 engineer vs the 20+ for Storybook, I'm quite happy about it!

Exhibitor, a snappy & delightful React component workshop, is GA. My aim is for Exhibitor to be an extremely fast, easy to use, and delightful tool for creating front-end component libraries.

It's been around 2 months since my last mention and quite a tonne has changed.

Wiki: https://github.com/samhuk/exhibitor/wiki

Looks interesting. Coincidentally, I've just completed the bulk of work on a distributed Websocket network system to synchronize certain bits of state between multiple clients for my own kind of Storybook tool [0]. How interesting!

This kind of tool is exactly what I would have needed, instead of the approach I've taken which is a bit kludgy, grass-roots, novice-like, etc.

Good work :)

[0] https://github.com/samhuk/exhibitor/pull/22

I was a bit deflated when my submission about https://github.com/samhuk/exhibitor fell through the HN floor-boards.

Think Storybook but simpler, faster, better Typescript support, and uses esbuild by default.

...Is the aim. I'm the sole lead dev working on it at the moment up against the ~10-20 strong team who built most of Storybook, so it's a long road ahead, but it's growing into something I'm quite proud of and happy about.