[Docs] Clarify search pattern#3949
Open
heatherlarsen wants to merge 3 commits into
Open
Conversation
Add a Search subsection to the TextInput guidelines recommending a standalone search input for broad dataset queries (e.g., App Header) and advising embedding search into the Filter Bar or following Filter Patterns when searching within a filterable dataset. Includes links to the Filter Bar and Filter Patterns docs for further guidance.
Update filter bar guidelines to discourage using the Filter Bar for search-only features and recommend the Text Input instead. Rename and expand the Search section to "Integrating search", add Do/Don't callouts explaining that search should be used alongside filters (not by itself), and include an example image (filter-bar-search-no-filters.png) illustrating the incorrect search-only usage.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
heatherlarsen
changed the title
jorytindall
approved these changes
Jun 25, 2026
jorytindall
left a comment
jorytindall
left a comment
Contributor
There was a problem hiding this comment.
Non-blocking, but just a note about some of the prose, otherwise looks good!
|
|
||
| ### Search | ||
|
|
||
| Use a standalone search input when users are querying a broad dataset without immediate filtering needs, e.g., in the App Header. |
Contributor
There was a problem hiding this comment.
There's something that is throwing me off with this sentence; specifically around "immediate filtering needs" because I kind of view search in most capacities as a type of filter. Maybe something like:
Suggested change
| Use a standalone search input when users are querying a broad dataset without immediate filtering needs, e.g., in the App Header. | |
| Use a standalone search input when users are querying a broad dataset without fine-grained filtering needs, e.g., in the App Header. |
alex-ju
approved these changes
Jun 29, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
📌 Summary
If merged, this PR updates the documentation about the differences between a standalone search input and search within filtering. I've updated the following pages to add clarity:
📸 Screenshots
Text Input Before:
Text Input After:
Filter Bar Before:
Filter Bar After:
🔗 External links
Jira ticket: HDS-6476
Context: Slack thread
💬 Please consider using conventional comments when reviewing this PR.