work on auto-generating parts of docs from JSONSchema

src/content/docs/processors/osc/message/create.mdx

@@ -4,14 +4,11 @@ sidebar:
   label: Create
   order: 1
 ---
+import SchemaInfo from '../../../../../components/SchemaInfo.astro';
 
 This processor will create an OSC message from the provided parameters. This processor will return an error if any of the required parameters are missing or if the parameters are of the wrong type. The address parameter is required, while the args and types parameters are optional. However, if args are provided, then types must also be provided and must match the amount of args provided.
 
-- **type**: `osc.message.create`
-- **params**:
-  - **address**: the address of the OSC message.
-  - **args**: (optional) array of string templates for each argument.
-  - **types**: (optional) a single string with the of each arg in order. This is required if args are provided.
+<SchemaInfo type="processor" id="osc.message.create"/>
 
 ### Example
 

src/content/docs/processors/osc/message/decode.mdx

@@ -4,10 +4,11 @@ sidebar:
   label: Decode
   order: 3
 ---
+import SchemaInfo from '../../../../../components/SchemaInfo.astro';
 
 The `osc.message.decode` processor takes a array of bytes and turn it into OSC message if it can be. This processor will return an error if the bytes cannot be parsed as an OSC message
 
-- **type**: `osc.message.decode`
+<SchemaInfo type="processor" id="osc.message.decode"/>
 
 ### Example
 

src/content/docs/processors/osc/message/encode.mdx

@@ -4,10 +4,11 @@ sidebar:
   label: Encode
   order: 2
 ---
+import SchemaInfo from '../../../../../components/SchemaInfo.astro';
 
 The `osc.message.encode` processor takes an OSC message and turns it into an array of bytes. This processor will return an error if the OSC message cannot be turned into bytes.
 
-- **type**: `osc.message.encode`
+<SchemaInfo type="processor" id="osc.message.encode"/>
 
 ### Example