add keyword search capabilities #203
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
jasonLaster
approved these changes
Jun 18, 2024
filiphric
force-pushed
the
filip/dev-495-docs-structure-does-not-play-well-with-search-and-breadcumbs
branch
from
fc8f3d8 to
a6e260c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should close DEV-495 and PRO-607.
The way I’m trying to solve search issues is by adding
keywordsfrontmatter attribute that can be fed with keywords. Content should be easier to search in that case. For example if we have "PR Comments" section in navigation, but the title of this page says "Pull request comments", it should be easily found if a keyword such as "PR Comments" is added to the list of keywords.