Glad you like it! Devdocs includes Mozilla’s docs, for JS, CSS, DOM, SVG, and others. (But my ranking algorithm doesn’t understand that “mdn” is a synonym for “developers.mozilla.org” so it’s hard to surface them explicitly.)
Thanks for the feature request—I don’t have any frontend JS set up yet that I could easily add this to, but I can see how this could be useful and I’ll put it on my list.
Personally, I’d rather click a link to MDN docs than most other sources, so if you had some way to expose pass-through attribution from devdocs, that’d be useful at least for me.
I wonder how many engineers think about search results link origin before clicking through.
Although I’m sourcing the crawl data from devdocs, the ingestion process uses the upstream URL, so the search results link to developer.mozilla.org with the appropriate favicon.
I’ve heard enough complaints about W3Schools and other SEO-heavy but accuracy-light sources that I suspect a fair proportion of technically-minded users probably consider the ___domain before clicking on a result link.
Thanks for the feature request—I don’t have any frontend JS set up yet that I could easily add this to, but I can see how this could be useful and I’ll put it on my list.