Add the autocomplete client

README.md

@@ -56,7 +56,8 @@ The exhaustive list of the maintained repositories by the team is available belo
 - [Angular](https://github.com/meilisearch/meilisearch-angular)
 - [React](https://github.com/meilisearch/meilisearch-react)
 - [Vue](https://github.com/meilisearch/meilisearch-vue)
-- [instant-meilisearch](https://github.com/meilisearch/instant-meilisearch): a plugin to establish the communication between Meilisearch and the open-source [InstantSearch](https://github.com/algolia/instantsearch.js) tools (powered by Algolia) for your front-end application.
+- [instant-meilisearch](https://github.com/meilisearch/instant-meilisearch): A search client that enables the integration of the open-source tool [instantsearch.js](https://www.algolia.com/doc/guides/building-search-ui/what-is-instantsearch/js/) with Meilisearch. This client allows you to combine the functionalities of Meilisearch with InstantSearch.js, resulting in a powerful and interactive search user interface.
+- [Autocomplete client](https://github.com/meilisearch/meilisearch-js-plugins/tree/main/packages/autocomplete-client): A search client that enables the integration of the open-source tool [autocomplete-js](https://www.algolia.com/doc/ui-libraries/autocomplete/introduction/what-is-autocomplete/) with Meilisearch. This client allows you to utilize the powerful features of Meilisearch in combination with autocomplete functionality for an enhanced search experience.
 - [docs-searchbar.js](https://github.com/meilisearch/docs-searchbar.js): a search bar integration for all kinds of documentation.
 
 ### 🧩 Platform Plugins

resources/dependencies.md

@@ -9,6 +9,7 @@ They depend on [`meilisearch-js`](https://github.com/meilisearch/meilisearch-js)
 - [`firestore-meilisearch`](https://github.com/meilisearch/firestore-meilisearch/)
 - [`gatsby-plugin-meilisearch`](https://github.com/meilisearch/gatsby-plugin-meilisearch/)
 - [`instant-meilisearch`](https://github.com/meilisearch/instant-meilisearch/)
+- [`autocomplete-client`](https://github.com/meilisearch/meilisearch-js-plugins/tree/main/packages/autocomplete-client)
 - [`strapi-plugin-meilisearch`](https://github.com/meilisearch/strapi-plugin-meilisearch/)
 - [`mini-dashboard`](https://github.com/meilisearch/mini-dashboard/)
 
@@ -34,6 +35,7 @@ Also, even if they are not parts of the integration team, we should keep in mind
 ## Instant Meilisearch
 
 They depend on [`instant-meilisearch`](https://github.com/meilisearch/instant-meilisearch/)
+- [`autocomplete-client`](https://github.com/meilisearch/meilisearch-js-plugins/tree/main/packages/autocomplete-client)
 - [`meilisearch-angular`](https://github.com/meilisearch/meilisearch-angular/) and the [associated code-sandbox](https://codesandbox.io/s/im-angularis-7xipe?file=/src/app/app.component.ts)
 - [`meilisearch-react`](https://github.com/meilisearch/meilisearch-react/) and the [associated code-sandbox](https://codesandbox.io/s/ms-react-is-sh9ud?fontsize=14&hidenavigation=1&theme=dark)
 - [`meilisearch-vue`](https://github.com/meilisearch/meilisearch-vue/) and the [associated code-sandbox](https://codesandbox.io/s/ms-vue-is-1d6bi?fontsize=14&hidenavigation=1&theme=dark)

resources/scopes.md

@@ -38,6 +38,7 @@ Same, if you are not responsible for a scope, you are always encouraged to check
 | [React integration](https://github.com/meilisearch/meilisearch-react) | [bidoubiwa](https://github.com/bidoubiwa/) |
 | [Vue integration](https://github.com/meilisearch/meilisearch-vue) | [bidoubiwa](https://github.com/bidoubiwa/) |
 | [instant-meilisearch](https://github.com/meilisearch/instant-meilisearch) | [bidoubiwa](https://github.com/bidoubiwa/) | [brunoocasali](https://github.com/brunoocasali/) & [mdubus](https://github.com/mdubus/) |
+| [autocomplete-client](https://github.com/meilisearch/meilisearch-js-plugins) | [bidoubiwa](https://github.com/bidoubiwa/) | [brunoocasali](https://github.com/brunoocasali/) |
 | [docs-searchbar.js](https://github.com/meilisearch/docs-searchbar.js) | [bidoubiwa](https://github.com/bidoubiwa/) | [mdubus](https://github.com/mdubus/) | [bidoubiwa](https://github.com/bidoubiwa/) |
 |||
 | [Firestore extension](https://github.com/meilisearch/firestore-meilisearch) | [bidoubiwa](https://github.com/bidoubiwa/) | [alallema](https://github.com/alallema/) |

resources/tiers.md

@@ -41,6 +41,7 @@ Integration | Tier |
 Javascript | #1 |
 PHP | #1 |
 Instant Meilisearch | #1 |
+Autocomplete client | #1 |
 Python | #1 |
 Ruby | #1 |
 Go | #1 |
@@ -88,9 +89,9 @@ Every pre-release has its central issue ([like this one](https://github.com/meil
 
 But if, for some reason, the team does not finish implementing on time, it still is the top priority to finish it before anything else. If only parts of the features are available on the release D-Day, the team will evaluate how long it will take to finish them. Depending on the integration tier, and the time it would take the team to finish, we will release the integration with the partial implementations. These are the delays we accept per tier before releasing:
 
-Tier #1 = Release day + 1 day  
-Tier #2 = Release day + 1 week  
-Tier #3 = Release day + unlimited  
+Tier #1 = Release day + 1 day
+Tier #2 = Release day + 1 week
+Tier #3 = Release day + unlimited
 
 So, if a tier #1 SDK is not fully ready on the Meilisearch engine release day, the user can expect a release in **any case on the following day**. Yes, __this release may lack some of the features planned initially__. Those features will be implemented as a top priority.<br/>
 The same can happen with tier #2. If it is not fully ready, you can expect a release **a week after the release day**, and the remaining features will be implemented in the following weeks.<br/>