Closed Bug 1246459 Opened 5 years ago Closed 5 years ago
prioritize web api reference by default
> Would you know which filter to use to make your search better? Do users use filters? My instinct is no but we can probably check with GA. > Regarding boosting specific topics over other topics, I haven't seen anything about the purpose of MDN search. As I understand it, we have a few different audiences -- web developers, addon developers, fxos open webapp devs, firefox hackers, maybe others. I'm suggesting we could quickly optimize the search results for one of those audiences at the expense of the others by changing the default filters.
Our largest audience is, by far, Web developers.
That UI sounds really flexible, but changing the defaults is a more powerful measure
This is extremely important to the devrel team- increasing the relevance of MDN search results for web developers will make education and adoption much easier.
Agreed. Web Developers are the primary audience for MDN and should be the default.
I talked to Lonnen about this. I'm going to grab it and work on it this week.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
It'd help to have like 5 different search queries to play with as I'm tinkering with search stuff. * bind * ... What are four more that exhibit this behavior where it exists in multiple categories, but we want web-related ones to show up higher? If no one can think of others, I'll spend some time doing GA poking. Figured I'd ask in case there were.
These have the desired result on the second page * bind * call These have the desired results on the first page, but lower than Firefox internals versions of the web api * window * promise * workers * xmlhttprequest * apply * postmessage * navigator These have a single good result on the top and the rest of the page is not quality: * regexp These have an obscure result in the web api above the obvious common result and may not be worth fixing in this bug: * slice
Assignee: willkg → nobody
Status: ASSIGNED → NEW
Pushed the unfinished branch here: https://github.com/mozilla/kuma/tree/1246459-search Gist that has my harness is here: https://gist.github.com/willkg/e827829d3d8065a0c5bc
Assignee: nobody → robhudson
I think "APIs & DOM" is needed too as this includes all the Web APIs that are not in the JS definition.
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/4be458dceed0132e4ecad2eb36f3cab98cb333c2 Fix bug 1246459 - Prioritize web by default https://github.com/mozilla/kuma/commit/7f15829572f2872795363c8d5929ec615cce8c7c Merge pull request #3814 from robhudson/1246459-search-web Fix bug 1246459 - Prioritize web by default
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Is there a follow-up bug for APIs & DOM? Definitely need that turned on as well.
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.