.github/FUNDING.yml

@@ -0,0 +1,13 @@
+# These are supported funding model platforms
+
+github: [lukasoppermann]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+otechie: # Replace with a single Otechie username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project-name e.g., cloud-foundry
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+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.
+
+**Test Case**
+Please copy this [codepen](https://codepen.io/pen/?template=GRoQRxo) and create a working test case showing the experienced bug: https://codepen.io/pen/?template=GRoQRxo
+
+**System (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**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: ''
+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/dependabot.yml

@@ -0,0 +1,61 @@
+version: 2
+updates:
+- package-ecosystem: npm
+  directory: "/"
+  schedule:
+    interval: daily
+    time: "04:00"
+  open-pull-requests-limit: 10
+  ignore:
+  - dependency-name: rollup
+    versions:
+    - 2.38.1
+    - 2.39.0
+    - 2.39.1
+    - 2.41.3
+    - 2.41.4
+    - 2.41.5
+    - 2.42.0
+    - 2.42.1
+    - 2.42.2
+    - 2.42.3
+    - 2.42.4
+    - 2.43.0
+    - 2.43.1
+    - 2.44.0
+    - 2.45.0
+    - 2.45.1
+  - dependency-name: eslint
+    versions:
+    - 7.20.0
+    - 7.22.0
+    - 7.23.0
+    - 7.24.0
+  - dependency-name: y18n
+    versions:
+    - 4.0.2
+  - dependency-name: "@typescript-eslint/eslint-plugin"
+    versions:
+    - 4.15.1
+    - 4.15.2
+    - 4.16.0
+    - 4.18.0
+    - 4.19.0
+    - 4.20.0
+    - 4.21.0
+  - dependency-name: "@typescript-eslint/parser"
+    versions:
+    - 4.15.1
+    - 4.15.2
+    - 4.16.0
+    - 4.18.0
+    - 4.19.0
+    - 4.20.0
+    - 4.21.0
+  - dependency-name: "@types/jest"
+    versions:
+    - 26.0.21
+    - 26.0.22
+  - dependency-name: typescript
+    versions:
+    - 4.1.4

.github/workflows/html5sortable.yml

@@ -0,0 +1,34 @@
+name: Build and test 
+
+on: [push, pull_request]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/checkout@v2
+
+    - name: Cache node modules
+      uses: actions/cache@v2
+      env: 
+        cache-name: cache-node-modules
+      with:
+        path: ~/.npm
+        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
+        restore-keys: |
+          ${{ runner.os }}-build-${{ env.cache-name }}-
+          ${{ runner.os }}-build-
+          ${{ runner.os }}-
+
+    - name: Build and test
+      uses: actions/setup-node@v1
+      with:
+        node-version: '14.x'
+    - run: npm ci
+    - run: npm run github-build
+
+    - name: Coveralls
+      uses: coverallsapp/github-action@master
+      with:
+        github-token: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -1,2 +1,2 @@
 node_modules
-bower_components/
+coverage

CODE_OF_CONDUCT.md

@@ -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 lukas@vea.re. 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/

CONTRIBUTING.md

@@ -0,0 +1,98 @@
+# Contributing
+
+We ❤️ contributions, so if you find a bug or have a great idea for a feature create an [issue](https://github.com/lukasoppermann/html5sortable/issues) or even better, send a [pull request](https://github.com/lukasoppermann/html5sortable/pulls).
+
+We are a beginners friendly project! This means, we are happy to help you with contributing to the project. If you are not sure how to make your PR fulfill all the points below, send a [WIP] (work in progress) PR. In the description you can mentioning the points you are still working on and what you need help with.
+
+If you are just starting out with github, you are very welcome to submit small PRs. For example improvements to the readme or code cleanup PRs.
+
+
+## Pull Requests
+
+- We use [standardjs](https://standardjs.com/) to enforce common coding style, so please write your code according to it. (Run `npm test` to see where you need adjust your code.)
+
+- **Add tests!** - To avoid bugs we keep the test coverage as high as possible. Please help by adding tests to your bugfixes & features.
+
+- **Comment your code** - Your code should be as self-documenting and easy to read as possible, however please add comments whenever possible/sensible. People with all levels of skill and involvement in the project will work on the code.
+
+- **Use Docblocks for functions** – Every function should have a [docblock](http://usejsdoc.org/about-getting-started.html) above stating what the function does and what parameters it is supposed to receive, return values, etc.
+
+  ```javascript
+  /*
+  * remove event handlers from sortable
+  * @param: {Element} sortable
+  */
+  ```
+
+- **Document any change in behavior** - Make sure the `README.md` and any other relevant documentation are kept up-to-date.
+
+- **Do NOT commit the dist folder** – Please do not commit anything in the `dist` directory, those files will be updated once a release is created.
+
+- **One pull request per feature** - We appreciate every improvement you have for the project. To make it easy and fast to merge your pull requests, only change one thing per PR. We rather have 10 small PRs than one giant one.
+
+- **Rebase to master**
+Please make sure to [`rebase` to `master`](#rebase-to-master) so that your pull request can be easily merged.
+
+**Remember:** If you have trouble with any of the steps above, just ask for help.
+
+## Running Tests
+
+``` bash
+$ npm test
+```
+
+## Rebase
+
+If you are new to rebasing you might want to create a backup of your branch, in case something goes wrong 😉.
+
+### Rebase to master
+
+#### Track the upstream master
+First you need to track the `upstream/master` (master of this repo) from your fork.
+
+```bash
+git remote add upstream git@github.com:lukasoppermann/html5sortable.git
+```
+
+#### Rebase to the upstream master
+Before you send a PR, or whenever you need to get changes from the upstream master into your branch, you need to do the following:
+
+```bash
+# get the latest changes from upstream
+git fetch upstream
+# go to your branch if you are not already on it
+git checkout your-branch
+# move your changes ontop of the current upstream/master branch
+git rebase upstream/master
+```
+
+If you are unlucky you might get a conflict. You will need to resolve it just like a merge conflict.
+
+### Interactive rebase
+It is nice to try to send only meaningful commits, as this makes it easier for us to understand what you where doing. However when working one often has commits like `fix` or `update`.
+
+To remove those and create an easy to understand history you can use `git rebase -i` – an interactive `-i` rebase.
+
+```bash
+# to work on the last 3 commits
+git rebase -i HEAD~3
+# to work on all commits up to 34kl24314
+git rebase -i 34kl24314
+```
+
+First you will get an overview of your commits:
+
+```bash
+pick ae23f76 update contribution
+pick 41c2535 update contribute
+```
+
+You can `pick` (keep), `reword` (keep & edit message), `edit`, `squash` (meld into the previous (shown) commit), `fixup` (like squash but without commit message), `exec` or `drop` (remove commit). Those options are listen as comments below the commits in your overview screen. You can also reorder commit to change the order in which they are shown.
+
+**Note:** This screen is read from bottom to top, so for e.g. `squash` will meld into the commit above.
+
+Once you are happy with you changes, save and close the file to move on. Another file with all commit messages is shown. Remove the ones you don't want and save and close this file as well. Your rebase should continue and you should be down.
+
+**Note:** As you rewrote history, you will now need to force-push if you changed commits that are already on a remote server.
+
+**Happy coding!**