How to choose a DuckDuckGo cheatsheet topic

If you want to develop a DuckDuckGo cheatsheet and you’ve got the technicals down, the next task is to choose a cheatsheet topic. As with naming things, this can be harder than it sounds.

Certain topics are better suited to be cheatsheets than others; because the cheatsheet is a static file, it’s better to provide information which is unlikely to change, such as a list of the members of the Wu-Tang Clan. With that in mind, here are some good sources of inspiration for your cheatsheet.

Scan the cheatsheet corpus

Get inspiration from association. The DuckDuckGo goodie repo maintains all of the static cheatsheets. Have a look at them, maybe you’ll get an idea for something similar to what’s already been done. I made the GNU Screen cheatsheet after I saw the tmux one - there was a lot of copy and paste involved!

Check the instant answer request list

One way to get cheatsheet ideas is to think about technical and trivia subjects you’re interested in. That’s “supply”. Another way is to look at “demand” - i.e. what people have asked for. Helpfully, the DuckDuckGo community maintains an extensive list of instant answer ideas. Have a browse!

Mine Google AdWords

Another way to view demand is to check search traffic. This is an old SEO trick to find common associations with a keyword using the Google AdWords keywords planner tool. For example I used the tool to find the top 50 searches associated with the term “cheatsheet”:

KeywordAvg. Monthly Searches (exact match only)
markdown cheatsheet1900
vim cheatsheet1600
git cheatsheet1600
regex cheatsheet1300
vi cheatsheet1000
jquery cheatsheet480
fantasy football cheatsheet390
cheatsheets390
html cheatsheet390
subnet cheatsheet390
python cheatsheet390
fantasy football cheatsheets320
xss cheatsheet320
sql cheatsheet320
gdb cheatsheet320
emacs cheatsheet260
latex cheatsheet260
linux cheatsheet210
screen cheatsheet210
r cheatsheet210
svn cheatsheet170
php cheatsheet170
html5 cheatsheet170
sql injection cheatsheet170
ruby cheatsheet170
regular expression cheatsheet140
bash cheatsheet140
uml cheatsheet140
css3 cheatsheet110
xpath cheatsheet90
perl cheatsheet70
unix cheatsheet70
django cheatsheet70
subnet mask cheatsheet70
c# cheatsheet70
powershell cheatsheet70
asciidoc cheatsheet70
fantasy cheatsheet50
rails cheatsheet50
mediawiki cheatsheet40
regular expressions cheatsheet40
zfs cheatsheet40
free fantasy football cheatsheets30
dailybeast cheatsheet30
dmv cheatsheet30
fantasy football draft cheatsheet30
fantasy baseball cheatsheet30
photobert cheatsheet30
cheatsheet html30
autosys cheatsheet30

If nothing in this list appeals, try searching against similar terms like “cheat sheet”, “help”, “FAQ” and “usage” to find something that inspires you.

Conclusion

Developing cheatsheets should be fun. If you’re wrestling with a potential cheatsheet topic remember that there is a large developer community waiting to help you. The DuckDuckHack site is a good source of information. It has a FAQ, a guide to picking the right plugin type for your idea and information on how to join the DuckDuckGo Slack site. Useful information can also be found in the quack and hack cheatsheet!

Once you’ve drafted your cheatsheet, consider using my cheatsheet checker tool. It finds common syntax and data errors which can make developing a cheatsheet easier.


This article was originally posted on PerlTricks.com.

Tags

David Farrell

David is the editor of Perl.com. An organizer of the New York Perl Meetup, he works for ZipRecruiter as a software developer, and sometimes tweets about Perl and Open Source.

Browse their articles

Feedback

Something wrong with this article? Help us out by opening an issue or pull request on GitHub