4 ms·
This looks great! MDN docs are pretty strong. Perhaps devdocs is a superset, but if not, I’d recommend indexing them as well. Also, feature request: it’d be n
by pcl 4y ago
This looks great!
MDN docs are pretty strong. Perhaps devdocs is a superset, but if not, I’d recommend indexing them as well.
Also, feature request: it’d be nice if the query help unfolded the instructions in-line with the current page instead of navigating to another page. That way, I would be able to see them while mucking with my query.
- wolfgang42 4y agoGlad 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.
- pcl 4y agoPersonally, 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.
- wolfgang42 4y agoAlthough 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.
- pcl 4y agoYeah w3schools is the very reason I avoid Google search for code questions.