add integrations section

Author: CodeShellDev

docs/best-practices/best-practices.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 4
+sidebar_position: 5
 title: Best Practices
 ---
 

docs/features/features.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 7
+sidebar_position: 2
 title: Features
 ---
 

docs/getting-started/_category_.json

@@ -1,4 +1,4 @@
 {
 	"label": "Getting Started",
-	"position": 2
+	"position": 3
 }

docs/integrations/_category_.json

@@ -0,0 +1,4 @@
+{
+	"label": "Integrations",
+	"position": 8
+}

docs/integrations/compatibility.md

@@ -0,0 +1,35 @@
+---
+sidebar_position: 1
+title: Compatibility
+---
+
+# Compatibility
+
+## The Problem
+
+**Secured Signal API** is only of use when compatible with programms.
+Even if it keeps the underlying Signal CLI REST API you'd still need your services to support Signal CLI REST API.
+
+## The Solution
+
+**Secured Signal API** implements enough features to technically support any and all services.
+But with one flaw:
+
+> _manual configuration_
+
+In order for Secured Signal API to be compatible and integratable with a service you still need to manually define [**Data Aliases**](../configuration/data-aliases)
+and [**Message Templates**](../configuration/message-templates), which is quite easy,
+provided you know what the services is using as payload (try sending a request to some debugging endpoint).
+
+> _Now wouldn't it be great if someone had already done that?_
+
+If you are using a common and popular service or programm there is probably someone who already configured everything and was willing to share it on
+[our Github Discussions](https://github.com/codeshelldev/secured-signal-api/discussions) (**Thank you!**).
+
+## How to Help
+
+You successfully integrated a service and want to share it?
+
+> Well that's nice of you 🤩👍️
+
+Then create a [Discussion](https://github.com/CodeShellDev/secured-signal-api/discussions/categories/integrations) and share your configs or if you want you can also submit a [Pull Request](https://github.com/codeshelldev/secured-signal-api/pulls) to add your integration to the [**Integrations Section**](.) in the official Documentation.

docs/reverse-proxy/_category_.json

@@ -1,4 +1,4 @@
 {
 	"label": "Reverse Proxy",
-	"position": 6
+	"position": 7
 }

docs/usage/_category_.json

@@ -1,4 +1,4 @@
 {
 	"label": "Usage",
-	"position": 3
+	"position": 4
 }