-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make blog post search better #695
base: master
Are you sure you want to change the base?
Conversation
Updating build logging Showing message when nothing is found
we can pass terms in as an array
Weighting slug and title the same
@@ -532,7 +533,7 @@ const cfg: GatsbyConfig = { | |||
// List of keys to index. The values of the keys are taken from the | |||
// normalizer function below. | |||
// Default: all fields | |||
index: ['title', 'searchable_tags'], | |||
index: ['slug', 'title', 'searchable_tags'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the slug
sometimes contains some interesting values that might match what the user is searching for
@danthelion - one idea I have been considering is making a list of like maybe 10 top terms we really want to make sure can be found and search for them automatically for users. Meaning - if someone searches |
Visit the preview URL for this PR (updated for commit 4c0459c): https://estuary-marketing--pr695-travjenkins-bug-blog-r4jujlc5.web.app (expires Fri, 07 Mar 2025 23:10:03 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 76f6b095a0752e5d9c6c890267f9fdc3e392161e |
Label
generate-pr-preview
required before opening PR for preview buildChanges
Tests / Screenshots
Now we will inform user when we cannot find blog posts
gcs
search returns less results but much more accurate to query