I’m trying to make our design system easier to search by including alternate search terms/tags in the description of the component, and it’s a frustrating experience. I can’t rename the component itself, because we want to keep naming 1:1 with an existing web framework, so I’m adding in alternate search terms in the descriptions.
Using the component description works to an extent, by which I mean that the component will appear… somewhere in the middle of a long list.
For example, if I search for “dropdown”, my asset panel results will contain a mix of dropdown menu items, icons with “down” in the name, the actual component I want to highlight somewhere in the middle of this, as well as some assets that are completely unrelated to dropdowns if I have other libraries turned on in the document.
Many of our components are nested and contain several items for constructing menus (dropdown/item, dropdown/separator etc.) , and these are often shown with equal or more priority than the core component itself. At the same time, we don’t want make those menu items unavailable to our designers by unpublishing them.
If I could somehow prioritize components in search so that my team can more easily find the core items they are looking for, that would be amazing! I know I can change the background color of component to highlight individual items, but it would be really useful to add something more robust like a tagging system, since that could be used as search filters too.