From a30659ea31b066049cd65c24a501f82fb9a6650a Mon Sep 17 00:00:00 2001
From: gitea_admin <admin@gitea.local>
Date: Mon, 12 Oct 2026 05:41:19 +0000
Subject: [PATCH] Update wiki Home page for wasm

---
 Home.md | 37 +++++++++++++++++++++++--------------
 1 file changed, 23 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..9db1906 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,30 @@
-# Deploy the Project on CamelX Platform
+# Wasm
 
-Deploy on CamelX Platform in three steps
+Invoke Wasm functions.
 
-## 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 | `wasm` |
+| Support Level | Stable |
+| Labels | core,script |
+| Version | 4.20.0 (CEQ 3.36.0) |
 
-## 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.quarkus</groupId>
+    <artifactId>camel-quarkus-wasm</artifactId>
+    <version>4.20.0 (CEQ 3.36.0)</version>
+</dependency>
+```
 
-## Step 3: Expose
-Enable **"Expose"**
+## Endpoint Properties
 
-Choose an **API Gateway** (Internal, Public, etc.)
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `functionName` | string | ✓ |  | The Function Name |
+| `module` | string | ✓ |  | Set the module (the distributable, loadable, and executable unit of code in WebAssembly) resource that provides the producer function. |
+| `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. |