Update wiki Home page for wordpress

Home.md

@@ -1,21 +1,41 @@
-# Deploy the Project on CamelX Platform
+# WordPress
 
-Deploy on CamelX Platform in three steps
+Manage posts and users using the WordPress API.
 
-## 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 | `wordpress` |
+| Support Level | Stable |
+| Labels | cloud,api,cms |
+| 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-wordpress</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 |
+|------|------|----------|---------|-------------|
+| `operation` | string | ✓ |  | The endpoint operation. |
+| `operationDetail` | string |  |  | The second part of an endpoint operation. Needed only when endpoint semantic is not enough, like wordpress:post:delete |
+| `apiVersion` | string |  | `2` | The Wordpress REST API version |
+| `criteria` | object |  |  | The criteria to use with complex searches. |
+| `force` | boolean |  | `false` | Whether to bypass trash and force deletion. |
+| `id` | integer |  |  | The entity ID. Should be passed when the operation performed requires a specific entity, e.g. deleting a post |
+| `password` | string |  |  | Password from authorized user |
+| `searchCriteria` | object |  |  | Search criteria |
+| `url` | string | ✓ |  | The Wordpress API URL from your site, e.g. http://myblog.com/wp-json/ |
+| `user` | string |  |  | Authorized user to perform writing operations |
+| `bridgeErrorHandler` | boolean |  | `false` | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
+| `exceptionHandler` | object |  |  | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
+| `exchangePattern` | object |  |  | Sets the exchange pattern when the consumer creates an exchange. |
+| `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. |