Snippets TOC: added *instructions to contributors*

README.md

@@ -1,6 +1,8 @@
 ![logo](images/PineCoders.png "Pine")
 
-# pine-utils
-Reusable code snippets and tricks & tips to help Pine Script developers.
+# pinecoders/pine-utils
+Reusable Pine Script snippets and tricks & tips to help Pine Script developers.
 
-See our [web site](http://pinecoders.com) for access to our guides and Pine FAQ & Code.
+The [PineCoders web site](http://pinecoders.com) contains links to our [Coding Conventions](http://www.pinecoders.com/coding_conventions/), [Pine FAQ & Code](http://www.pinecoders.com/faq_and_code/) and [Pine Resources](http://www.pinecoders.com/resources/).
+
+[Interested in contributing?](/snippets/#instructions-to-contributors)

snippets/readme.md

@@ -1,10 +1,15 @@
 ![PineCoders](/images/PineCodersLong.png "PineCoders")
 
 <!-- if you need to give space before text to format tabulation use keys &ensp; &emsp; combination-->
-# Snippets
+# Pine Script Snippets 
 
-## Code Snippets for Tradingview Pine Script language:
-Snippets categorized by purpose.
+Welcome to the list of categorized Pine Script snippets available in the PineCoders repo. The snippets are divided in thematic categories. A snippet can be either a function, a piece of code implementing a particular technique, or variable definitions.
+
+**To access a snippet, just click on its name.**
+
+> [Interested in contributing?](#instructions-to-contributors)
+
+## Snippets by category
 <!--  -->
 
 <!-- ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• -->
@@ -157,3 +162,35 @@ Snippets categorized by purpose.
 </details>
 
 </details>
+
+
+<br>
+
+## Instructions to contributors
+
+First of all, **thank you!** &#128150;&ensp; We hope this repo becomes the de facto reference for reusable Pine code, and this will only happen with contributions like yours.
+
+You can contribute in three ways:
+
+1. Do everything yourself:
+    - Fork the repo.
+    - Use the supplied snippet templates to format each of your snippet.
+    - Add snippet to an existing category or in the `uncategorized` category.
+    - Issue a PR.
+1. Supply the code through GitHub without formatting your snippet:
+    - Fork the repo.
+    - Add your code in the `uncategorized` category.
+    - Issue a PR.
+1. If you are not familiar with GitHub, you can just send your code in a text file to pinecoders@gmail.com. You can use the supplied templates to format your code, but it's not mandatory.
+
+We will revise and, if required, edit contributions to ensure they meet our publications standards. We will get in touch with you if we have questions.
+
+### Notes
+- Authors are recognized in each snippet.
+- No coding conventions are mandatory. It's more important to share than to have uniform code. If you are interested in following a standard, use the [PineCoders Coding Conventions](http://www.pinecoders.com/coding_conventions).
+- Since the repo's code is meant to be used by Pine coders of all skill levels, care should be taken to document assumptions and proper use of your snippets. The example section in each snippet is often the best way to achieve that.
+- Templates are in the `snippets/templates` directory. There is one template for each type of snippet: *function*, *technique* and *variable*.
+- Formatting inside the templates is a mix of [Markdown](https://github.com/adam-p/markdown-here/wiki) and HTML.
+- Version 4 code is preferred. The templates allow for multiple versions of your snippets.
+
+**[Back to top](#pine-script-snippets)**