Merge pull request #7 from AminoJS/blogdev

The Blog Update (Version: 0.2)

Author: moelrobi

.DS_Store

@@ -1,3 +1,4 @@
-docs/*
-test/*
-testing.js
+docs/*
+test/*
+testing.js
+examples/*

.eslintignore

@@ -0,0 +1,26 @@
+---
+name: Reporting Bugs
+about: Open an Issue to help us fix Stuff.
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+(Please describe how we could reproduce the Error you encountered)
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Node-Version [e.g. v.8.8.0]
+ - Version [e.g. 2.0, nightly, etc.]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+**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/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,12 @@
+### Your checklist for this pull request
+🚨Please review the [guidelines for contributing](../CONTRIBUTING.md) to this repository.
+
+- [ ] Make sure you are requesting to **pull a topic/feature/bugfix branch** (right side). Don't request your master!
+- [ ] Make sure you are making a pull request against the **latest dev branch** (left side). Also you should start *your branch* off *our latest dev branch*.
+- [ ] Check the commit's or even all commits' message styles matches our requested structure.
+- [ ] Check your code additions will fail neither code linting checks nor unit test.
+
+### Description
+Please describe your pull request.
+
+Thank you!

.github/PULL_REQUEST_TEMPLATE.md

@@ -62,4 +62,13 @@ typings/
 testing.js
 
 #A Testing file for tesing various stuff
-testing.js
+testing.js
+
+# env file for local testing
+env.js
+
+# OSX stuff
+.DS_Store
+
+# Ignore Cache Files for c9-WebIDE
+.c9/

.gitignore

@@ -1,7 +1,13 @@
-cache:
-  directories:
-    - "node_modules"
-
-language: node_js
-node_js:
-  - "8"
+cache:
+  directories:
+    - "node_modules"
+    - "docs"
+    - "examples"
+
+language: node_js
+
+node_js:
+  - "8"
+script:
+  - yarn run lint
+  - yarn run test

.travis.yml

@@ -0,0 +1,74 @@
+# Changelogs
+## v.2.0 (The Blog / Wiki Update)
+"Finally, we can release it." ~Me, or so.
+The Blog / Wiki update gives new functionaly to AminoJS, fixed some bugs, enhances security and handles testcases way differently then v.0.1
+
+Summary:
+* Create, Comment and Delete Different Wiki Entries / Blog Posts. (Restricted to User Online)
+* Fetch Blogs from Community Feed or a Community User.
+* Users can now use AminoJS Safe, because it runs now via HTTPS
+* Testcases, a lot of them.
+* Added Code of Conduct and Issue Templates.
+
+Full Changelog (with PR Refrence):
+[`#6 Make Login more simple`](https://github.com/AminoJS/Amino.JS/pull/6)
+Thanks to [Felix](https://github.com/felixfong227), we don't need to parse in the secret ID, that was required in every function we called.
+
+[`#9 Modulize the Core Libary`](https://github.com/AminoJS/Amino.JS/pull/10)
+Also thanks to [Felix](https://github.com/felixfong227), the entire libary is now seperated in modules, wich makes easier development possible.
+
+[`#12 The Wiki Stuff!`](https://github.com/AminoJS/Amino.JS/pull/12)
+[Robin](https://github.com/moelrobi) then started working on the "Wiki Stuff", with that PR, the Libary started to have Wiki Functionallties. The Libary could, with the PR:  Create, Comment, Delete Wiki Blogs.
+
+[`#25 Fetch User Blogs`](https://github.com/AminoJS/Amino.JS/pull/25)
+[Felipe](https://github.com/akatsukilevi) and [Robin](https://github.com/moelrobi) created the Ability to fetch User Blogs! (Dammmn Daniel! :D)
+
+[`#26 Blog all`](https://github.com/AminoJS/Amino.JS/pull/26)
+Thanks to First-Time Contributor [Tau5](https://github.com/Tau5) AminoJS got all of the Blogs! Thanks from me again!
+
+[`#29 HTTPS!`](https://github.com/AminoJS/Amino.JS/pull/29)
+Woo.. we got that now.
+
+[`#30 & #31 & #32 Repoworks!`]
+[`#30 Create issue Templates!`](https://github.com/AminoJS/Amino.JS/pull/30)
+[`#31 Create Code of Conduct`](https://github.com/AminoJS/Amino.JS/pull/31)
+[`#32 New Testcases!`](https://github.com/AminoJS/Amino.JS/pull/32)
+
+Just some Repowork. New Issue Templates, a Code of Conduct and Testcases for easier Development.
+
+## v.0.1.1
+Updating the NPM Package to be routing to the new Repo.
+Please take a Look at Commit [`d98828f`](https://github.com/AminoJS/Amino.JS/commit/d98828ff184cbb9b4c1fdb788d4ad120d88af598) for more Infomation
+## v.0.1 (The Documentaion Update!):
+The Code was documentated.
+First Official Alpha Release since open-sourcing the Project.
+The Code is now Avaible and Maintend on Github! (https://github.com/AminoJS/Amino.JS)
+Pullrequest is under: (https://gitlab.com/AminoJS/Amino.JS/pull/2)
+Full Changelog with Commit Names:
+[`db28fd1 & 05b6e08`] Switching from gitlab-ci to Travis-Ci.
+[`95180d5`] Added Eslint as a Sutiable Testcase.
+[`6935738`] Removed some Testcases because of Sorter-Rewrite
+[`840c1f2`] Changed the Readme to actually Look Better.
+[`3c489ae`] Added a new Function called getMyProfile which fetches the logged in Profile
+[`4641444`] Added the Docs for the above mentioned Function
+## v.0.0.3:
+A Bug was fixed.
+See: https://gitlab.robsys.space/Kikai/KikaiFramework/issues/2
+## v.0.0.2:
+A major Bugfix was released.
+See https://gitlab.robsys.space/Kikai/KikaiFramework/issues/1
+# v.0.0.1:
+The Client Framework can now do the Following:
+It can Authenticate with the Narvii API.
+It can Load all Communitys that a User is joined.
+It can Load all joined Chats.
+It can send Messages to Specific Chats.
+It can load Messages from Specific Chats.
+### TODO:
+Add Media Support (v.0.0.2 alpha)
+Make the Get Messages Cleaner (v.0.0.2 alpha)
+A lot more...
+
+## indev:
+Initial Commit
+Added a Builder

CHANGELOG

@@ -0,0 +1,46 @@
+# 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, gender identity and expression, level of experience, 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 moelrobi@gmail.com. The project team will review and investigate all complaints, and will respond in a way that it deems 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://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/