Explore alternatives to current search implementation

[ghost]

I'm not sure which one of you guys was responsible for configuring algolia instance but you clearly didn't test it through via v7, first of all you are not using browse method which means pagination and correct data via filters can't be guaranteed.
Second: You have set paginationLimitedTo to 3500, take a look at pro thin for example, it contains 3671 icons, algolia returns correct number of pages 4, but we only can see first 20 pages, according to the requests you can view up to 180 icons per page aka 20 pages, so 180 * 20 = 3600, but guess how many can we view? only 3500

https://www.algolia.com/doc/rest-api/search/#tag/Indices/operation/setSettings pay attention to the note about paginationLimitedTo

Third: over all none of the indexing strategy was configured correctly from what I can observe, i don't want to go too deep into that but whoever was working on this page (https://fontawesome.com/search?p=2&f=classic&s=thin&o=r) might be a little bit slow/not a paying attention type of a person.

even the lack of proper support for the page number from direct visit i.e. https://fontawesome.com/search?p=2&f=classic&s=thin&o=r says it all, but its not the most problematic part obviously (consider switching to /browse?).

Maybe you should completely get rid of it and switch back to normal datasheets and regular searches/your own internal ones? or maybe at least fix it (the index) so we can view all the icons in needed categories, i doubt we need "sorting" on simple pagination page on your website, but now imagine the moment you hit 20k icons per a category, what then? ask algolia increase their internal limits?

	
integer <= 20000
Default: 1000

Maximum number of search results that can be obtained through pagination.

Higher pagination limits might slow down your search. For pagination limits above 1,000, the sorting of results beyond the 1,000th hit can't be guaranteed.

message: 'you can only fetch the 3500 hits for this query. You can extend the number of hits returned via the paginationLimitedTo index parameter or use the browse method. You can read our FAQ for more details about browsing: https://www.algolia.com/doc/guides/sending-and-managing-data/manage-your-indices/how-to/export-an-algolia-index/#exporting-the-index-using-an-api-client',

[ghost]

#20604
#17957

additional to that
just try going on search, picking thin, classic, go through pages with network tab open, until you hit the 19th or 20th page, and check the response.

i assume @ej2 can responsible for algolia integration fixes now, but so far there's no changes from the #20604 status update times

https://github.com/FortAwesome/Font-Awesome/issues?q=is%3Aissue%20state%3Aopen%20algolia
https://github.com/FortAwesome/Font-Awesome/issues?q=is%3Aissue%20state%3Aclosed%20algolia

the issue is massive actually because even if we perform search single index on the given index

 {
  data: '{}',
  headers: {
    accept: 'application/json',
    'content-type': 'text/plain',
    'x-algolia-api-key': 'c79b2e61519372a99fa5890db070064c',
    'x-algolia-application-id': 'M19DXW5X0Q'
  },
  method: 'POST',
  url: 'https://M19DXW5X0Q-dsn.algolia.net/1/indexes/fontawesome_com-collections-7.0.0/query?x-algolia-agent=Algolia%20for%20JavaScript%20(5.36.0)%3B%20Search%20(5.36.0)%3B%20Node.js%20(23.3.0)',
  connectTimeout: 2000,
  responseTimeout: 5000
}

we will be getting

  nbHits: 4866,
  page: 0,
  nbPages: 175,
  hitsPerPage: 20,
  exhaustiveNbHits: false,
  exhaustiveTypo: true,
  exhaustive: { nbHits: false, typo: true },
  query: '',
  params: '',
  processingTimeMS: 1,
  processingTimingsMS: {
    _request: { roundTrip: 126 },
    afterFetch: { format: { total: 1 } },
    total: 0
  },
  serverTimeMS: 1

now imagine after which page the search will be broken if we would've had "view all icons" page

[ghost]

im gonna delete my account now but i hope the issue gets fixed as soon as possible (this week for example)

[ghost]

[sensibleworld]

Moving this to a feature discussion.

[sensibleworld]

@ej2 FYI