add layout for remaining processors/modules and order everything

src/content/docs/modules/http/http-server.md

@@ -1,6 +1,7 @@
 ---
 title: HTTP Server
 sidebar:
+    label: Server
     order: 2
 ---
 The `http.server` module emits a message for every HTTP request that is made to the server.

src/content/docs/modules/midi/input.mdx

@@ -1,6 +1,7 @@
 ---
 title: MIDI Input
 sidebar:
+    label: Input
     order: 1
 ---
 

src/content/docs/modules/midi/output.mdx

@@ -1,6 +1,7 @@
 ---
 title: MIDI Output
 sidebar:
+    label: Output
     order: 2
 ---
 import { Aside } from '@astrojs/starlight/components';

src/content/docs/modules/mqtt/client.mdx

@@ -1,6 +1,7 @@
 ---
 title: MQTT Client
 sidebar:
+    label: Client
     order: 1
 ---
 

src/content/docs/modules/nats/client.md

@@ -0,0 +1,11 @@
+---
+title: NATS Client
+sidebar:
+    label: Client
+    order: 1
+---
+
+- **type**: `nats.client`
+- **params**:
+    - **url**
+    - **subject**

src/content/docs/modules/nats/server.md

@@ -0,0 +1,11 @@
+---
+title: NATS Server
+sidebar:
+    label: Server
+    order: 2
+---
+
+- **type**: `nats.server`
+- **params**:
+    - **ip**
+    - **port**

src/content/docs/modules/net/tcp/client.md

@@ -1,6 +1,7 @@
 ---
 title: TCP Client
 sidebar:
+    label: Client
     order: 1
 ---
 The `net.tcp.client` module connects to TCP server and emits messages based on the data it receives from the server that it connects to. Messages are determined by "framing" techniques as TCP is a stream based protocol. The module will attempt to reconnect anytime the connection is closed.

src/content/docs/modules/net/tcp/server.md

@@ -1,6 +1,7 @@
 ---
 title: TCP Server
 sidebar:
+    label: Server
     order: 2
 ---
 The `net.tcp.server` module emits a message messages based on the data it receives from clients that connect to it. Messages are determined by "framing" techniques as TCP is a stream based protocol.

src/content/docs/modules/net/udp/client.md

@@ -1,7 +1,8 @@
 ---
 title: UDP Client
 sidebar:
-    order: 3
+    label: Client
+    order: 1
 ---
 The `net.udp.client` module sends messages to a the configured `host` and `port`. This module does not produce any messages and so using it as an `input` to a [route](/concepts/routes) would be pointless.
 

src/content/docs/modules/net/udp/multicast.md

@@ -0,0 +1,12 @@
+---
+title: UDP Multicast
+sidebar:
+    label: Multicast
+    order: 3
+---
+
+- **type**: `net.udp.multicast`
+- **params**:
+    - **ip**
+    - **port**
+    - **bufferSize**

src/content/docs/modules/net/udp/server.md

@@ -1,7 +1,8 @@
 ---
 title: UDP Server
 sidebar:
-    order: 4
+    label: Server
+    order: 2
 ---
 The `net.udp.server` module emits a message for every incoming UDP datagram.
 

src/content/docs/modules/psn/client.md

@@ -0,0 +1,8 @@
+---
+title: PSN Client
+sidebar:
+    label: Client
+    order: 1
+---
+
+- **type**: `psn.client`

src/content/docs/modules/redis/client.mdx

@@ -1,6 +1,7 @@
 ---
 title: Redis Client
 sidebar:
+    label: Client
     order: 1
 ---
 

src/content/docs/modules/serial/client.mdx

@@ -1,6 +1,7 @@
 ---
 title: Serial Client
 sidebar:
+    label: Client
     order: 1
 ---
 

src/content/docs/modules/sip/call/server.md

@@ -0,0 +1,13 @@
+---
+title: SIP Call Server
+sidebar:
+    label: Server
+    order: 1
+---
+
+- **type**: `sip.call.server`
+- **params**:
+    - **ip**
+    - **port**
+    - **transport**
+    - **userAgent**

src/content/docs/modules/sip/dtmf/server.md

@@ -0,0 +1,14 @@
+---
+title: SIP DTMF Server
+sidebar:
+    label: Server
+    order: 1
+---
+
+- **type**: `sip.dtmf.server`
+- **params**:
+    - **ip**
+    - **port**
+    - **transport**
+    - **userAgent**
+    - **separator**