[projproj]

Check out tomdn.com. I created it to make it easier to get to MDN. E.g., instead of googling array.map, just type tomdn.com?array.map. It will take you straight to MDN docs on Array.prototype.map. Other things work as well, like tomdn.com?object.keys, tomdn.com?css.color, tomdn.com?htmlel.button, etc.

If there is a pattern it doesn't recognize, you end up on the MDN search results page.

edit: More info. about how it works is available here: https://github.com/tayler/tomdn

[hnarn]

What value does this provide over simply Googling or DDG'ing "array.map mdn"? It's shorter and the first result for me is (unsurprisingly) MDN on both, and I don't have to run my searches through an unknown third party.

DDG also has !bangs for this specific purpose and !mdn does, as expected, lead you to MDN.

[projproj]

Valid questions. I just think it's faster. One action on tomdn.com instead of 1. DDG "array.map mdn", 2. Find MDN result (usually first), 3. Click result, 4. See docs.

Bangs are great, just shorter again to use tomdn.com: - `!mdn array.map` leads me to https://developer.mozilla.org/en-US/search?q=array.map, which I have to scan the results and click on. - tomdn.com?array.map leads me to the exact page in the docs. https://developer.mozilla.org/en-US/docs/Web/Javascript/Refe...

This may or may not be valuable, but I like saving the extra steps for something I do many times a week. Basically this calculation (https://xkcd.com/1205/) works out for me + the fun of working on a new project.

edit: >I don't have to run my searches through an unknown third party

Very sympathetic to this concern. Feel free to host yourself -- it's a single html file. https://github.com/tayler/tomdn