init

.eslintrc.js

@@ -10,8 +10,45 @@ module.exports = {
   parserOptions: {
     parser: 'babel-eslint'
   },
+  plugins: [
+    'only-warn'
+  ],
   rules: {
-    'no-console': process.env.NODE_ENV === 'production' ? 'error' : 'off',
-    'no-debugger': process.env.NODE_ENV === 'production' ? 'error' : 'off'
+    'no-console': 'off',
+    'no-debugger': 'off',
+    'brace-style': [2, 'stroustrup', { allowSingleLine: true }],
+    'vue/valid-v-on': 'warn',
+    'vue/no-side-effects-in-computed-properties': 'warn',
+    'vue/no-unused-components': 'warn',
+    'vue/valid-v-for': 'warn',
+    'no-use-before-define': 'warn',
+    'new-cap': 'warn',
+    'no-undef': 'warn',
+    'no-tabs': 'off',
+    'import/first': 'off',
+    'no-unused-vars': 'off',
+    'eol-last': 'off',
+    'quote-props': 'off',
+    'standard/no-callback-literal': 'off',
+    'no-template-curly-in-string': 'off',
+    'prefer-promise-reject-errors': 'off',
+    'no-return-await': 'off',
+    'prefer-const': 'off',
+    'no-multiple-empty-lines': 'warn',
+    'no-trailing-spaces': 'warn',
+    'handle-callback-err': 'warn',
+    'import/no-webpack-loader-syntax': 'warn',
+    'no-mixed-operators': 'warn',
+    'no-useless-catch': 'warn',
+    'no-useless-escape': 'warn',
+    'no-return-assign': 'warn',
+    'operator-linebreak': 'warn',
+    'camelcase': 'warn',
+    'no-global-assign': 'warn',
+    'comma-dangle': 'warn',
+    'padded-blocks': 'warn',
+    'space-before-function-paren': 'warn',
+    'indent': 'warn',
+    'no-unreachable': 'warn'
   }
 }

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,11 @@
+---
+name: Feature request
+about: Suggest a feature or improvement idea for the app
+---
+<!-- 
+STEP 1: Before creating a new issue, check out the pinned issue called "improvements in development" and make sure your feature request is not already on the list.
+STEP 2: Make sure the issue title looks consistent with titles of other issues and starts with: [Feature request]
+STEP 3: Describe your feature request below
+-->
+
+## Feature request:

.github/ISSUE_TEMPLATE/Problem_report.md

@@ -0,0 +1,15 @@
+---
+name: Problem report
+about: Create a report to help improve the app
+---
+<!-- 
+STEP 1: make sure the issue title looks like this: [Problem report] YOUR_TITLE
+STEP 2: specify required info in the "Issue details" below
+STEP 3: describe the problem below
+-->
+
+## System info:
+- **App version**: `SPECIFY_VERSION_HERE` <!-- for example: 1.0.0 -->
+- **Operating System**: `SPECIFY_OS_HERE` <!-- for example: x64 | Windows 10 -->
+
+## Problem:

.gitignore

@@ -19,3 +19,6 @@ yarn-error.log*
 *.njsproj
 *.sln
 *.sw?
+
+#Electron-builder output
+/dist_electron

BAKERS.md

@@ -0,0 +1,30 @@
+# Supporters
+
+See the full list of rewards, and join our community on Patreon:
+
+<a target="_blank" href="https://patreon.com/sigma_file_manager">
+  <img
+    src="./.github/media/patreon_button.png"
+    width="164px"
+    style="box-shadow: 0px 6px 24px rgb(255, 66, 77, 0.2); margin: 16px 0"
+  />
+</a>
+
+- Supporters are added to the list from top to bottom. The earlier you start supporting the project, the higher your name will be on the list.
+- "3+ months" supporters will have the ⭐ badge displayed next to their name.
+- The funding will be used for:
+  - Support other open-source and open-content creators (developers, educators, digital artists, etc);
+  - Fund the development of this project;
+  - Fund the development of my other big research project: advanced tools / algorithms that will help scientists speed up development of new medications and treatments for diseases, reducing the time need to find a new medication from 10 years (current average) to just a few months, and hopefully help humanity get rid of diseases;
+
+## SPONSORS - LEVEL 2
+Become the first supporter
+
+## SPONSORS - LEVEL 1
+Become the first supporter
+
+## GENEROUS SUPPORTERS
+Become the first supporter
+
+## GRATEFUL SUPPORTERS
+Become the first supporter

CONTRIBUTING.md

@@ -0,0 +1,39 @@
+# Notes
+
+The app is in early development (prototyping) stage:
+- The codebase hasn't been optimized yet. A large portion of the codebase has been written when I barely knew how to code.
+- The whole codebase will be refactored and optimized in future updates.
+
+# How to contribute
+
+If you want to implement some changes into this project yourself, but you don't know how to do it yet, watch several video tutorials (at least 10) and look up a few "beginner guides to contributing to a GitHub project", then practice working with branches and commiting / pushing changes to your own test repository, make sure you understand what you are doing. When you've done this, you can try to contribute to this project.
+
+## Steps:
+
+1. Create a new issue or a discussion and describe the feature / fix / changes you want to implement.
+2. When you are ready to modify the code, fork the project's repository.
+3. Create a new branch for your feature / fix with a meaningful name:
+```
+git checkout -b my-new-feature-name
+```
+4. Implement your changes into the code.
+5. Check the Github page of your fork and if it says "This branch is X commits behind PROJECT_NAME:main", then pull the changes from the main repository to your forked repository (look up a guide online, like this one: [update-github-repositories-with-changes-by-others](https://www.earthdatascience.org/courses/intro-to-earth-data-science/git-github/github-collaboration/update-github-repositories-with-changes-by-others)).
+6. Make sure there's no conflicts between your changes and the pulled changes. Then commit your changes with a short descriptive message:
+```
+git commit -am "fixed X problem"
+```
+7. Push the commits to your forked repository on Github:
+```
+git push origin my-new-feature-name
+```
+8. Create a new pull request
+
+## Notes:
+
+- Bug fixes should be submitted (pull request) to the main branch.
+
+- New features and breaking changes should be submitted (pull request) to the dev branch.
+
+- Use a descriptive title for the pull request no more than 64 characters long. This will be used as the commit message when your PR is merged, for example: "improved navigator list layout"
+
+- If you are fixing a known problem (specific issue), reference the issue # that the PR resolves at the top of the body of the PR, for example: "Fixes #1234" or "Resolves #6458" (see [closing issues using keywords](https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue))