shortuuid VS stork

Unlike many people here, I don't like to write hundreds of mediocre posts. Instead, I prefer very few posts, that unfortunately are still mediocre.

If you're tired of all the perfection that exists on the internet, where every piece is deeply insightful and changes your life, I'd encourage you to read my articles, which only promise to shorten it:

https://www.stavros.io/

I use shortuuid[0] for that stuff, which also omits the capital letter I, and has some other niceties (I wrote the library). It works really well, and I like how small the IDs are.

[0] https://github.com/skorokithakis/shortuuid

skorokithakis: developer of django-annoying and shortuuid

https://github.com/skorokithakis/shortuuid#usage

If your content is mostly static, you might want to consider pre-building an index and shipping it as a whole. You could look into something like

* https://stork-search.net/ (Rust/WASM)

* tinysearch: https://github.com/tinysearch/tinysearch (Rust/WASM)

* https://lunrjs.com/ (JS, simple, stable)

* http://elasticlunr.com/ - based on the former, slightly more sophisticated tuning options

Mostly write about Elixir. Check out the search function. It is a rust library run as WASM in the browser (all the right keywords for HN hehe).

My blog: https://victorbjorklund.com/blog

Search library used: https://stork-search.net/

(And yes, I know it is totally overkill to have search when you just got a few articles)

Also another alternative is stork https://stork-search.net/

Stork seems perfect: https://stork-search.net/

It doesn’t do live crawling, so might not be quite what you want, but I built Stork Search (https://stork-search.net) to solve full-text search for static sites.

Today, you’d run a binary as part of a site’s build or deploy process, feeding in the input files. It generates a search index which you deploy alongside your site. The project’s JS library will load that index and turn it into a client-side interactive search interface.

I’d be curious to see if this sounds interesting or workable for you - you mentioned that you don’t want to host your own index, but does that change if “hosting the index” feels similar to hosting an image, instead of spinning up a server?

I’d be interested in building a paid addition that will crawl your site & host the index - you’re probably the 2nd person I’ve seen with that suggestion. Please let me know if you’d be interested in being a beta user.

You can index your crawl data with StorkSearch[0] then use its js interface for search.

[0]https://stork-search.net/

stork: a fast web search made for static sites

There seems to be an open issue regarding this hopefully it is resolved soon.