Update wiki Home page for jolt

Home.md

@@ -1,21 +1,34 @@
-# Deploy the Project on CamelX Platform
+# JOLT
 
-Deploy on CamelX Platform in three steps
+JSON to JSON transformation using JOLT.
 
-## Step 1: Create a release
-From the project space, click on **"Create a release"**
+## Metadata
 
-The new version is automatically available in the list
+| Property | Value |
+|----------|-------|
+| Scheme | `jolt` |
+| Support Level | Stable |
+| Labels | transformation |
+| Version | 4.10.2 |
 
-## Step 2: Deploy
-Click on **"Deploy"**
+## Maven Dependency
 
-- **Version:** Select the desired release
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
-- **Configuration:** Select the configuration source
-- **Resources:** Set CPU and Memory
+```xml
+<dependency>
+    <groupId>org.apache.camel</groupId>
+    <artifactId>camel-jolt</artifactId>
+    <version>4.10.2</version>
+</dependency>
+```
 
-## Step 3: Expose
-Enable **"Expose"**
+## Endpoint Properties
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `resourceUri` | string | ✓ |  | Path to the resource. You can prefix with: classpath, file, http, ref, or bean. classpath, file and http loads the resource using these protocols (classpath is default). ref will lookup the resource in the registry. bean will call a method on a bean to be used as the resource. For bean you can specify the method name after dot, eg bean:myBean.myMethod. |
+| `allowTemplateFromHeader` | boolean |  | `false` | Whether to allow to use resource template from header or not (default false). Enabling this allows to specify dynamic templates via message header. However this can be seen as a potential security vulnerability if the header is coming from a malicious user, so use this with care. |
+| `contentCache` | boolean |  | `false` | Sets whether to use resource content cache or not |
+| `inputType` | object |  | `Hydrated` | Specifies if the input is hydrated JSON or a JSON String. |
+| `outputType` | object |  | `Hydrated` | Specifies if the output should be hydrated JSON or a JSON String. |
+| `transformDsl` | object |  | `Chainr` | Specifies the Transform DSL of the endpoint resource. If none is specified Chainr will be used. |
+| `lazyStartProducer` | boolean |  | `false` | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |