docs: add contributing guidelines

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: 'Bug: '
+labels: ''
+assignees: ''
+
+---
+
+<!--- Please provide a short description of the bug -->
+<!--- Please follow the naming conventions -->
+
+### Description
+<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
+
+### Expected Behavior
+<!--- Tell us what should happen -->
+
+### Actual Behavior
+<!--- Tell us what happens instead -->
+
+### Possible Fix
+<!--- Not obligatory, but suggest a fix or reason for the bug -->
+
+### Steps to Reproduce
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+
+### Context
+<!--- How has this bug affected you? What were you trying to accomplish? -->
+
+### Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+* Version used:
+* System type: <!--- eg VPS, Bare metal -->
+* Operating System and version:
+* System specs:

.github/ISSUE_TEMPLATE/change-request.md

@@ -0,0 +1,20 @@
+---
+name: Change request
+about: Propose a change
+title: 'Change: '
+labels: ''
+assignees: ''
+
+---
+
+<!--- Please provide a short description in the title above -->
+<!--- Please follow the naming conventions -->
+
+### Description
+<!--- Provide a more detailed introduction to the request itself, and why you consider to change it -->
+
+### Actual status
+<!--- Tell us what happens now -->
+
+### Expected status
+<!--- Tell us what should happen -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: HydraDX Community Support
+    url: https://discord.gg/T8HfDP6d83
+    about: Please ask and answer questions here.

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,21 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: 'Feature: '
+labels: ''
+assignees: ''
+
+---
+
+<!--- Please provide a short description in the title above -->
+<!--- Please follow the naming conventions -->
+
+### Detailed Description
+<!--- Provide a detailed description of the change or addition you are proposing -->
+
+### Context
+<!--- Why is this change important to you? How would you use it? -->
+<!--- How can it benefit other users? -->
+
+### Possible Implementation
+<!--- Not obligatory, but suggest an idea for implementing addition or change -->

.github/ISSUE_TEMPLATE/improvement.md

@@ -0,0 +1,21 @@
+---
+name: Improvement
+about: Propose an improvement
+title: 'Improve: '
+labels: ''
+assignees: ''
+
+---
+
+<!--- Please provide a short description in the title above -->
+<!--- Please follow the naming conventions -->
+
+### Detailed Description
+<!--- Provide a detailed description of the improvement you are proposing -->
+
+### Context
+<!--- Why is this improvement important to you? -->
+<!--- How can it benefit other users? -->
+
+### Possible Implementation
+<!--- Not obligatory, but suggest an idea for implementing this improvement -->

.github/ISSUE_TEMPLATE/refactor.md

@@ -0,0 +1,20 @@
+---
+name: Refactor
+about: Describe need for a refactor
+title: 'Refactor: '
+labels: ''
+assignees: ''
+
+---
+
+<!--- Please provide a short description in the title above -->
+<!--- Please follow the naming conventions -->
+
+### Description
+<!--- Provide a more detailed introduction to the problem itself, and why you consider there is a need to refactor this -->
+
+### Actual solution
+<!--- Tell us what you are changing, possibly link to an issue or comment -->
+
+### Expected solution
+<!--- Tell us what should happen when this changes -->

.github/pull_request_template.md

@@ -0,0 +1,28 @@
+<!--- Provide a general summary of your changes in the Title above -->
+<!--- We are using semantinc pull request to make our lives easier -->
+<!--- Please use prefixes for the title and use ! before : if breaking like below -->
+<!--- build: ci: docs: feat: perf: refactor: fix: style: test: refactor!: -->
+
+## Description
+<!--- Describe your changes in detail -->
+
+## Related Issue
+<!--- This project only accepts pull requests related to open issues -->
+<!--- If suggesting a new feature or change, please discuss it in an issue first -->
+<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
+<!--- Please link to the issue below using keyword like: Fixes: #0 -->
+
+## Motivation and Context
+<!--- Why is this change required? What problem does it solve? -->
+
+## How Has This Been Tested?
+<!--- Please describe in detail how you tested your changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Checklist:
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- [ ] I have updated the documentation if necessary.
+- [ ] I have added tests to cover my changes, regression test if fixing an issue.
+- [ ] This is a breaking change.

README.md

@@ -2,6 +2,11 @@
 
 CROSS-CHAIN LIQUIDITY PROTOCOL BUILT ON SUBSTRATE
 
+## Contributions & Code of Conduct
+
+Please follow the contributions guidelines as outlined in [`docs/CONTRIBUTING.md`](docs/CONTRIBUTING.md).
+We are welcoming and friendly community please follow our [Code of Conduct](docs/CODE_OF_CONDUCT.md).
+
 ## Local Development
 
 Follow these steps to prepare a local Substrate development environment :hammer_and_wrench:

docs/CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+
+# HydraDX Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations