Update wiki Home page for stitch

Home.md

@@ -1,21 +1,36 @@
-# Deploy the Project on CamelX Platform
+# Stitch
 
-Deploy on CamelX Platform in three steps
+Stitch is a cloud ETL service that integrates various data sources into a central data warehouse through various integrations.
 
-## 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 | `stitch` |
+| Support Level | Stable |
+| Labels | cloud,api,saas,bigdata |
+| 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-stitch</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 |
+|------|------|----------|---------|-------------|
+| `tableName` | string |  |  | The name of the destination table the data is being pushed to. Table names must be unique in each destination schema, or loading issues will occur. Note: The number of characters in the table name should be within the destination's allowed limits or data will rejected. |
+| `keyNames` | string |  |  | A collection of comma separated strings representing the Primary Key fields in the source table. Stitch use these Primary Keys to de-dupe data during loading If not provided, the table will be loaded in an append-only manner. |
+| `region` | object |  | `EUROPE` | Stitch account region, e.g: europe |
+| `stitchSchema` | object |  |  | A schema that describes the record(s) |
+| `connectionProvider` | object |  |  | ConnectionProvider contain configuration for the HttpClient like Maximum connection limit .. etc, you can inject this ConnectionProvider and the StitchClient will initialize HttpClient with this ConnectionProvider |
+| `httpClient` | object |  |  | Reactor Netty HttpClient, you can injected it if you want to have custom HttpClient |
+| `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. |
+| `stitchClient` | object |  |  | Set a custom StitchClient that implements org.apache.camel.component.stitch.client.StitchClient interface |
+| `token` | string | ✓ |  | Stitch access token for the Stitch Import API |