exhibitor VS epub2tts

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.

I wrote https://github.com/aedocw/epub2tts and the quality is pretty phenomenal if you use XTTS for the voice generation. It's really excellent, but requires the book not have DRM.

Depending on what you are looking for from an audio book, there are options. If you expect essentially a professionally made radio production of the book (multiple voice actors, effects, etc) then a real audio book is hard to beat.

On the other hand if you just want to listen to the book being read, check out https://github.com/aedocw/epub2tts ... It does not sound as good as a pro human, but it's not far off in my opinion. I've used that to listen to 30+ books that I owned the digital version of.

Recently I wanted an audiobook version of a book I was going to read, but it didn't exist. I put this together using Coqui-TTS and the voice sounds really good. It's not as good as Eleven Labs, but it's far better than anything else I had previously heard.

https://github.com/aedocw/epub2tts

If anyone knows of better TTS synthesizers that I could use please let me know!

I'm not blind but I wrote an EPUB to Text-To-Speech reader using Coqui (a really good AI TTS project). There are books I wanted to listen to while doing other things, and I couldn't find audio-book versions of them, so this worked out perfectly. It could be that I did not do enough searching, but I was surprised I didn't see anything out there that already worked this way.

https://github.com/aedocw/epub2tts

I wrote the script in python and put it up on github here: https://github.com/aedocw/epub2tts