From 7692e2361fff21e080e5a00a434cc8d29173102f Mon Sep 17 00:00:00 2001
From: gitea_admin <admin@gitea.local>
Date: Wed, 11 Mar 2026 14:36:32 +0000
Subject: [PATCH] Update wiki Home page for chatscript

---
 Home.md | 40 ++++++++++++++++++++++++++--------------
 1 file changed, 26 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..8bdee8b 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,33 @@
-# Deploy the Project on CamelX Platform
+# ChatScript
 
-Deploy on CamelX Platform in three steps
+Chat with a ChatScript Server.
 
-## 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 | `chatscript` |
+| Support Level | Stable |
+| Labels | ai,chat |
+| 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-chatscript</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 |
+|------|------|----------|---------|-------------|
+| `host` | string | ✓ |  | Hostname or IP of the server on which CS server is running |
+| `port` | integer |  | `1024` | Port on which ChatScript is listening to |
+| `botName` | string | ✓ |  | Name of the Bot in CS to converse with |
+| `chatUserName` | string |  |  | Username who initializes the CS conversation. To be set when chat is initialized from camel route |
+| `resetChat` | boolean |  | `false` | Issues :reset command to start a new conversation everytime |
+| `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. |