elasticlunr.js VS faustjs

When i did my static site search function some time ago, I used Elasticlunr. I was able to pregenerate the index file as a big json file that is loaded at the client.

http://elasticlunr.com/

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

Very nice! Seems to perform very well. I'm curious, have you compared Fuse with other search engines? Like flex search or elasticlunr? Why did you choose fuse ?

Check out elasticlunr

There's also Elasticlunr which is based off of lunr.js and is what mdBook uses

http://elasticlunr.com/

Does this relate to http://elasticlunr.com/? mdBook uses the latter, and I was wondering how I can parse/read its indexes from Python so I can provide my own search from them.

Same as above, for most blogs something like http://elasticlunr.com/ can get the job done really well.

3. HotSwap on the fly themes

Doctave comes with offline search built in. We use the elasticlunr-rs crate to generate a search index that is compatible with the elasticlunr.js library. You can see it in action by going to our docs (built with the CLI, naturally) and hitting the letter s on your keyboard to focus on the search bar. The searching happens entirely client-side.

Yeah, in hindsight, we would have used Next/Vercel. So we're tactically moving over to that. There are many new frameworks, like Astro, that are really exciting, but it seems like Next is the best choice if you have a data-heavy app that has a dynamic mix of SSR and static pages. For Wordpress in particular, I'd recommend that you check out Faust.js. It's build with Next and I'm amazed by how well it works with Wordpress without much effort: https://faustjs.org/

https://faustjs.org is a great headless Wordpress solution for Nextjs. I've tried several CMS solutions and ultimately WordPress is invariably the friendliest option from a client perspective.

I'm working through a large project where we're leveraging WordPress and Next.js. Check out Faust.js (https://faustjs.org/) which works as a layer to handle a lot of the query/template/routing stuff that maybe isn't super-intuitive when trying to hook WordPress up headlessly...

- FaustJS (built for headless WP on NextJS w/ full site editing capabilities)

Faust.js is the front-end JavaScript framework built on top of Next.js, created to make developing headless WordPress sites easier. The idea of this new version is to make a parity between the WordPress world that a developer might be used to but replicate it as much as possible in the JavaScript front-end world.

This is where it started. Then there is also Faustjs started by WPEngine. https://faustjs.org/

https://faustjs.org/ built specifically for headless WP