open-source docs update

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders 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, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at
+<https://www.contributor-covenant.org/translations>.

.github/CONTRIBUTING.md

@@ -0,0 +1,110 @@
+# Contributing to the Add to Calendar Button Repository
+
+You like the project and want to get involved?
+Awesome! It is always great to get some help.
+
+Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.
+
+Following these guidelines helps to communicate that you respect the time of the developers managing and developing this open source project.
+In return, they should reciprocate that respect in addressing your issue or assessing patches and features.
+
+<br />
+
+## 📄 Using the issue tracker
+
+The [issue tracker](https://github.com/add2cal/add-to-calendar-button/issues) is the preferred channel for [bug reports](#bugs), [precise features requests](#features) and [submitting pull requests](#pull-requests), but please **do not** use the issue tracker for personal support requests.
+
+
+<br />
+
+<a name="bugs"></a>
+
+## 🐞 Bug reports
+
+A bug is a _demonstrable problem_ that is caused by the code in the repository.
+Good bug reports are extremely helpful - thank you!
+
+Guidelines for bug reports:
+
+1.  **Use the GitHub issue search** — check if the issue has already been reported.
+
+2.  **Check if the issue has been fixed** — try to reproduce it using the latest version.
+
+A good bug report shouldn't leave others needing to chase you up for more information.
+Please try to be as detailed as possible in your report. What is your environment? What steps will reproduce the issue? What browser(s) and OS experience the problem? What would you expect to be the outcome?
+All these details will help people to fix any potential bugs.
+
+Therefore, use the official bug issue option and fill out all the provided fields
+
+<br />
+
+<a name="features"></a>
+
+## ✨ Feature requests
+
+Feature requests are welcome. But take a moment to find out whether your idea fits with the scope and aims of the project.
+It's up to _you_ to make a strong case to convince the project's developers of the merits of this feature.
+Please provide as much detail and context as possible.
+Within the scope of this repository, a feature request can also simply aim for specific guides or simply additional content.
+
+<br />
+
+<a name="pull-requests"></a>
+
+## 🧰 Pull requests
+
+Good pull requests - patches, improvements, new features - are a fantastic help.
+They should remain focused in scope and avoid containing unrelated commits.
+
+**Please ask first** before embarking on any significant pull request (e.g. implementing features, refactoring code, porting to a different language).
+Otherwise you risk spending a lot of time working on something that the project's developers might not want to merge into the project.
+You can do so via the issue tracker or email us at [contributing at add-to-calendar-pro.com]([email protected]);
+
+Adhering to the following process is the best way to get your work included in the project:
+
+1.  [Fork](https://help.github.com/articles/fork-a-repo/) the project, clone your fork, and configure the remotes:
+
+    ```bash
+    # Clone your fork of the repo
+    git clone https://github.com/add2cal/docs.git
+    # Navigate to the newly cloned directory
+    cd docs
+    # Assign the original repo to a remote called "upstream"
+    git remote add upstream https://github.com/add2cal/docs.git
+    ```
+
+2.  If you cloned a while ago, get the latest changes from upstream:
+
+    ```bash
+    git checkout main
+    git pull upstream main
+    ```
+
+    **Also check any other dev_x branch. In doubt, especially if there is a lot of unmerged stuff in them, ask how to proceed!**
+
+3.  Create a new topic branch to contain your feature, change, or fix. The name should start with "dev\_", followed by your individual title.
+
+    ```bash
+    git checkout -b <topic-branch-name>
+    ```
+
+4.  Commit your changes in logical chunks. Please adhere to these [git commit message guidelines](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) or your code is unlikely be merged into the main project.
+    Use Git's [interactive rebase](https://help.github.com/articles/about-git-rebase/) feature to tidy up your commits before making them public.
+
+5.  Locally merge (or rebase) the upstream main branch into your topic branch:
+
+    ```bash
+    git pull [--rebase] upstream main
+    ```
+
+6.  Push your topic branch up to your fork:
+
+    ```bash
+    git push origin <topic-branch-name>
+    ```
+
+7.  [Open a Pull Request](https://help.github.com/articles/using-pull-requests/) with a clear title and description.
+
+<br />
+
+**IMPORTANT**: By submitting a patch, you agree to allow the project owners to license your work under the terms of the [Apache License, Version 2.0](../LICENSE.txt).

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,24 @@
+## Type(s) of changes
+
+<!--- What types of changes does your code introduce? Remove the lines, that do not apply -->
+
+- **(Bug) fix** <!--- (non-breaking change which fixes an issue) -->
+- **Updates to the content** <!--- (changing content) -->
+- **Breaking change** <!--- (changes to the config, new pages or structure, even deeper changes) -->
+
+## Description of the change
+
+<!--- Describe your changes and why it was important to do it -->
+
+...
+
+## Checklist
+
+<!--- Go over all the following points, and put an `x` in the boxes. -->
+
+- [] My code follows the code style of this project.
+- [] I have read the **CONTRIBUTING** document.
+
+<!--- Pull requests should be thought of as a conversation. There will be some back and forth when trying to get code merged into this or any other project. With all but the simplest changes you can and should expect that the maintainers of the project will request changes to your code. Please be aware of that and check in after you open your PR in order to get your code merged in cleanly.
+
+Thanks! -->

.github/dependabot.yml

@@ -0,0 +1,8 @@
+version: 2
+updates:
+  # Enable version updates for npm
+  - package-ecosystem: 'npm'
+    directory: '/'
+    schedule:
+      interval: 'monthly'
+    open-pull-requests-limit: 0

README.md

@@ -1,3 +1,22 @@
-# Add to Calendar Documentation
+# Add to Calendar PRO Docs
 
-Documentation for the Pro application
+This is the official documentation for Add to Calendar PRO.
+
+[add-to-calendar-pro.com](https://add-to-calendar-pro.com)
+
+<br /><br /><br /><br />
+
+
+## 🙌 Contributing
+
+Anyone is welcome to contribute, if you think that some parts are not helpful or missing important details.
+
+Simply open up a pull request, but mind our [guidelines](.github/CONTRIBUTING.md).
+
+If you are unsure, whether a change (especially, if it is significant) might get approved, open a new issue first. There, explain what you are up for before starting the actual work.
+
+<br /><br />
+
+## 📃 License
+
+This documentation is licensed under [Apache License, Version 2.0](LICENSE.txt).