Update wiki Home page for ibm-watson-language

Home.md

@@ -1,21 +1,38 @@
-# Deploy the Project on CamelX Platform
+# IBM Watson Language
 
-Deploy on CamelX Platform in three steps
+Perform natural language processing using IBM Watson Natural Language Understanding
 
-## Step 1: Create a release
+## Metadata
-From the project space, click on **"Create a release"**
 
-The new version is automatically available in the list
+| Property | Value |
+|----------|-------|
+| Scheme | `ibm-watson-language` |
+| Support Level | Stable |
+| Labels | ai,cloud |
+| Version | 4.20.0 (CEQ 3.36.0) |
 
-## Step 2: Deploy
+## Maven Dependency
-Click on **"Deploy"**
 
-- **Version:** Select the desired release
+```xml
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
+<dependency>
-- **Configuration:** Select the configuration source
+    <groupId>org.apache.camel.quarkus</groupId>
-- **Resources:** Set CPU and Memory
+    <artifactId>camel-quarkus-ibm-watson-language</artifactId>
+    <version>4.20.0 (CEQ 3.36.0)</version>
+</dependency>
+```
 
-## Step 3: Expose
+## Endpoint Properties
-Enable **"Expose"**
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `label` | string | ✓ |  | Logical name |
+| `serviceUrl` | string |  |  | The service endpoint URL. If not specified, the default URL will be used. |
+| `analyzeCategories` | boolean |  | `false` | Enable category classification |
+| `analyzeConcepts` | boolean |  | `false` | Enable concept extraction |
+| `analyzeEmotion` | boolean |  | `false` | Enable emotion analysis |
+| `analyzeEntities` | boolean |  | `true` | Enable entity extraction |
+| `analyzeKeywords` | boolean |  | `true` | Enable keyword extraction |
+| `analyzeSentiment` | boolean |  | `true` | Enable sentiment analysis |
+| `operation` | enum |  |  | The operation to perform |
+| `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. |
+| `apiKey` | string | ✓ |  | The IBM Cloud API key for authentication |