Initial commit

.env.template

@@ -0,0 +1 @@
+REACT_APP_VERSION=$npm_package_version

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+github: [Aichnerc]
+custom: ["https://www.paypal.me/ChristianAichner"]

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+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.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+  - OS: [e.g. iOS]
+  - Browser: [e.g. chrome, safari]
+  - Version: [e.g. 22]
+
+**Smartphone (please complete the following information):**
+  - Device: [e.g. iPhone6]
+  - OS: [e.g. iOS8.1]
+  - Browser: [e.g. stock browser, safari]
+  - Version: [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+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.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/quick_request.md

@@ -0,0 +1,14 @@
+---
+name: Trimmed Feature request
+about: Suggest a quick idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the feature or change you'd like**
+A clear and concise description of what you want to happen.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.gitignore

@@ -0,0 +1,30 @@
+# See https://help.github.com/ignore-files/ for more about ignoring files.
+
+# Dependencies
+/node_modules
+package-lock.json
+
+# Testing
+/coverage
+
+# Production
+/build
+
+# MDB
+mdb*
+
+# Firebase configuration
+src/config/fbConfig.js
+
+# Environment variables
+.env
+
+# All editor configs but vscode
+.editorconfig
+.idea
+
+# Logs
+*.log*
+
+# SPDX-License-Identifier: (EUPL-1.2)
+# Copyright © 2020 Werbeagentur Christian Aichner

.prettierrc

@@ -0,0 +1,7 @@
+{
+  "trailingComma": "es5",
+  "arrowParens": "always",
+  "tabWidth": 2,
+  "useTabs": false,
+  "singleQuote": false
+}

.vscode/extensions.json

@@ -0,0 +1,18 @@
+{
+  "recommendations": [
+    "coenraads.bracket-pair-colorizer-2",
+    "streetsidesoftware.code-spell-checker",
+    "msjsdiag.debugger-for-chrome",
+    "dracula-theme.theme-dracula",
+    "flowtype.flow-for-vscode",
+    "walter-ribeiro.full-react-snippets",
+    "bradgashler.htmltagwrap",
+    "yzhang.markdown-all-in-one",
+    "christian-kohler.npm-intellisense",
+    "christian-kohler.path-intellisense",
+    "esbenp.prettier-vscode",
+    "pmneo.tsimporter",
+    "eg2.vscode-npm-script",
+    "formulahendry.auto-rename-tag"
+  ]
+}

.vscode/settings.json

@@ -0,0 +1,42 @@
+{
+  "editor.fontFamily": "Fira Code, Consolas, 'Courier New', monospace",
+  "editor.fontLigatures": true,
+  "editor.snippetSuggestions": "top",
+  "editor.rulers": [120],
+  "terminal.integrated.fontFamily": "Consolas",
+  "workbench.colorTheme": "Dracula Soft",
+  "cSpell.ignoreWords": [
+    "aichner",
+    "eupl",
+    "mdbreact",
+    "spdx",
+    "werbeagentur",
+    "fontawesome",
+    "fortawesome",
+    "reactjs",
+    "react.js"
+  ],
+  "cSpell.enabledLanguageIds": [
+    "html",
+    "go",
+    "javascript",
+    "javascriptreact",
+    "markdown",
+    "php",
+    "plaintext",
+    "text",
+    "typescript",
+    "typescriptreact",
+    "yml"
+  ],
+  "cSpell.showStatus": true,
+  "cSpell.ignorePaths": ["node_modules"],
+  "cSpell.words": [
+    "browserslist",
+    "homescreen",
+    "precached",
+    "renamer",
+    "webfonts"
+  ],
+  "editor.formatOnSave": true
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,25 @@
+<p align="center">
+  <a href="https://www.aichner-christian.com/" target="_blank" rel="noopener noreferrer">
+    <img src="https://www.aichner-christian.com/img/logo/logo_web.png" alt="Agency Logo" height="150">
+  </a>
+</p>
+
+<h3 align="center">Official code of conflict</h3>
+
+## Table of contents
+- [Conflicts](#conflicts)
+
+## [](#conflicts)Conflicts
+
+Our development effort is a very personal process compared
+to "traditional" ways of developing software. Your code and ideas
+behind it will be carefully reviewed, often resulting in critique and
+criticism. The review will almost always require improvements to the
+code before it can be included. Know that this happens because everyone 
+involved wants to see the best possible solution for the overall success 
+of this project.
+
+As a reviewer of code, please strive to keep things civil and focused on
+the technical issues involved. We are all humans, and frustrations can
+be high on both sides of the process. Try to keep in mind the immortal
+words of Bill and Ted, "Be excellent to each other."

CONTRIBUTING.md

@@ -0,0 +1,51 @@
+<p align="center">
+  <a href="https://www.aichner-christian.com/" target="_blank" rel="noopener noreferrer">
+    <img src="https://www.aichnerc.at/img/logo/logo_web.png" alt="Agency Logo" height="150">
+  </a>
+</p>
+
+<h3 align="center">Agency Contributing Guidelines</h3>
+
+<p align="center">
+  A code of conduct is a set of rules outlining the norms, rules, and responsibilities of, 
+  and or proper practices for, an individual. This applies to all people contributing to this repository in any form.
+</p>
+
+## Table of contents
+- [Table of contents](#table-of-contents)
+- [Commits](#commits)
+- [Pull Requests](#pull-requests)
+- [Coding Style](#coding-style)
+- [Versioning](#versioning)
+- [Creators](#creators)
+
+## [](#commits)Commits
+
+- All commits must be verified. [Learn how to sign commits using GitKraken](https://support.gitkraken.com/git-workflows-and-extensions/commit-signing-with-gpg/).
+- All commit summaries must start with an uppercase letter.
+- All commit summaries must be written in present tense.
+- The commit summary and description are mandatory.
+- All commit descriptions must be written in past tense.
+- The commit headline must have a maximum of `71 chars`.
+- The commit message must have a maximum of `71 chars per line`.
+- If possible, include link to online topic as reference `Ref: `.
+- The purpose of the commit and your intentions behind it must be clear.
+- Include references to issues if applicable.
+- No commit, under no circumstances, should be pushed to master directly.
+- Each commit should only serve one distinct purpose.
+
+## [](#pull-requests)Pull Requests
+
+- Each pull request should only follow one general topic.
+- You must follow the template for creating a pull request.
+- Each pull request must have at least one assigned developer.
+- Each pull request must have a label. If issues are present, it has to include those at a minimum.
+- Each pull request should be merged by a reviewer.
+- Each pull request has to pass all checks and reviews before merging.
+- Each pull request should include linked issues. Although it is not mandatory, it helps to track the thoughts of the developers and is therefore strongly advised.
+
+## [](#versioning)Versioning
+
+- Each merge of a branch to master should have a suitable change in the version if applicable.
+- Each change in version has to be documented with the creation of a new release, including a changelog.
+- Always use semantic versioning. (Major, Minor, Patch) See <https://semver.org/> for more information.