[camel-website] branch master updated: Replace table with unordered list

[ac...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-website.git


The following commit(s) were added to refs/heads/master by this push:
     new dadd64a  Replace table with unordered list
     new bb16b6a  Merge pull request #175 from AghaSaad04/releases-structure-improvement
dadd64a is described below

commit dadd64a3121f247cc3b8aa772f58976b037c90be
Author: AghaSaad04 <ag...@gmail.com>
AuthorDate: Sun Mar 8 00:06:36 2020 +0500

    Replace table with unordered list
---
 content/blog/Camel3-Whatsnew/index.md | 93 +++++++++++++++++------------------
 1 file changed, 46 insertions(+), 47 deletions(-)

diff --git a/content/blog/Camel3-Whatsnew/index.md b/content/blog/Camel3-Whatsnew/index.md
index 66e021b..bb5d1e6 100644
--- a/content/blog/Camel3-Whatsnew/index.md
+++ b/content/blog/Camel3-Whatsnew/index.md
@@ -44,27 +44,27 @@ Camel 3 is the first official release that supports Java 11. Java 8 will still b
 
 The camel-core has been modularized from 1 JAR to 33 JARs. The core functionality has been splitup into:
 
-| Artifact |
-|---- |
-| **camel-api** | 
-| camel-base |
-| camel-caffeine-lrucache |
-| camel-cloud | 
-| camel-core |
-| camel-core-engine |
-| camel-core-osgi 
-| camel-core-xml |
-| camel-endpointdsl |
-| camel-headersmap |
-| camel-jaxp |
-| camel-main | 
-| camel-management-api |
-| camel-management-impl |
-| **camel-support** |
-| camel-util |
-| camel-util-json |
-
-For Camel end users then only a few JARs are relevant. 
+**Artifact**
+
+- camel-api
+- camel-base
+- camel-caffeine-lrucache
+- camel-cloud
+- camel-core
+- camel-core-engine
+- camel-core-osgi
+- camel-core-xml
+- camel-endpointdsl
+- camel-headersmap
+- camel-jaxp
+- camel-main
+- camel-management-api
+- camel-management-impl
+- camel-support
+- camel-util
+- camel-util-json
+
+For Camel end users then only a few JARs are relevant.
 
 **camel-api** contains the public API for Camel (eg interfaces such as CamelContext, Endpoint, Exchange, Message, and so on).
 
@@ -72,32 +72,31 @@ For Camel end users then only a few JARs are relevant.
 
 The components that resided in camel-core has also be externalized into individual components:
 
-| Artifact |
-|---- |
-| camel-bean |
-| camel-log |
-| camel-stub |
-| camel-browse |
-| camel-mock |
-| camel-timer |
-| camel-controlbus |
-| camel-properties |
-| camel-validator |
-| camel-dataformat |
-| camel-ref |
-| camel-vm |
-| camel-direct |
-| camel-rest |
-| camel-xpath |
-| camel-directvm |
-| camel-saga |
-| camel-xslt | 
-| camel-file |
-| camel-scheduler |
-| camel-zip-deflater |
-| camel-language |
-| camel-seda |
-
+**Artifact**
+
+- camel-bean
+- camel-log
+- camel-stub
+- camel-browse
+- camel-mock
+- camel-timer
+- camel-controlbus
+- camel-properties
+- camel-validator
+- camel-dataformat
+- camel-ref
+- camel-vm
+- camel-direct
+- camel-rest
+- camel-xpath
+- camel-directvm
+- camel-saga
+- camel-xslt
+- camel-file
+- camel-scheduler
+- camel-zip-deflater
+- camel-language
+- camel-seda
 
 Camel end users can then pick and choose exactly only what they need, or keep using everything.