Added new docs

Author: eldadfux

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers 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, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,74 @@
+# Contributing
+
+We would ❤️ for you to contribute to Appwrite and help make it better! As a contributor, here are the guidelines we would like you to follow:
+
+## Code of Conduct
+
+Help us keep Appwrite open and inclusive. Please read and follow our [Code of Conduct](/CODE_OF_CONDUCT.md).
+
+## Creating Language Class
+
+First, create a new class for the new language in this directory:�https://github.com/appwrite/sdk-generator/tree/master/src/SDK/Language
+
+You can use the interface to know which methods are required and needs to be implemented:
+https://github.com/appwrite/sdk-generator/blob/master/src/SDK/Language.php
+
+**getName**
+SDK Language name (JS, PHP…)
+
+**getKeywords**
+An array with language keywords to avoid using as param or function names, template engine will solve conflicts
+
+**getFiles**
+An array with a list of language template files in [twig format](https://twig.symfony.com/). 
+Each file scope determines what template parameters will be available.
+
+* default scope - Basic SDK and language-specific params (package name, language name, etc…)
+* service scope - Generate x templates where x is the number of API services, adds service-specific params to the template (service name, methods, etc…)
+* method scope - Generate x*y templates where x is the number of API services and y is the number of methods, adds service and method-specific params to the template (service name, method name, method params, etc…), good for generating MD files with examples for using each method
+
+**getTypeName**
+This method receives the API param type and should return the equivalent param in the implemented language.
+
+**getParamDefault**
+This method receives the API param and should return the equivalent default value of param in the implemented language, for example, a default array param in PHP is represented as [].
+
+**getParamExample**
+This method receives the API param and should return the equivalent example value of param in the implemented language, for example, if an example value is **some text** in PHP return value should be **'some text'** (with quotes).
+
+Notice: The easiest way to get started is to copy an existing language class close to the new language about to be implemented and just edit it.
+
+## Adding Templates
+
+Add your new templates as listed in your language class **getFiles** method. Make sure to follow the [checklist](https://github.com/appwrite/sdk-generator#sdk-checklist) when building the language templates.
+
+Make sure to follow the objects structure and service separation architecture. We aim to keep developer experience as consisted as possible across different SDKs to make the learning curve as small as possible.
+
+When in need to test the API templates output, add your new language instance to the example.php file like this:
+
+sdk-generator/blob/master/example.php:
+
+```php
+    use Appwrite\Spec\Swagger2;
+    use Appwrite\SDK\SDK;
+    use Appwrite\SDK\Language\NewLang;
+    
+    // NewLang
+    $sdk  = new SDK(new NewLang(), new Swagger2($spec));
+    $sdk
+        ->setLogo('https://appwrite.io/v1/images/console.png')
+        ->setLicenseContent('test test test')
+        ->setWarning('**WORK IN PROGRESS - NOT READY FOR USAGE**')
+    ;
+    $sdk->generate(__DIR__ . '/examples/new-lang');
+```
+
+Run the following command:
+
+```bash
+php example.php
+```
+
+>Note: Make sure to have PHP CLI installed on your host.
+
+Check your output files at: /examples/new-lang and make sure the SDK works. When possible add some unit tests.