Add CONTRIBUTING.md, issue and pr templates (#190)

* Add issue and pull request templates, and created contributing guidelines
* Added build instructions
* Improved the comments and added the Documentation type of change

Author: monesidn

.github/ISSUE_TEMPLATE/01-bug-report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Report something that is not working as expected
+title: ""
+labels: ""
+assignees: ""
+---
+
+### What is the expected and actual behavior?
+
+The library should do XXX but it's instead doing YYY
+
+### Platform details
+
+<!--
+Please provide as much information as possible here about the environment where you experinced the issue.
+Delete any row that doesn't apply to your issue.
+-->
+
+I'm running the application in
+
+- A Browser: _Example: chrome, firefox, edge..._
+- Node: _Example: v22.14.0_
+- Other: _Example: Deno..._
+
+I'm using:
+
+- Typescript
+- Babel
+- ESBuild
+- TSC
+- Other
+
+### How to replicate the issue?
+
+<!-- Please be specific as possible. Use dashes (-) or numbers (1.) to create a list of steps. If possible provide a code snippet or a link to a repo where the problem can be reproduced. -->
+
+### Other Comments

.github/ISSUE_TEMPLATE/02-feature-request.md

@@ -0,0 +1,27 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ""
+labels: ""
+assignees: ""
+---
+
+## Feature Request
+
+<!-- Thank you for taking the time to suggest a feature for our library! Please fill out the following details to help us understand your request better. -->
+
+### Is your feature request related to a problem? Please describe.
+
+<!-- A clear and concise description of the problem. Example: "I'm frustrated when..." -->
+
+### Describe the solution you'd like to see implemented
+
+<!-- A clear and concise description of what you want to happen. -->
+
+### Describe any alternative you've considered
+
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+### Additional context
+
+<!-- Add any other context, screenshots, or code examples about the feature request here. -->

.github/ISSUE_TEMPLATE/03-support-request.md

@@ -0,0 +1,19 @@
+---
+name: Support request
+about: Ask for help with a problem that is hard to solve
+title: ""
+labels: ""
+assignees: ""
+---
+
+### Problem description
+
+<!-- Please provide a clear and concise description of the issue or question you need help with. -->
+
+## Steps to Reproduce/Minimal example
+
+<!-- If applicable, list the steps to reproduce the issue:  -->
+
+1.
+2.
+3.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,30 @@
+### Description
+
+<!-- Please include a summary of the changes and the related issue. Highlight any key points or decisions made. -->
+
+Fixes #(issue1)
+
+### Type of Change
+
+-   [ ] Bug fix (non-breaking change which fixes an issue)
+-   [ ] New feature (non-breaking change which adds functionality)
+-   [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+-   [ ] Documentation
+
+### Checklist
+
+<!-- Please remove any step that doesn't apply. You can remove the section entirely if not relevant  -->
+
+-   [ ] My code follows the style guidelines of this project.
+-   [ ] I have performed a self-review of my code.
+-   [ ] I have commented my code, particularly in hard-to-understand areas.
+-   [ ] I have added tests that prove my fix is effective or that my feature works.
+-   [ ] New and existing unit tests pass locally with my changes.
+
+### Screenshots (if applicable)
+
+<!-- Add screenshots to help explain your changes. You can remove the section entirely if not relevant -->
+
+### Additional Notes
+
+<!-- Include any other relevant information or context. You can remove the section entirely if not relevant  -->

CONTRIBUTING.md

@@ -0,0 +1,38 @@
+# Contributing to Serializr
+
+Thank you for considering contributing to Serializr! Please follow these guidelines to ensure a smooth contribution process.
+
+## Guidelines
+
+1. **Create an Issue First**  
+   Before creating a pull request (PR), please open an issue to discuss your proposed changes.
+
+2. **Use Yarn**  
+   This project uses `yarn` for dependency management. Please ensure you use `yarn` instead of `npm`.
+
+3. **Include Unit Tests**  
+   Any PR must include relevant unit tests to ensure the stability of the project.
+
+4. **Lint Your Code**  
+   Use `eslint` to check your code and resolve any suggestions or errors before submitting your PR. We suggest integrating `eslint` directly into your IDE for a seamless development experience.
+
+5. **Format with Prettier**  
+   Use `prettier` to ensure consistent code formatting across the project. We also recommend setting up `prettier` in your IDE to automatically format your code.
+
+6. **Search Existing Issues**  
+   Before opening a new issue, please search the existing issues to avoid duplicates.
+
+## Setting up the environment
+
+At the moment to setup your working environment you must do the following steps:
+
+-   `yarn`
+-   `yarn build`
+
+Once this is done you will be able to run automated tests with
+
+-   `yarn test`
+
+**NOTE:** if you accidentally run `npm install` please revert any change it introduces. It is a known issue that running `npm install` corrupts the dependency tree
+
+We appreciate your contributions and look forward to collaborating with you!