README and infrastructure changed, small fixes

Author: Gesugao-san

.gitattributes

@@ -0,0 +1,17 @@
+
+* text=auto
+
+## Enforce text mode and CRLF line breaks
+*.editorconfig  text eol=crlf
+*.gitattributes text eol=crlf
+*.gitignore     text eol=crlf
+*.htm           text eol=crlf
+*.html          text eol=crlf
+*.json          text eol=crlf
+*.log           text eol=crlf
+*.md            text eol=crlf
+*.txt           text eol=crlf
+*.yaml          text eol=crlf
+*.yml           text eol=crlf
+CODEOWNERS      text eol=crlf
+LICENSE         text eol=crlf

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+
+#* @Gesugao-san

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,79 @@
+
+# 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 byond.libraries@gmail.com. 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 http://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+For answers to common questions about this code of conduct, see
+http://www.contributor-covenant.org/faq
+
+---
+
+[homepage]: http://www.contributor-covenant.org

.github/CONTRIBUTING.md

@@ -0,0 +1,31 @@
+
+# CONTRIBUTING
+
+[Back]
+
+> Guide to contributing to [Expectatives/Discord.js-v13-Example](http://github.com/Expectatives/Discord.js-v13-Example) repo.
+
+### Table of content
+- [CONTRIBUTING](#contributing)
+		- [Table of content](#table-of-content)
+	- [Pull Request Process](#pull-request-process)
+	- [Banned content](#banned-content)
+
+## Pull Request Process
+
+There is no strict process when it comes to merging pull requests. Pull requests will sometimes take a while before they are looked at by a maintainer; the bigger the change, the more time it will take before they are accepted.
+
+Please feel free to:
+ * fix mistakes through a [Pull Requests (PR is short)].
+
+## Banned content
+
+Do not add any of the following in a Pull Request or risk getting the PR closed:
+
+* Code which violates GitHub's [Terms of Service (ToS is short)].
+
+---
+
+[Back]: ../README.md
+[Pull Requests (PR is short)]: http://github.com/Expectatives/Discord.js-v13-Example/pulls
+[Terms of Service (ToS is short)]: http://github.com/site/terms

.github/DOWNLOAD.md

@@ -0,0 +1,41 @@
+
+# DOWNLOADING
+
+[Back]
+
+> Guide to download from [Expectatives/Discord.js-v13-Example] repo.
+
+### Table of content
+- [DOWNLOADING](#downloading)
+		- [Table of content](#table-of-content)
+	- [Browser](#browser)
+	- [git bash](#git-bash)
+
+## Browser
+
+Download the source code as a zip by clicking the ZIP button in the code tab of http://github.com/Expectatives/Discord.js-v13-Example (note: this will use a lot of bandwidth if you wish to update and is a lot of hassle if you want to make any changes at all, so it's not recommended)
+
+![Browser download]
+
+For more info check [official Github guide], please.
+
+## git bash
+
+You can use any Git client to "clone" the repository, downloading a copy to your machine. You can also use Git to "pull", which updates your copy to match recent changes.
+
+```shell
+$ git clone http://github.com/Expectatives/Discord.js-v13-Example
+```
+
+![Mintty download]
+
+For more info check [official Github guide], please.
+
+---
+
+[Back]: ../README.md
+[Expectatives/Discord.js-v13-Example]: http://github.com/Expectatives/Discord.js-v13-Example
+[Browser download]: /.github/static/browser_download.png
+[official Github guide]: http://docs.github.com/en/github/creating-cloning-and-archiving-repositories
+[Mintty download]: /.github/static/mintty_download.png
+[official Github guide]: http://docs.github.com/en/github/creating-cloning-and-archiving-repositories

.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,27 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,7 @@
+
+**Changes**
+A brief description of the changes.
+
+1. Did X
+2. Tested Y
+3. ...

.github/TODO.md

@@ -0,0 +1,21 @@
+
+# TODO
+
+[Back]
+
+> ToDo list.
+
+### Table of content
+
+- [TODO](#todo)
+		- [Table of content](#table-of-content)
+	- [ToDo table](#todo-table)
+
+## ToDo table
+
+- [ ] ~~Example entry (not marked as done)~~;
+- [x] ~~Example entry (marked as done)~~.
+
+---
+
+[Back]: ../README.md