[Feature Proposal] Custom Query Mapping ("Magic Keyword" Feature)

[JdotCarver]

📌 This proposal builds on the discussion in #3582 , which aims to improve visibility and manageability of topmost entries. This present issue outlines a potential next step in giving users more control over how specific queries return results.

Description

During the discussion in #3582 , it became clear that one of the core issues with result relevance is that the search system doesn’t always align with the user’s intent — particularly for short or ambiguous queries.

This idea builds on that general theme: enabling users to define a custom query that maps to a curated set of results, ordered and optionally isolated from the usual ranked search.

 

Solution

Rather than influencing ranking indirectly (e.g. through usage or topmosting), this would allow users to say:

When I type magic, I want to see Photoshop, Paint, and GIMP — in that order.

This could offer a new layer of precision and predictability, especially for power users with fixed workflows.

• From 3582 : Users have an interface to define a query or keyword (e.g. magic, ps, dev, etc.)
• Improvement of 3582 : They associate that query with a list of specific results
• New : Option to manually set the order of this result
• New : Option to suppress standard search results

 

Why It Might Be Useful

• Users with consistent routines can create predictable search behavior.
• Helps mitigate ambiguity in queries (e.g. ps → multiple possible matches).
• Builds on the idea of “topmost,” but extends it from one item to a result set.

 

Additional context This issue isn’t meant to suggest that implementation should begin now — especially since the ideas in #3582 are still being explored. Rather, it’s an attempt to carry the conversation forward in a way that’s easier to follow and revisit later. By framing this as a separate, longer-term idea, the hope is to make things clearer and more approachable for anyone interested in scoping out future possibilities.