Make links to contribution material point to the website

.github/PULL_REQUEST_TEMPLATE

@@ -1,6 +1,6 @@
 ### What is this PR for?
 A few sentences describing the overall goals of the pull request's commits.
-First time? Check out the contributing guide - https://github.com/apache/zeppelin/blob/master/CONTRIBUTING.md
+First time? Check out the contributing guide - https://zeppelin.apache.org/contribution/contributions.html
 
 
 ### What type of PR is it?

README.md

@@ -3,7 +3,7 @@
 **Documentation:** [User Guide](http://zeppelin.apache.org/docs/latest/index.html)<br/>
 **Mailing Lists:** [User and Dev mailing list](http://zeppelin.apache.org/community.html)<br/>
 **Continuous Integration:** [![Build Status](https://secure.travis-ci.org/apache/zeppelin.png?branch=master)](https://travis-ci.org/apache/zeppelin) <br/>
-**Contributing:** [Contribution Guide](https://github.com/apache/zeppelin/blob/master/CONTRIBUTING.md)<br/>
+**Contributing:** [Contribution Guide](https://zeppelin.apache.org/contribution/contributions.html)<br/>
 **Issue Tracker:** [Jira](https://issues.apache.org/jira/browse/ZEPPELIN)<br/>
 **License:** [Apache 2.0](https://github.com/apache/zeppelin/blob/master/LICENSE)
 
@@ -18,7 +18,7 @@ Core feature:
 To know more about Zeppelin, visit our web site [http://zeppelin.apache.org](http://zeppelin.apache.org)
 
 ## Requirements
- * Git 
+ * Git
  * Java 1.7
  * Tested on Mac OSX, Ubuntu 14.X, CentOS 6.X, Windows 7 Pro SP1
  * Maven (if you want to build from the source code)
@@ -67,7 +67,7 @@ First of all, set your proxy configuration on Maven `settings.xml`.
 </settings>
 ```
 
-Then, run these commands from shell. 
+Then, run these commands from shell.
 ```
 npm config set proxy http://localhost:3128
 npm config set https-proxy http://localhost:3128
@@ -87,10 +87,10 @@ git config --global --unset https.proxy
 git config --global --unset url."http://".insteadOf
 ```
 
-_Notes:_ 
+_Notes:_
  - If you are behind NTLM proxy you can use [Cntlm Authentication Proxy](http://cntlm.sourceforge.net/).
  - Replace `localhost:3128` with the standard pattern `http://user:pwd@host:port`.
- 
+
 #### Install maven
 ```
 wget http://www.eu.apache.org/dist/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz

docs/README.md

@@ -1,6 +1,6 @@
 # Apache Zeppelin documentation
 
-This README will walk you through building the documentation of Apache Zeppelin. The documentation is included here with Apache Zeppelin source code. The online documentation at [https://zeppelin.apache.org/docs/<ZEPPELIN_VERSION>](https://zeppelin.apache.org/docs/latest) is also generated from the files found in here. 
+This README will walk you through building the documentation of Apache Zeppelin. The documentation is included here with Apache Zeppelin source code. The online documentation at [https://zeppelin.apache.org/docs/<ZEPPELIN_VERSION>](https://zeppelin.apache.org/docs/latest) is also generated from the files found in here.
 
 ## Build documentation
 Zeppelin is using [Jekyll](https://jekyllrb.com/) which is a static site generator and [Github Pages](https://pages.github.com/) as a site publisher. For the more details, see [help.github.com/articles/about-github-pages-and-jekyll/](https://help.github.com/articles/about-github-pages-and-jekyll/).
@@ -19,7 +19,7 @@ bundle install
 
 For the further information about requirements, please see [here](https://help.github.com/articles/setting-up-your-github-pages-site-locally-with-jekyll/#requirements).
 
-On OS X 10.9, you may need to do 
+On OS X 10.9, you may need to do
 
 ```
 xcode-select --install
@@ -39,7 +39,7 @@ Using the above command, Jekyll will start a web server at `http://localhost:400
 
 
 ## Contribute to Zeppelin documentation
-If you wish to help us and contribute to Zeppelin Documentation, please look at [Zeppelin Documentation's contribution guideline](https://github.com/apache/zeppelin/blob/master/docs/CONTRIBUTING.md).
+If you wish to help us and contribute to Zeppelin Documentation, please look at [Zeppelin Documentation's contribution guideline](https://zeppelin.apache.org/contribution/contributions.html).
 
 
 ## For committers only
@@ -49,7 +49,7 @@ If you wish to help us and contribute to Zeppelin Documentation, please look at
 
 ### Deploy to ASF svnpubsub infra
  1. generate static website in `./_site`
-    
+
     ```
     # go to /docs under Zeppelin source
     bundle exec jekyll build --safe

docs/development/writingzeppelininterpreter.md

@@ -42,7 +42,7 @@ In 'Separate Interpreter(scoped / isolated) for each note' mode which you can se
 Creating a new interpreter is quite simple. Just extend [org.apache.zeppelin.interpreter](https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/Interpreter.java) abstract class and implement some methods.
 You can include `org.apache.zeppelin:zeppelin-interpreter:[VERSION]` artifact in your build system. And you should put your jars under your interpreter directory with a specific directory name. Zeppelin server reads interpreter directories recursively and initializes interpreters including your own interpreter.
 
-There are three locations where you can store your interpreter group, name and other information. Zeppelin server tries to find the location below. Next, Zeppelin tries to find `interpreter-setting.json` in your interpreter jar. 
+There are three locations where you can store your interpreter group, name and other information. Zeppelin server tries to find the location below. Next, Zeppelin tries to find `interpreter-setting.json` in your interpreter jar.
 
 ```
 {ZEPPELIN_INTERPRETER_DIR}/{YOUR_OWN_INTERPRETER_DIR}/interpreter-setting.json
@@ -73,7 +73,7 @@ Here is an example of `interpreter-setting.json` on your own interpreter.
   },
   {
     ...
-  } 
+  }
 ]
 ```
 
@@ -207,7 +207,7 @@ Checkout some interpreters released with Zeppelin by default.
 
 We welcome contribution to a new interpreter. Please follow these few steps:
 
- - First, check out the general contribution guide [here](https://github.com/apache/zeppelin/blob/master/CONTRIBUTING.md).
+ - First, check out the general contribution guide [here](https://zeppelin.apache.org/contribution/contributions.html).
  - Follow the steps in [Make your own Interpreter](#make-your-own-interpreter) section above.
  - Add your interpreter as in the [Configure your interpreter](#configure-your-interpreter) section above; also add it to the example template [zeppelin-site.xml.template](https://github.com/apache/zeppelin/blob/master/conf/zeppelin-site.xml.template).
  - Add tests! They are run by [Travis](https://travis-ci.org/apache/zeppelin) for all changes and it is important that they are self-contained.
@@ -215,4 +215,3 @@ We welcome contribution to a new interpreter. Please follow these few steps:
  - Add documentation on how to use your interpreter under `docs/interpreter/`. Follow the Markdown style as this [example](https://github.com/apache/zeppelin/blob/master/docs/interpreter/elasticsearch.md). Make sure you list config settings and provide working examples on using your interpreter in code boxes in Markdown. Link to images as appropriate (images should go to `docs/assets/themes/zeppelin/img/docs-img/`). And add a link to your documentation in the navigation menu (`docs/_includes/themes/zeppelin/_navigation.html`).
  - Most importantly, ensure licenses of the transitive closure of all dependencies are list in [license file](https://github.com/apache/zeppelin/blob/master/zeppelin-distribution/src/bin_license/LICENSE).
  - Commit your changes and open a [Pull Request](https://github.com/apache/zeppelin/pulls) on the project [Mirror on GitHub](https://github.com/apache/zeppelin); check to make sure Travis CI build is passing.
- 

zeppelin-web/README.md

@@ -61,4 +61,4 @@ also try to add proxy info  to npm install command:
 and retry to build again.
 
 ## Contribute on Zeppelin Web
-If you wish to help us and contribute to Zeppelin WebApplication, please look at [Zeppelin WebApplication's contribution guideline](CONTRIBUTING.md).
+If you wish to help us and contribute to Zeppelin WebApplication, please look at the overall project [contribution guidelines](https://zeppelin.apache.org/contribution/contributions.html) and the more focused [Zeppelin WebApplication's documentation](https://zeppelin.apache.org/contribution/webapplication.html).