3.00

.gitattributes

@@ -0,0 +1,27 @@
+###################################################################
+## Example Gitattributes File 
+## Containing some Default Configurations
+###################################################################
+
+# Set default behaviour, in case users don't have core.autocrlf set.
+* text=auto
+
+# Explicitly declare text files we want to always be normalized and converted 
+# to native line endings on checkout.
+*.php text eol=lf
+*.sql text eol=lf
+*.htm text eol=lf
+*.html text eol=lf
+*.js text eol=lf
+*.css text eol=lf
+*.lang text eol=lf
+*.txt text eol=lf
+*.md text eol=lf
+*.bat text eol=lf
+
+# Denote all files that are truly binary and should not be modified.
+*.ico binary
+*.png binary
+*.jpg binary
+*.odt binary
+*.odf binary

.github/CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing
+
+Follow these guidelines if you'd like to contribute to the project!
+
+---
+
+## Table of contents
+
+Read through these guidelines before you get started:
+
+1. [Questions & Concerns](#questions--concerns)
+2. [Issues & Bugs](#issues--bugs)
+3. [Feature Requests](#feature-requests)
+4. [Submitting Pull Requests](#submitting-pull-requests)
+5. [Code Style](#code-style)
+
+## Questions & concerns
+
+If you have any questions about using or developing for this project, reach out to @bugfishtm.
+
+## Issues & bugs
+
+Submit an issue or pull request with a fix if you find any bugs in
+the project. When submitting an issue or pull request, make sure you're as detailed as possible and fill in all answers to questions asked in the templates. For example, an issue that simply states "X/Y/Z isn't working!" will be closed.
+
+## Feature requests
+
+Submit an issue to request a new feature. Features fall into one of two
+categories:
+
+1. **Major**: Major changes should be discussed via email. I'm
+   always open to suggestions and will get back to you as soon as I can!
+2. **Minor**: A minor feature can simply be added via a pull request.
+
+## Submitting pull requests
+
+Before you do anything, make sure you check the current list of pull requests 
+to ensure you aren't duplicating anyone's work. Then, do the following:
+
+1. Fork the repository and make your changes in a git branch: `git checkout -b my-branch base-branch`
+2. Read and follow the code style guidelines.
+3. Make sure your feature or fix doesn't break the project! Test thoroughly.
+4. Commit your changes, and be sure to leave a detailed commit message.
+5. Push your branch to your forked repo on GitHub: `git push origin my-branch`
+6. Submit a pull request and hold tight!
+7. If any changes are requested by the project maintainers, make them and follow this process again until the changes are merged in.
+
+## Code style
+
+Please mark your changes by comments inside the code structure.

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+custom: https://paypal.me/bugfish
+patreon: bugfish

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,26 @@
+# Submit a feature request or bug report
+
+Before you submit an issue, check to see if it has already been reported!  
+Any questions should be directed to @bugfishtm.
+
+---
+
+
+## Information
+
+- Operating System: X
+- Browser: X
+- Software Version: X
+- Software Build: X
+
+## Description
+
+Include screenshots if possible and describe the issue you have or the feature you want to add. If you are adding a bug report, try to add upper information like software version and operating system, so we can better understand your issue. This is a general issue template, in some repositories some requested information may not be necessary or required.
+
+## Steps to reproduce
+
+Add steps if possible to reproduce your issue, that the support can better understand whats going on.
+
+## Other relevant information
+
+Add any other relevant information about this issue.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,32 @@
+# Submit a pull request
+
+Thank you for submitting a pull request! To speed up the review process, please ensure that everything below
+is true:
+
+1. This is not a duplicate of an existing pull request.
+2. No existing features have been broken without good reason.
+3. Your commit messages are detailed.
+4. The code style guidelines have been followed.
+5. Documentation has been updated to reflect your changes.
+6. Tests have been added or updated to reflect your changes.
+7. All tests have passed.
+
+Any questions should be directed to @bugfishtm.
+
+---
+
+## Pull request details
+
+Provide details about your pull request and what it adds, fixes, or changes.
+
+## Breaking changes
+
+Describe what features are broken by this pull request and why, if any.
+
+## Issues fixed
+
+Enter the issue numbers resolved by this pull request below, if any.
+
+## Other relevant information
+
+Provide any other important details below.

.gitignore

@@ -0,0 +1,6 @@
+###################################################################
+## Example Gitignore File 
+## To ignore HTAccess Files
+###################################################################
+
+**/.htaccess*

CHANGELOG.md

@@ -0,0 +1,3 @@
+# Changelog
+
+See inside the _changelogs Folder inside this repository to get Changelog Informations between versions.

CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing
+
+Follow these guidelines if you'd like to contribute to the project!
+
+---
+
+## Table of contents
+
+Read through these guidelines before you get started:
+
+1. [Questions & Concerns](#questions--concerns)
+2. [Issues & Bugs](#issues--bugs)
+3. [Feature Requests](#feature-requests)
+4. [Submitting Pull Requests](#submitting-pull-requests)
+5. [Code Style](#code-style)
+
+## Questions & concerns
+
+If you have any questions about using or developing for this project, reach out to @bugfishtm.
+
+## Issues & bugs
+
+Submit an issue or pull request with a fix if you find any bugs in
+the project. When submitting an issue or pull request, make sure you're as detailed as possible and fill in all answers to questions asked in the templates. For example, an issue that simply states "X/Y/Z isn't working!" will be closed.
+
+## Feature requests
+
+Submit an issue to request a new feature. Features fall into one of two
+categories:
+
+1. **Major**: Major changes should be discussed via email. I'm
+   always open to suggestions and will get back to you as soon as I can!
+2. **Minor**: A minor feature can simply be added via a pull request.
+
+## Submitting pull requests
+
+Before you do anything, make sure you check the current list of pull requests 
+to ensure you aren't duplicating anyone's work. Then, do the following:
+
+1. Fork the repository and make your changes in a git branch: `git checkout -b my-branch base-branch`
+2. Read and follow the code style guidelines.
+3. Make sure your feature or fix doesn't break the project! Test thoroughly.
+4. Commit your changes, and be sure to leave a detailed commit message.
+5. Push your branch to your forked repo on GitHub: `git push origin my-branch`
+6. Submit a pull request and hold tight!
+7. If any changes are requested by the project maintainers, make them and follow this process again until the changes are merged in.
+
+## Code style
+
+Please mark your changes by comments inside the code structure.