davsclaus commented on a change in pull request #546:
URL: https://github.com/apache/camel-website/pull/546#discussion_r581075990



##########
File path: content/blog/2021/02/Kamelet-Catalog/index.md
##########
@@ -0,0 +1,52 @@
+---
+title: "Kamelet Catalog"
+date: 2021-02-23
+draft: false
+authors: [nicolaferraro]
+categories: ["Camel-K"]
+preview: "We're starting a new initiative at Apache Camel to create a 
community-driven catalog of reusable Kamelets"
+---
+
+We're starting a new initiative at Apache Camel to create a community-driven 
catalog of reusable Kamelets (_Camel_ route snipp_ets_, i.e. connectors) that 
can be used to stream data from/to external systems into any platform powered 
by Apache Camel.
+
+The ["Apache Camel Kamelet catalog" is available here](/camel-kamelets/latest) 
and it already contains a collection of useful Kamelets: we would like to 
extend it with help of the community.
+
+Kamelets are currently supported out-of-the-box by the [Apache Camel 
K](/camel-k/latest) project and we're working to support them also in Camel 
core and [Camel Kafka Connector](/camel-kafka-connector/latest/).

Review comment:
       I think we may want to emphaisize a bit more by Camel core it can 
eventually run anywhere with Camel also Camel Spring Boot and Camel Quarkus.

##########
File path: content/blog/2021/02/Kamelet-Catalog/index.md
##########
@@ -0,0 +1,52 @@
+---
+title: "Kamelet Catalog"
+date: 2021-02-23
+draft: false
+authors: [nicolaferraro]
+categories: ["Camel-K"]
+preview: "We're starting a new initiative at Apache Camel to create a 
community-driven catalog of reusable Kamelets"
+---
+
+We're starting a new initiative at Apache Camel to create a community-driven 
catalog of reusable Kamelets (_Camel_ route snipp_ets_, i.e. connectors) that 
can be used to stream data from/to external systems into any platform powered 
by Apache Camel.
+
+The ["Apache Camel Kamelet catalog" is available here](/camel-kamelets/latest) 
and it already contains a collection of useful Kamelets: we would like to 
extend it with help of the community.
+
+Kamelets are currently supported out-of-the-box by the [Apache Camel 
K](/camel-k/latest) project and we're working to support them also in Camel 
core and [Camel Kafka Connector](/camel-kafka-connector/latest/).
+
+## Why are they useful?
+
+The most important reason why the new Kamelet catalog is so useful is that it 
provides a collection of connectors that are not tied to a particular platform, 
but they can be reused in multiple contexts. The new **OpenShift 4.7 developer 
console** is a clear evidence of this pattern. You can look at what it provides 
in the following animation:
+
+![Kamelet Catalog demo in Openshift 4.7 Developer 
Console](./kamelet-catalog-source-demo.gif)
+
+The console shows a serverless environment where a Knative channel has been 
created and it's ready to receive and dispatch events to a registered 
subscribing service.
+From the console, the user can add a new "Event Source" and the UI displays a 
collection of possibilities: well, starting from Camel K 1.4.0, that collection 
of sources will display **the official Apache Camel Kamelet catalog**. This 
means that [contributing](#markdown-header-contributing) new Kamelets to the 
catalog will allow you to enhance the OpenShift catalog of Knative sources, for 
instance.
+
+But there's nothing in the Kamelet catalog specifically related to OpenShift: 
**we show this to encourage people to take the same approach** for other 
platforms (in-house or open source, especially Kubernetes-based) and use cases. 
One of the advantages of this approach is that, since Kamelets have a well 
defined JSON-schema interface, they are available to any kind of users, 
including those who don't even know anything about Apache Camel.

Review comment:
       Can we add a link to this JSon-schema (or a landing page for this spec)




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to