If the home page has a query parameter of q=<SEARCH_TERMS> then the page should redirect to the search page using that query parameter and perform a search.
The search takes a while to retrieve indexes, the search text says what it's doing but lacks any animation. I think I can listen for pagefind-start, pagefind-stop events. If that is true then I can add a spinner to indicate the browser is getting the data requested.
The search would benefit from a facet search (at least by index bundle). Tommy's implemented facets with PageFind before.
The search results need richer context. If the search terms return a bunch of manual pages across repositories you see "NAME ..." repeated. Makes you think it is a duplicate listing when it is not. I'm wondering if I can indicate in the search results which index was used to return the result. That way it would be clear when it was a potential duplicate (multiple occurrences of the word) or distinct pages.
If the home page has a query parameter of
q=<SEARCH_TERMS>then the page should redirect to the search page using that query parameter and perform a search.The search takes a while to retrieve indexes, the search text says what it's doing but lacks any animation. I think I can listen for pagefind-start, pagefind-stop events. If that is true then I can add a spinner to indicate the browser is getting the data requested.
The search would benefit from a facet search (at least by index bundle). Tommy's implemented facets with PageFind before.
The search results need richer context. If the search terms return a bunch of manual pages across repositories you see "NAME ..." repeated. Makes you think it is a duplicate listing when it is not. I'm wondering if I can indicate in the search results which index was used to return the result. That way it would be clear when it was a potential duplicate (multiple occurrences of the word) or distinct pages.