-
Notifications
You must be signed in to change notification settings - Fork 394
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
Add Search functionality to Blog #2712
Comments
I think this is doable! Are we planning to mimic the design of the doc's search input? Also, where do we want this input to be placed on the blog? The search input for the docs is in the sidebar, but the blog doesn't have a sidebar 🤔 |
It means that we need some design input here. Let's put it in the list of things for the design team. |
Do we have a deadline or priority level for this issue? |
Tomorrow? Just kidding. To me this should have always been there. Now that we have more content, it's much more important. I know you've got other things to tend to and I don't know how time consuming this is. If it helps this is how I would rank the issues I have, in importance from greatest to least, but all accomplished by end of quarter. 😬
If you told me, "there's no way we can do all that by the end of the year with everything else," I'd say cut out 2 and 3 and put them in Q1 '22. The rest need to get done. |
@DavidGOrtega also mentioned using faceted search! |
What does that mean? |
Faceted search is a way of searching by applying filters to your search (like how you can narrow down your search on Amazon by selected the color or size you want). We already have tags on our blog posts. Maybe we can show the available tags below wherever we place the search bar, allowing users to select them 🤔 |
Yes! I like this idea. It will send them to more content they didn't even know they were looking for! Please yes! |
@yathomasi please take a look at the review. |
As the content grows, it would be good to have an internal search function for the blog like we do on the docs.
The text was updated successfully, but these errors were encountered: