|
1 | 1 | # Contributing an Instant Answer to DuckDuckGo.com |
2 | 2 |
|
3 | | -> You can find the full [DuckDuckHack documentation here](http://docs.duckduckhack.com) |
| 3 | +## Learn to Make New Instant Answers |
4 | 4 |
|
5 | | -Have an idea [that no one has done yet](https://duck.co/ia)? Improving an [existing Instant Answer](https://duck.co/ia/dev/issues)? |
| 5 | +Learn to make an Instant Answer by starting with our walkthroughs: |
6 | 6 |
|
7 | | -1. **Before coding, [create an Instant Answer Page](https://duck.co/ia/new_ia) for your idea.** If you're fixing an existing Instant Answer, [locate its existing page](https://duck.co/ia). |
| 7 | +- Learn how to build a [convenient calculation tool](http://docs.duckduckhack.com/walkthroughs/calculation.html) |
| 8 | +- Learn how to turn an [external API into delightful search results](http://docs.duckduckhack.com/walkthroughs/forum-lookup.html) |
| 9 | +- Create a [cheat sheet for a favorite topic](http://docs.duckduckhack.com/walkthroughs/programming-syntax.html) |
8 | 10 |
|
9 | | - > Instant Answer Pages are the "home base" for each Instant Answer. They are where the community plans, collaborates, and tracks the [life cycle](http://docs.duckduckhack.com/submitting/long-term.html) of all Instant Answers. It's where we aggregate pull requests, issues, attribution, and feedback. |
| 11 | +*UPDATE: We're aiming to have multiple Instant Answers for every programming language and framework. Jump in and help us [fill in the blanks](https://github.com/duckduckgo/duckduckgo/wiki/Programming-IA-Coverage).* |
10 | 12 |
|
11 | | -2. **Hack away, keeping the [Instant Answer Production Guidelines](http://docs.duckduckhack.com/submitting/checklist.html) in mind.** |
| 13 | +You can find the full [DuckDuckHack documentation here](http://docs.duckduckhack.com). |
12 | 14 |
|
13 | | -3. **[Submit a pull request](http://docs.duckduckhack.com/submitting/pull-request.html).** |
| 15 | +## Improve a Live Instant Answer |
| 16 | + |
| 17 | +We welcome new contributors to dive in and improve live Instant Answers. It's a great, hands-on way to learn how things work: |
| 18 | + |
| 19 | +- Have a [favorite Instant Answer](http://duck.co/ia) that you want to make even better? Feel free to dive in and make changes. |
| 20 | +- Help other DuckDuckHackers with their [Instant Answers in development](https://duck.co/ia/dev/pipeline) |
| 21 | +- Suggest improvements & file bugs for [live Instant Answers](https://duck.co/ia) through the, "Create Issue" button on each IA page |
| 22 | +- Tackle some of the "low-hanging fruit" and, "high priority" issues on our [Live Issues Page](https://duck.co/ia/dev/issues?tag=lowhangingfruit) |
| 23 | + |
| 24 | +## Go Live on DuckDuckGo.com |
| 25 | + |
| 26 | +The final step is to have your contribution appear on DuckDuckGo.com above ads and organic links, on [millions of searches](https://duckduckgo.com/traffic.html). |
| 27 | + |
| 28 | +1. **[Create an Instant Answer Page](https://duck.co/ia/new_ia) as the home base for your idea.** If you're fixing an existing Instant Answer, [locate its existing page](https://duck.co/ia). |
14 | 29 |
|
15 | | - > Make sure to paste your Instant Answer page URL in the description. This will automatically link the two. |
| 30 | + This page will be the center for feedback, Github issues, attribution, deployment, and collaboration. |
16 | 31 |
|
17 | | -We're excited to meet you and support you along the way - and it's never too early to say hello. Join us on [Slack](mailto:[email protected]?subject=AddMe) or [email](mailto:open@duckduckgo.com). |
| 32 | +2. **Make sure your contribution meets the [Production Guidelines](http://docs.duckduckhack.com/submitting/checklist.html).** |
18 | 33 |
|
19 | | -*The opportunities to contribute don't stop here. Learn about [keeping your IA awesome](http://docs.duckduckhack.com/submitting/long-term.html).* |
| 34 | +3. **[Submit a pull request](http://docs.duckduckhack.com/submitting/pull-request.html).** |
20 | 35 |
|
| 36 | +We're excited to meet you and support you along the way - and it's never too early to say hello. Join us on [Slack ](https://quackslack.herokuapp.com) or [email ](mailto:[email protected]). |
21 | 37 |
|
22 | | -## Pull Request Format |
| 38 | +## Formatting Your Pull Request |
23 | 39 |
|
24 | 40 | When submitting a pull request, the following guidelines help speed up the review process: |
25 | 41 |
|
26 | | -If your IA is new, use the format: `"New {IA TOPIC} {IA TYPE}"`. For example: |
| 42 | +### New Instant Answers |
27 | 43 |
|
28 | | - - "New Instagram Spice" |
29 | | - - "New Firefox Cheat Sheet" |
30 | | - |
31 | | -If you're submitting a fix, use the title format: `"{IA NAME}: Brief explanation`. For example: |
32 | | - |
33 | | - - "PeopleInSpace: Use smaller local image, fallback to API when needed." |
| 44 | +1. New IAs should be titled as follows: **`New {IA TOPIC} {IA TYPE}`**. For example, `New Instagram Spice` or `New Firefox Cheat Sheet` |
| 45 | + |
| 46 | +2. Paste the relevant [Instant Answer Page URL](https://duck.co/ia/new_ia) in the description field. This will automatically link the PR to the Instant Answer. |
34 | 47 |
|
35 | | -Include the issue number in the description (conveniently, this will automatically resolve the issue upon merging). Describe your motivation, thought process, and solution in the description. For example: |
| 48 | +### Improvements |
| 49 | + |
| 50 | +1. Fixes should be titled as follows: **`{IA NAME}: Brief explanation`**. For example: `PeopleInSpace: Use smaller local image, fallback to API when needed.` |
| 51 | + |
| 52 | +2. Paste the relevant [Instant Answer Page URL](https://duck.co/ia/new_ia) in the description field. This will automatically link the PR to the Instant Answer. |
36 | 53 |
|
37 | | - - "**Fixes #2038.** The images used by the API are very large and don't change often. I've but a smaller version of each image (and a 2x version for retina screens) in the share directory. The callback will try and load a local image based on the astronauts name and fallback to using the API's image if one does not exist." |
| 54 | +3. Include the issue number in the description (conveniently, this will automatically resolve the issue upon merging). Describe your motivation, thought process, and solution in the description. For example: |
38 | 55 |
|
39 | | -**Finally, don't forget to paste the relevant [Instant Answer Page URL](https://duck.co/ia/new_ia) in the description field**, while creating new pull requests. This will automatically link the two. |
| 56 | + "**Fixes #2038.** The images used by the API are very large and don't change often. I've put a smaller version of each image (and a 2x version for retina screens) in the share directory. The callback will try and load a local image based on the astronauts name and fallback to using the API's image if one does not exist." |
40 | 57 |
|
41 | 58 | > **IMPORTANT:** Don't worry if you get an initial error regarding failing Travis tests. The reason is that your IA page hasn't yet been moved out of the "Planning" status - which only community leaders/staff can do. As long as the ID in your IA page matches the ID in your code, and you've pasted the URL to your IA page, you can ignore this initial error. |
42 | 59 | |
0 commit comments