From c2b9f5e552fb8342748f269074167cfd9983d7b4 Mon Sep 17 00:00:00 2001
From: gitea_admin <admin@gitea.local>
Date: Wed, 11 Mar 2026 14:40:05 +0000
Subject: [PATCH] Update wiki Home page for set-kafka-key-action

---
 Home.md | 34 ++++++++++++++++++++--------------
 1 file changed, 20 insertions(+), 14 deletions(-)

diff --git a/Home.md b/Home.md
index 93a012c..720b6c8 100644
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,27 @@
-# Deploy the Project on CamelX Platform
+# Set Kafka Key Action
 
-Deploy on CamelX Platform in three steps
+Set Kafka Key based on a specific incoming header value from the message body.
 
-## Step 1: Create a release
-From the project space, click on **"Create a release"**
+The headerName parameter allows you to specify which header value to set as Kafka Key.
 
-The new version is automatically available in the list
+## Metadata
 
-## Step 2: Deploy
-Click on **"Deploy"**
+| Property | Value |
+|----------|-------|
+| Type | action |
+| Group | Actions |
+| Namespace | Kafka |
+| Support Level | Stable |
+| Provider | Apache Software Foundation |
 
-- **Version:** Select the desired release
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
-- **Configuration:** Select the configuration source
-- **Resources:** Set CPU and Memory
+## Properties
 
-## Step 3: Expose
-Enable **"Expose"**
+| Name | Type | Required | Default | Description |
+|------|------|----------|---------|-------------|
+| `headerName` | string | ✓ |  | The name of the header to set as Kafka Key |
+| `forceHeaderDeletion` | boolean |  | `false` | If true, it will remove the header with name headerName from the Exchange after setting it as Kafka Key |
 
-Choose an **API Gateway** (Internal, Public, etc.)
+## Dependencies
+
+- `camel:kamelet`
+- `camel:core`