3 ms·
What is the motivation? Adding search functionality to sites that have no dynamic backend? How would I build an index? Are tools included for that, or is it ju
by lignuist 14y ago
What is the motivation? Adding search functionality to sites that have no dynamic backend?
How would I build an index? Are tools included for that, or is it just reading an index? Is it building the index each time the page is loaded, or in advance, or is both possible?
While the slides explain, what a search engine is, they seem not really to explain, how I can use this particular search engine, which is a pitty, since this looks like a cool project.
This is the project page, but I cannot find such information there as well:
https://github.com/reyesr/fullproof https://github.com/reyesr/fullproof
- lighthazard 14y agoI am working on a project which is, essentially, fully client-side. We decided to use the browser's built in search function to handle searching until we could implement a better search method. We also have tagging in place because that's how we handle our most basic of searching. Having a fulltext search library that was would allow us to search through our data more effectively. Now to test this on the mobile browser.
- stdbrouw 14y agoI would think that even for a static site you'd at least want to generate the index as part of the build process, not (like fullproof) do that on the client as well. Of course, for client-side apps that never touch a server and store user content in Local Storage or some-such, that's not really an option. I'd wager 99% of us don't have that problem, though. Still, kudos to the author, looks well thought-out.