[docs-infra] Replace <DocSearch> for in-house implementation
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 99.1k
- Forks
- 32.5k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 106
Description
Related page
Kind of issue
Missing information
Issue description
I was looking for how the algolia search is implemented on the homepage. As i can see it doesn't use any mui components, except for the hits that typography and badges are used. Is there any specific reasons on why this is not implemented using the mui's Autocomplete component?
Context 🔦
We need to implement algolia in our site and thinking of how we can do this using material ui. The first option is to build it without the components that are provided from algolia (instantsearch) so that we can leverage the mui components.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the homepage search implementation on mui.com and inspect how , Algolia InstantSearch, and MUI's Autocomplete are currently used. Clarify the desired in-house replacement, its scope, and acceptance criteria before identifying the relevant docs-infra entry points; done should mean the agreed search behavior is implemented without the current DocSearch integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- documentation, frontend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100