Update wiki Home page for message-timestamp-router-action

Home.md

@@ -1,21 +1,28 @@
-# Deploy the Project on CamelX Platform
+# Message Timestamp Router Action
 
-Deploy on CamelX Platform in three steps
+Update the topic field as a function of the original topic name and the record's timestamp field.
 
-## 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 |
+|----------|-------|
+| Type | action |
+| Group | Actions |
+| Namespace | Kafka |
+| Support Level | Stable |
+| Provider | Apache Software Foundation |
 
-## Step 2: Deploy
+## Properties
-Click on **"Deploy"**
 
-- **Version:** Select the desired release
+| Name | Type | Required | Default | Description |
-- **Environment:** Choose `Development`, `Staging`, or `Production` 
+|------|------|----------|---------|-------------|
-- **Configuration:** Select the configuration source
+| `topicFormat` | string |  | `topic-$[timestamp]` | Format string which can contain '$[topic]' and '$[timestamp]' as placeholders for the topic and timestamp, respectively. |
-- **Resources:** Set CPU and Memory
+| `timestampFormat` | string |  | `yyyyMMdd` | Format string for the timestamp that is compatible with java.text.SimpleDateFormat. |
+| `timestampKeys` | string | ✓ |  | Comma separated list of Timestamp keys. The timestamp is taken from the first found field. |
+| `timestampKeyFormat` | string |  | `timestamp` | Format of the timestamp keys. Possible values are 'timestamp' or any format string for the timestamp that is compatible with java.text.SimpleDateFormat. In case of 'timestamp' the field will be evaluated as milliseconds since 1970, so as a UNIX Timestamp. |
 
-## Step 3: Expose
+## Dependencies
-Enable **"Expose"**
 
-Choose an **API Gateway** (Internal, Public, etc.)
+- `camel:jackson`
+- `camel:kamelet`
+- `camel:core`