ghostToHugo VS pagefind

Couple that with the regular "your theme is no longer supported" messages, I got fed up of burning time to keep up with their updates, which offered no benefits to me. I quit and moved to Hugo (using a ghost-to-hugo migration tool [1]).

[0] https://ryansouthgate.com/goodbye-ghost-hello-hugo/#im-no-lo...

[1] https://github.com/jbarone/ghostToHugo

For me I found a useful CLI tool to do the conversion for me. https://github.com/jbarone/ghostToHugo I made some tweaks to that above version https://github.com/robrotheram/ghostToHugo

ghostToHugo is the converter, it didn't work for me, I found that if you had a bookmark with a nil description it would cause the tool to fail. I've fixed the bug and committed it back to the repo so it works if you have the same problem as I did. You can check out my commit here.

Pagefind is a static search library that aims to perform well on small or large sites, while using as little bandwidth as possible, and you don't have to host any infrastructure.

In theory, if we ran lower level code, we would be using less resources. That's more than a theory. Go to this video where I demonstrate Pagefind, written in Rust and compiled to Wasm as target, as a static app that ingests and indexes HTML documents and runs super efficient search queries, all client-side.

✅ Pagefind static search library integration

I use Astro SSG and Cloudflare Pages. I use https://github.com/cloudcannon/pagefind for search on my Astro setup. You can test the search functionality here https://tinyrocket.pages.dev/.

From its repo: "Pagefind runs after any static site generator and automatically indexes the built static files. Pagefind then outputs a static search bundle to your website, and exposes a JavaScript search API that can be used anywhere on your site."

Pagefind is cool!

An option there is https://pagefind.app/ — not as fast as a persistent server but solves some of the deployment and bandwidth issues.