Merge pull request #2988 from duckduckgo/zac/ProgUpdates

more updates for programming mission

.github/PULL_REQUEST_TEMPLATE.md

@@ -12,13 +12,15 @@ your Pull Request.
 
 ###### Description of changes
 
-Provide an overview of the changes this pull request introduces.
+What changes does this PR introduce? 
 
-###### Which issues (if any) does this fix?
+###### Related Issues or Discussions 
 
-Fixes #NNNN - how specifically does it fix the issue?
+What issues or discussions (if any) does this PR address? Please provide the issue # or link.
 
-###### People to notify (@mention interested parties)
+###### People to notify
+
+@mention any relevant people/organizations
 
 
 ---

CONTRIBUTING.md

@@ -1,39 +1,12 @@
 # Contributing an Instant Answer to DuckDuckGo.com
 
-## Learn to Make New Instant Answers
+We're a community dedicated to improving search results with open source, "Instant Answers." Instant Answers use the Web's best APIs and data to solve searches in few or zero clicks. Together and openly, we can create the best search engine for every type of search.
 
-Learn to make an Instant Answer by starting with our walkthroughs:
+**The DuckDuckHack community and DuckDuckGo staff are working together on a mission to create the best search engine for programmers. To fully focus there, we are only accepting Pull Requests and Issues related to the [Programming Mission](https://forum.duckduckhack.com/t/duckduckhack-programming-mission-overview/53).** By working directly with contributors to this mission, we can more quickly provide search data and open source tools which give contributors and their Instant Answers more impact than ever before!
 
-- Learn how to build a [convenient calculation tool](http://docs.duckduckhack.com/walkthroughs/calculation.html)
-- Learn how to turn an [external API into delightful search results](http://docs.duckduckhack.com/walkthroughs/forum-lookup.html)
-- Create a [cheat sheet for a favorite topic](http://docs.duckduckhack.com/walkthroughs/programming-syntax.html)
+[**Join the Programming Mission!**](https://forum.duckduckhack.com/t/duckduckhack-programming-mission-overview/53)  
 
-*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).*
-
-You can find the full [DuckDuckHack documentation here](http://docs.duckduckhack.com).
-
-## Improve a Live Instant Answer
-
-We welcome new contributors to dive in and improve live Instant Answers. It's a great, hands-on way to learn how things work:
-
-- Have a [favorite Instant Answer](http://duck.co/ia) that you want to make even better? Feel free to dive in and make changes.
-- Help other DuckDuckHackers with their [Instant Answers in development](https://duck.co/ia/dev/pipeline)
-- Suggest improvements & file bugs for [live Instant Answers](https://duck.co/ia) through the, "Create Issue" button on each IA page
-- Tackle some of the "low-hanging fruit" and, "high priority" issues on our [Live Issues Page](https://duck.co/ia/dev/issues?tag=lowhangingfruit)
-
-## Go Live on DuckDuckGo.com
-
-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).
-
-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). 
-
-	This page will be the center for feedback, Github issues, attribution, deployment, and collaboration.
-
-2. **Make sure your contribution meets the [Production Guidelines](http://docs.duckduckhack.com/submitting/checklist.html).**
-
-3. **[Submit a pull request](http://docs.duckduckhack.com/submitting/pull-request.html).** 
-
-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]). 
+*Your help and expertise can have a huge impact on improving the search experience for developers and DuckDuckGo users around the world!* 
 
 ## Formatting Your Pull Request
 
@@ -53,7 +26,6 @@ When submitting a pull request, the following guidelines help speed up the revie
 
 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:
 
-	"**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."
+	"**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."
 
 > **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.
-