3 files changed, 66 insertions, 0 deletions
diff --git a/unipdf/.github/ISSUE_TEMPLATE/bug_report.md b/unipdf/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 0000000..ee0d623
--- /dev/null
+++ b/unipdf/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,24 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[BUG]"
+labels: ''
+assignees: ''
+
+---
+
+## Description
+A clear and concise description of what the bug is.
+
+## Expected Behavior
+A clear and concise description of what you expected to happen.
+
+## Actual Behavior
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+## Attachments
+Include a self-contained reproducible code snippet and PDF file that demonstrates the issue.
diff --git a/unipdf/.github/ISSUE_TEMPLATE/feature_request.md b/unipdf/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 0000000..6dd8285
--- /dev/null
+++ b/unipdf/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "[FEATURE]"
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is.
+
+**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.
diff --git a/unipdf/.github/workflows/greetings.yml b/unipdf/.github/workflows/greetings.yml
new file mode 100644
index 0000000..0bb4907
--- /dev/null
+++ b/unipdf/.github/workflows/greetings.yml
@@ -0,0 +1,22 @@
+name: Greetings
+
+on: [issues]
+
+jobs:
+  greeting:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/first-interaction@v1
+      with:
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
+        issue-message: >
+          Welcome! Thanks for posting your first issue. The way things work here is that while customer issues are prioritized,
+          other issues go into our backlog where they are assessed and fitted into the roadmap when suitable.
+          If you need to get this done, consider buying a license which also enables you to use it in your commercial products.
+          More information can be found on https://unidoc.io/
+        pr-message: >
+          Thanks for posting your first PR. Please be sure to sign the CLA and make sure that the
+          the Developer Guidelines https://github.com/unidoc/unipdf/wiki/UniPDF-Developer-Guide were followed.
+          You can expect that we will review the PR and post comments. The timeframe fpr this can vary depending
+          on various factors, including which issue(s) the PR addresses and where it fits in the roadmap.
+          Note also that customer PRs are prioritized.