-
Notifications
You must be signed in to change notification settings - Fork 7.1k
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
Integrations Search experience #11682
Comments
I was thinking about this very issue the other day. Another good example is that Neato was acquired by Vorwerk and users must know that those robots (vorwerk) support the Neato API and they can use them. I wonder if we need to allow for custom search terms maybe? |
Absolutely a good improvement, however, this needs quite a bit of rework on how we work with integrations in general on our website. Part of setting this in motion has started, as I'm currently working on creating a central resource for our data (our codebase) and importing/syncing that data with the website. I guess we could extend this for the future to make things like this possible. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still an issue (I know this is a longer-term thing, only posting for stalebot to keep it open) edit: I guess I was too late on that... oops |
It seems that currently, the search on Integrations page of the website only searches titles. The problem with that is many integrations can be called different things.
And so on. Home Assistant does have these integrations, and these are all valid search terms for them, but the user just gets a "Nothing found!" error and comes up empty handed. Some users might think of refining their search keyword, but others will just assume it's unsupported and move on.
Don't know whether this is possible with the current setup (as it appears to be a simple filter of title), but it'd be nice if there was a way to add additional metadata / aliases for search purposes so that it would catch these examples and point the user to the right place.
The text was updated successfully, but these errors were encountered: