meilisearch / meilisearch/documentation
Outdated: docs claim Meilisearch has no native support for pinning/promoting documents
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 174
- Forks
- 276
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 6
Description
Two pages still carry a <Tip> stating that Meilisearch offers no native support for promoting, pinning and boosting documents, and redirect readers to blog-post workarounds. Native pinning now exists as Search Rules (/dynamic-search-rules, dynamicSearchRules experimental flag), fully documented under capabilities/search_rules/.
Current text:
Meilisearch does not offer native support for promoting, pinning, and boosting specific documents so they are displayed more prominently than other search results. Consult these Meilisearch blog articles for workarounds on implementing promoted search results with React InstantSearch and document boosting.
Affected files
- capabilities/full_text_search/relevancy/custom_ranking_rules.mdx — line 88 (section "Sorting at search time and custom ranking rules")
live: https://www.meilisearch.com/docs/capabilities/full_text_search/relevancy/custom_ranking_rules#sorting-at-search-time-and-custom-ranking-rules - capabilities/filtering_sorting_faceting/how_to/sort_results.mdx — line 110
live: https://www.meilisearch.com/docs/capabilities/filtering_sorting_faceting/how_to/sort_results
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 with the two affected MDX files: capabilities/full_text_search/relevancy/custom_ranking_rules.mdx and capabilities/filtering_sorting_faceting/how_to/sort_results.mdx. Review the referenced Search Rules documentation at capabilities/search_rules/ and confirm both outdated Tip blocks are updated to reflect native pinning, promoting, and boosting support. Done means the old workaround claim no longer appears on either page and the documentation remains accurate.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100