Forien
diff --git a/‎.editorconfig
+315 b/‎.editorconfig
+315
diff --git a/‎.eslintignore
+7 b/‎.eslintignore
+7
diff --git a/‎.eslintrc
+40 b/‎.eslintrc
+40
diff --git a/‎.gitattributes
+1 b/‎.gitattributes
+1
diff --git a/‎.github/workflows/main.yml
+41 b/‎.github/workflows/main.yml
+41
diff --git a/‎.github/workflows/release.yml ‎.github/workflows/release.yml.bak b/‎.github/workflows/release.yml ‎.github/workflows/release.yml.bak
diff --git a/‎.gitignore
+2-4 b/‎.gitignore
+2-4
diff --git a/‎AUTHORS
+26 b/‎AUTHORS
+26
diff --git a/‎CONTRIBUTING.md
+46 b/‎CONTRIBUTING.md
+46
diff --git a/‎LICENSE
+21 b/‎LICENSE
+21
@@ -0,0 +1,7 @@
+.github/
+docs/
+external/
+lang/
+scripts/
+styles/
+templates/
@@ -0,0 +1,40 @@
+/**
+ * Loads https://github.com/typhonjs-node-config/typhonjs-config-eslint/blob/master/3.0/basic/es8/server/node/.eslintrc
+ * Loads https://github.com/typhonjs-fvtt/eslint-config-foundry.js/blob/main/0.8.0.js
+ *
+ * NPM: https://www.npmjs.com/package/typhonjs-config-eslint
+ * NPM: https://www.npmjs.com/package/@typhonjs-fvtt/eslint-config-foundry.js
+ */
+{
+  // ESLint configs are prone to particular choices, so if the first config below doesn't work for you then replace
+  // with one that you do prefer. The second config defines globals defined in `foundry.js` for use w/ `no-shadow`.
+  "extends": [
+    "@typhonjs-config/eslint-config/esm/2022/browser",
+    "@typhonjs-fvtt/eslint-config-foundry.js"
+  ],
+
+  // Defines / overrides a few more environment parameters not provided in the configs above.
+  "env": {
+    "jquery": true
+  },
+
+  // Prevents overwriting any built in globals particularly from `@typhonjs-fvtt/eslint-config-foundry.js`, but also
+  // node & browser environments. `event / window.event` shadowing is allowed due to being a common variable name and
+  // an uncommonly used browser feature.
+  //
+  // Note: if you are using Typescript you must use `@typescript-eslint/no-shadow`
+  "rules": {
+    "no-shadow": ["error", {
+      "builtinGlobals": true,
+      "hoist": "all",
+      "allow": [
+        "document",
+        "event",
+        "name",
+        "parent",
+        "status",
+        "top"
+      ]
+    }]
+  }
+}
@@ -0,0 +1 @@
+packs/** binary
@@ -0,0 +1,41 @@
+# From https://github.com/League-of-Foundry-Developers/FoundryVTT-Module-Template/blob/master/.github/workflows/main.yml
+name: Release Creation
+
+on:
+  release:
+    types: [published]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+
+      # Substitute the Manifest and Download URLs in the module.json
+      - name: Substitute Manifest and Download Links For Versioned Ones
+        id: sub_manifest_link_version
+        uses: microsoft/variable-substitution@v1
+        with:
+          files: 'module.json'
+        env:
+          version: ${{github.event.release.tag_name}}
+          url: https://github.com/${{github.repository}}
+          manifest: https://github.com/${{github.repository}}/releases/latest/download/module.json
+          download: https://github.com/${{github.repository}}/releases/download/${{github.event.release.tag_name}}/module.zip
+
+      # Create a zip file with all files required by the module to add to the release
+      - run: zip -r ./module.zip module.json assets/ css/ database/ external/ lang/ packs/ scripts/ src/ styles/ templates/ LICENSE AUTHORS
+
+      # Create a release for this specific version
+      - name: Update Release with Files
+        id: create_version_release
+        uses: ncipollo/release-action@v1
+        with:
+          allowUpdates: true # Set this to false if you want to prevent updating existing releases
+          name: ${{ github.event.release.name }}
+          draft: false
+          prerelease: false
+          token: ${{ secrets.GITHUB_TOKEN }}
+          artifacts: './module.json, ./module.zip'
+          tag: ${{ github.event.release.tag_name }}
+          body: ${{ github.event.release.body }}
@@ -1,8 +1,6 @@
 .idea/
-styles/.sass-cache/
-devtool/
+docs/
 lang/untranslated.json
 node_modules/
 foundry.js
-package.json
-/changelog.html
+package-lock.json
@@ -0,0 +1,26 @@
+# This is the official list of foundryvtt-forien-quest-log authors for copyright purposes.
+#
+# This does not necessarily list everyone who has contributed code, since in
+# some cases, their employer may be the copyright holder. To see the full list
+# of contributors, see the revision history in source control or
+# https://github.com/League-of-Foundry-Developers/foundryvtt-forien-quest-log/graphs/contributors.
+#
+# Authors who wish to be recognized in this file should add themselves (or
+# their employer, as appropriate).
+
+4535992 <5201916+p4535992@users.noreply.github.com>
+BrotherSharp <41280723+BrotherSharper@users.noreply.github.com>
+Dilomos <49794325+Dilomos@users.noreply.github.com>
+Eadorin <eadorin@gmail.com>
+eclarke12 <42503461+eclarke12@users.noreply.github.com>
+innocenti <renato.innocenti@gmail.com>
+JJBocanegra <5797636+JJBocanegra@users.noreply.github.com>
+klo <drdwing@gmail.com>
+Lyndsey Toft <toftl@rpi.edu>
+Michael Leahy <support@typhonjs.io>
+Rughalt <802214+Rughalt@users.noreply.github.com>
+Sad <23254376+zeteticl@users.noreply.github.com>
+sdenec <8881200+sdenec@users.noreply.github.com>
+Wojciech "Forien" Szulc <mr.forien@gmail.com>
+xdy <246024+xdy@users.noreply.github.com>
+Fallayn <fallayn@users.noreply.github.com>
@@ -0,0 +1,46 @@
+## Contribution Etiquette
+Open Source projects function most efficiently when everyone communicates well with each other. Here are some suggested practices that will let everyone else work alongside you comfortably:
+
+### **Did you find a bug? Do you want to suggest an enhancement?**
+
+* **Ensure your contribution is novel** by searching the [Issues](https://github.com/League-of-Foundry-Developers/foundryvtt-forien-quest-log/issues) page. Be sure to look through both open and closed issues, especially for enhancement suggestions as rejected suggestions will be closed.
+
+* If applicable **use the appropriate issue templates** to automatically apply the relevant tag to the created issue. This allows issues to be quickly differentiated as bug reports, enhancement suggestions, or whatever else without a maintainer manually adding the tag to the issue. The bug report template will specify which information to add that will aid in reproducing the bug.
+
+* Inconsequential fixes regarding typos, whitespace, etc. may not warrant an issue and can skip straight to the Pull Request.
+
+### **Do you want to fix a currently existing issue?**
+
+* Before working on an issue please **honor issue assignments** and ask to be assigned to the issue in a comment on the issue page. This allows everyone else to see that someone is working on the issue preventing any duplicate pull requests down the line. If someone is already assigned to the issue feel free to reach out to the assignee and inquire on the progress of that fix.
+
+* While working on an issue **document your changes** by providing detailed commit messages and providing an overview of planned / current implementation / changes on the issue page. 
+
+* When you feel your fork adequately fixes an issue, **submit a pull request for review**! [Please indicate which issue is to be closed if the PR is merged](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) as well as giving a detailed overview of your changes. 
+
+* Please **limit the content of your pull requests to its linked issues**. If your pull request does anything additional you must first open an issue that your PR may close (see the below section).
+
+### **Do you intend to add a new feature or change an existing one?**
+
+* Please **open an issue** to generate feedback on the change first. The maintainers reserve the right to reject changes / additions that they do not want to maintain, so be sure that the maintainers are on the same page as you to avoid wasted work!
+
+* Now that an issue covers the changes you wanted to make refer to the above section for implementing the changes.
+
+### **Do you want to submit/update a translation?**
+
+* **Submit a pull request** with your new / updated JSON file in the [lang folder](https://github.com/League-of-Foundry-Developers/foundryvtt-forien-quest-log/tree/master/lang).
+
+* Be sure that the JSON file is either completely flat or completely nested.
+
+* If your localization does not include translations for any strings please indicate as much in the [lang / missing folder](https://github.com/League-of-Foundry-Developers/foundryvtt-forien-quest-log/tree/master/lang/missing).
+
+### **Do you want to contribute documentation?**
+
+* Please **follow the above guidelines** regarding opening issues and submitting pull requests. Some documentation issues may be broader and ongoing, in which case you may want to contribute to assignee's forks first. Any smaller changes should still open a detailed issue and submit a detailed pull request that [closes that issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).
+
+### **Do you have questions about the source code?**
+
+* **Join the [TyphonJS Discord](https://discord.gg/mnbgN8f)** and direct questions to the appropriate channel (#forien-quest-log).
+
+* Please **do not directly contact maintainers** with questions; if you have a question other people might as well, so discussions should take place in public forums where others can see and learn from it as well.
+
+Thank you for your interest in contributing to Forien's Quest Log! :heart:
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2020-2021 Wojciech "Forien" Szulc, AUTHORS
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.