PageRenderTime 12ms CodeModel.GetById 1ms app.highlight 7ms RepoModel.GetById 2ms app.codeStats 0ms

Markdown | 71 lines | 48 code | 23 blank | 0 comment | 0 complexity | e8cd921b7df442c8b40b6daac3312f77 MD5 | raw file
 2[Index]( / **FAQ**
 6### Why should I make plugins?
 8We hope you will consider making DuckDuckGo plugins to:
10* Improve results in areas you personally search and care about, e.g. [programming documentation](, [gaming]( or [entertainment](
11* Increase usage of your own projects, e.g. data and [APIs](
12* Learn something new.
13* Attribution [on our site]( and [Twitter]( (working on more).
14* See your code live on a [growing]( search engine!
16### What if I'm not a coder at all?
18If you don't code at all and you've ended up here, please go over to our [ideas companion site]( where you can suggest and comment on plugin ideas such as identifying the best sites and data sources to draw from. Similarly, you can submit [issues about current plugins]( Both of these activities are very valuable and will help direct community efforts.
20If you're a business and want your data to be utilized, adding your service to []( is a great way for your API to get picked up by a developer and integrated into the search engine.
23### Can you help me?
25  Of course! Here are the easiest ways to contact someone who can help answer your questions:
27 * Write us publicly on the [discussion list](
28 * Write us privately at
30### What if I don't know Perl?
31If you don't know Perl, that's OK! Several <a href="">plugin types</a> are not in Perl. Also, if you know PHP, Ruby, or Python you should be able to write Goodies in Perl pretty easily using [this awesome cheat sheet](
33### Do you have any plugin ideas?
34Yup! We maintain [a growing list]( There are also improvement ideas for [Goodies](, [Spice](, [Fathead]( and [Longtail](
36### How do I note that I've started on something?
37In your initial pull request, please note the link on the [idea list]( We'll move it to the "in process" bucket for you.
39### Where I can report plugin bugs?
40Submit GitHub issues in the [appropriate repo](
42### What if there are plugin conflicts?
43The ultimate arbiter is the user, and that's the perspective we take. In other words, we ask "what is best for the user experience?" That said, it often makes sense to combine ideas into one, better plugin.
45### Why isn't my plugin in the [DuckDuckGo Instant Answers API](
46If your plugin is spice or longtail, sometimes we can't expose it through the API for licensing reasons (e.g. the WolframAlpha plugin), but our
47over-arching goal is to make all of our instant answers available on their own.
49### Can I do something more complicated?
50Maybe. There are a bunch more internal interfaces we haven't exposed yet, and we'd love to hear your ideas to influence that roadmap.
52### What's the roadmap?
53Here's what we're working on (in roughly in this order):
55* better testing/file structure for spice plugins.
56* better JS interface for spice plugin callback functions.
57* better attribution.
58* embedding plugins.
59* better testing/file structure for fathead plugins.
60* more defined structure for longtail plugins.
61* better testing for longtail plugins.
63### Are there other open source projects? 
64Yes! Check out the other repositories in [our GitHub account]( You can email if you have any questions on those.
66### Can I get the instant answers through an API?
67Yes! Check out the [DuckDuckGo API]( Our goal is to make as many plugins as possible
68available through this interface. Fathead and goodie plugins are automatically syndicated through the API, and Spice and Longtail are selectively (due to licensing complications) mixed in.
70### Can I talk to you about a partnership idea?###
71Sure -- check out [our partnerships page](