siriwatknp
commented
3 years ago Backup data
These are the records that are sent to algolia.
Closed siriwatknp closed 3 years ago
siriwatknp
commented
3 years ago These are the records that are sent to algolia.
eps1lon
commented
3 years ago I don't know how to interpret the data. All I'm interested is query -> results mapping. For that we should just focus on the diff between the results but that's hard to do with how you represent the data.
Problematic queries are listed in https://github.com/mui-org/material-ui/issues/16502
siriwatknp
commented
3 years ago I don't know how to interpret the data
You mean the data in this link is confusing? https://siriwatknp.github.io/mui-docsearch/. I have updated the RFC description, may be that helps.
Issues
cannot search
theme(display 5 result withDefault Theme)componentscategory does not come up as 1st suggestion (in the case below it should showButtoncomponent first) #19986Root cause
✅ 1. cannot search
theme(display 5 result withDefault Theme)This is already fixed by https://github.com/algolia/docsearch-configs/pull/4589
2.
componentscategory does not come up as 1st suggestionFrom my analysis about the current config in docsearchconfig repo. I found that
only_content_level: truein the config. This is the explanation in docsearch. This means the search result always contain content which does not leverage auto grouping in docsearch client library. This is how index is built.3. few suggestion (the result are at max 5 items)
We can specify
hitsPerPage: numbertodocsearchclient library to get more result. Fortunately, we can just upgrade the docsearch to v3 and it should be fine #28252 (WIP)Proposal
Give ranking to each group of pages with
page_rankattribute order byremove
only_content_level: truefrom the config. This is the result after removing the fieldadd `selectors_exclude: [".prevent-docsearch-index"]. There are some part of the site that might not need indexed, such as material icon name (currently 1700+ icons are indexed).
Steps