docs: add all current features (#34)

docs/reference/github-action.md

@@ -1 +1,25 @@
 # GitHub Action
+
+## Reference
+
+The action is available as `apricote/releaser-pleaser` on GitHub.com.
+
+## Versions
+
+The `apricote/releaser-pleaser` action is released together with `releaser-pleaser` and they share the version number.
+
+The action does not support floating tags (e.g. `v1`) right now ([#31](https://github.com/apricote/releaser-pleaser/issues/31)). You have to use the full version or commit SHA instead: `apricote/releaser-pleaser@v0.2.0`.
+
+## Inputs
+
+The following inputs are supported by the `apricote/releaser-pleaser` GitHub Action.
+
+| Input         | Description                                            |         Default |                                                              Example |
+| ------------- | :----------------------------------------------------- | --------------: | -------------------------------------------------------------------: |
+| `branch`      | This branch is used as the target for releases.        |          `main` |                                                             `master` |
+| `token`       | GitHub token for creating and updating release PRs     | `$GITHUB_TOKEN` |                                `${{secrets.RELEASER_PLEASER_TOKEN}}` |
+| `extra-files` | List of files that are scanned for version references. |            `""` | <pre><code>version/version.go<br>deploy/deployment.yaml</code></pre> |
+
+## Outputs
+
+The action does not define any outputs.

docs/reference/glossary.md

@@ -0,0 +1,47 @@
+# Glossary
+
+### Changelog
+
+The Changelog is a file in the repository (`CHANGELOG.md`) that contains the [Release Notes](#release-notes) for every release of that repository. Usually, new releases are added at the top of the file.
+
+### Conventional Commits
+
+[Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) is a specification for commit messages. It is the only supported commit message schema in `releaser-pleaser`. Follow the link to learn more.
+
+### Forge
+
+A **forge** is a web-based collaborative software platform for both developing and sharing computer applications.[^wp-forge]
+
+Right now only **GitHub** is supported. We plan to support **GitLab** in the future ([#4](https://github.com/apricote/releaser-pleaser/issues/4)). For other forges like Forgejo or Gitea, please open an issue and submit a pull request.
+
+[^wp-forge]: Quote from [Wikipedia "Forge (software)"](<https://en.wikipedia.org/wiki/Forge_(software)>)
+
+### Markdown
+
+[Markdown](https://en.wikipedia.org/wiki/Markdown) is a lightweight markup language used on many [forges](#forge) as the preferred way to format text.
+
+In `releaser-pleaser` Markdown is used for most texts.
+
+### Pre-release
+
+Pre-releases are a concept of [SemVer](#semantic-versioning-semver). They follow the normal versioning schema but use a suffix out of `-alpha.X`, `-beta.X` and `-rc.X`.
+
+Pre-releases are not considered "stable" and are usually not recommended for most users.
+
+Learn more in the [Pre-releases](../guides/pre-releases.md) guide.
+
+### Release Pull Request
+
+A Release Pull Request is opened by `releaser-pleaser` whenever it finds releasable commits in your project. It proposes a new version number and the Changelog. Once it is merged, `releaser-pleaser` creates a matching release.
+
+Learn more in the [Release Pull Request](../explanation/release-pr.md) explanation.
+
+### Release Notes
+
+Release Notes describe the changes made to the repository since the last release. They are made available in the [Changelog](#changelog), in Git Tags and through the [forge](#forge)-native Releases.
+
+Learn more in the [Release Notes customization](../guides/release-notes.md) guide.
+
+### Semantic Versioning (SemVer)
+
+[Semantic Versioning](https://semver.org/) is a specification for version numbers. It is the only supported versioning schema in `releaser-pleaser`. Follow the link to learn more.

docs/reference/pr-options.md

@@ -1 +1,46 @@
 # Pull Request Options
+
+The proposed releases can by influenced by changing the description and labels of either the release pull request or the normal pull requests created by other developers. This document lists the available options for both types of pull requests.
+
+## Release Pull Request
+
+Created by `releaser-pleaser`.
+
+### Release Type
+
+**Labels**:
+
+- `rp-next-version::alpha`
+- `rp-next-version::beta`
+- `rp-next-version::rc`
+- `rp-next-version::normal`
+
+Adding one of these labels will change the type of the next release to the one indicated in the label. This is used to create [pre-releases](../guides/pre-releases.md).
+
+Adding more than one of these labels is not allowed and the behaviour if multiple labels are added is undefined.
+
+### Release Notes
+
+**Code Blocks**:
+
+- `rp-prefix`
+- `rp-suffix`
+
+Any text in code blocks with these languages is being added to the start or end of the Release Notes and Changelog. Learn more in the [Release Notes](../guides/release-notes.md) guide.
+
+### Status
+
+**Labels**:
+
+- `rp-release::pending`
+- `rp-release::tagged`
+
+These labels are automatically added by `releaser-pleaser` to release pull requests. They are used to track if the corresponding release was already created.
+
+Users should not set these labels themselves.
+
+## Other Pull Requests
+
+Not created by `releaser-pleaser`.
+
+Normal pull requests do not support any options right now.