Weekly Update 126: Focusing on Fatheads
This is a copy of our weekly newsletter for developers which you can subscribe to here.
Since we started putting statistics about Instant Answer performance on the forum (see here for a summary), we've noticed that Fatheads tend to have the highest coverage. This is a helpful insight but what does that mean?
But what about coverage? Although interactive IAs and cheat sheets tend to get the most attention in blogs and social media, Fathead reference IAs are generally shown more often for searches on a particular topic, especially programming languages. We call this "coverage" and although it's not a perfect measure of an IA's success, a higher figure is usually better if triggering is accurate.
Based on this, we'd like to try focusing on Fatheads, both creating new ones and improving existing ones, to have a bigger impact for more programmers. To make this easier, we've been working with the language leaders to break down big tasks into smaller issues that anyone can pick up. With proper labelling, this generates a handy list of issues available for contributors, as you can see here:
This should help anybody wondering "how can I contribute to DuckDuckGo?" and as usual, let's highlight a few specific issues...
- MDN JS: Show the first example in the article
For coders, examples are often the best way to learn.
- Python: Add python version as subtitle
To distinguish between Python 2 and 3, the version should be added to the article title in parenthesis, in the output.txt file.
- NodeJS Bug: Not triggering for some articles
A lot of the docs articles don't trigger, e.g. searching for "node dns lookupService", "node child disconnect" or "node http message service" doesn't show a NodeJS result.
- NodeJS: Add common redirects
One approach is to replace symbols such as dots with spaces; e.g. "http.Agent" should have an "http agent" redirect.
Firstly you need to open your .gitconfig file which can be done with:
git config --global --edit
Now simply add the following two lines:
[url "firstname.lastname@example.org:"] insteadOf = gh:
After a reboot, you can now save key strokes when you clone a repository or add a remote upstream repository by using this syntax:
git clone gh:duckduckgo/zeroclickinfo-goodies
Isn't that clever? Of course, you can also use it for other Git phrases you use a lot.
Hope you have a great weekend!
- The DuckDuckGo Staff