debezium/dbz#1569 Update the text and catalog gif

Signed-off-by: indraraj <indraraj14@gmail.com>

Author: indraraj

_posts/2026-01-22-Debezium-platform-connection.adoc

@@ -6,18 +6,18 @@ tags: [ UI, debezium-platform, integration, debezium operator, debezium, debeziu
 author: indrashukla
 ---
 
-Since introducing the Debezium Management Platform (Debezium Platform), our goal has been to simplify how you build and manage CDC data pipelines—so you can focus on how your data flows, rather than repeatedly configuring the same infrastructure details.
+The Debezium Platform aims to simplify the building and management of CDC data pipelines by streamlining infrastructure setup.
 
-Earlier, connection-related properties (such as hostnames, ports, credentials, or authentication details) were defined directly as part of the Source or Destination configuration.
-While this worked, it often led to duplication, harder maintenance of the same connection details across multiple instances.
+Earlier, connection-related properties (such as hostnames, ports, credentials, and authentication details) were defined directly in the Source or Destination configuration.
+While this worked, it often led to duplication and harder maintenance of the same connection details across multiple instances.
 
-To address this, we are introducing **Connections** as a first-class entity in the Debezium Platform.
+To address this, we are introducing **Connections** as a first-class citizen in the Debezium Platform, making it easier for you to manage connection details in one place and avoid repetitive setup.
 
-Connections allow you to define, validate, and reuse connection details independently, and then reference them from any number of Sources and Destinations.
+Connections allow you to define, validate, and reuse connection details independently, reducing configuration errors and saving time by referencing them in multiple Sources and Destinations.
 
 == What are Connections?
 
-A *Connection* represents the configuration required to connect to an external system, such as a source database or a sink endpoint.
+A *Connection* specifies the configuration required to connect to an external system, like a source database or a sink endpoint.
 
 Instead of embedding these details inside each Source or Destination:
 
@@ -29,7 +29,7 @@ This makes pipelines easier to manage, safer to modify, and faster to set up.
 
 == Why introduce Connections?
 
-Separating connection details from Source and Destination configurations provides several benefits:
+Rather than defining connection details inside each Source or Destination, separating them as a first-class citizen provides a host of benefits:
 
 **Reusability**::
 A single Connection can be reused across multiple Sources or Destinations.
@@ -41,50 +41,56 @@ Update credentials or connection parameters in one place without editing every p
 Validate a Connection before it is ever used by a Source or Destination.
 
 **Cleaner configurations**::
-Source and Destination definitions focus only on CDC and data flow logic, not infrastructure details.
+Source and Destination definitions focus only on CDC and data-flow logic, not on infrastructure details.
+
+All these benefits make creating and managing pipelines easier, safer, and faster.
 
 == Creating a Connection
 
 You can create a Connection directly from the catalog or during the resource creation flow.
 
-When creating a Connection, you define the connection-specific properties required to communicate with the external system (for example, database host, port, authentication details, or sink endpoint configuration).
-
-Once defined, the Connection can be validated independently to ensure it is correctly configured and reachable.
-
 [.centered-image.responsive-image]
+====
 ++++
-<!-- Screenshot placeholder: Connection creation form -->
+<img src="/assets/images/2026-01-22-Debezium-platform-connection/connection-catalog.gif" style="max-width:100%;" class="responsive-image" alt="Connection catalog">
 ++++
+Connection catalog.
+====
+
+When creating a Connection, you define the connection-specific properties required to communicate with the external system (for example, database host, port, authentication details, or sink endpoint configuration).
+
+Once defined, the Connection can be validated independently to ensure it is correctly configured and reachable.
 
 === Validating a Connection
 
 A key part of the new Connection workflow is connection validation.
 
+[.centered-image.responsive-image]
+====
+++++
+<img src="/assets/images/2026-01-22-Debezium-platform-connection/Connection-creation.gif" style="max-width:100%;" class="responsive-image" alt="Connection validation and creation">
+++++
+Connection validation and creation.
+====
+
 After creating a Connection, you can explicitly validate it to verify that:
 
 * The configuration is complete
 * The platform can successfully connect to the target system
 * Authentication and network settings are correct
 
-This helps catch issues early—before a Source or Destination is created or a pipeline is executed.
-
-[.centered-image.responsive-image]
-++++
-<!-- Screenshot placeholder: Connection validation result -->
-++++
+This helps catch issues early—before a Source or Destination is created or a pipeline is started.
 
 == Using Connections in Sources and Destinations
 
-Once a Connection is created and validated, it becomes available for selection when creating Sources and Destinations.
-
-Instead of entering connection properties again, you simply reference an existing Connection.
-The Source or Destination then uses that Connection at runtime.
+When defining a Source or Destination, all validated Connection definitions are available in a drop-down for quick access, making pipeline setup and management fast and straightforward.
 
 [.centered-image.responsive-image]
 ====
 ++++
-<img src="/assets/images/2026-01-22-Debezium-platform-connection/connection-selector.gif" style="max-width:100%;" class="responsive-image" alt="Connection selector showing how to select or create a connection when configuring a Source">
+<img src="/assets/images/2026-01-22-Debezium-platform-connection/connection-selector.gif" style="max-width:100%;" class="responsive-image" alt="Connection selector on the go">
 ++++
+Select connection for source
 ====
 
 This allows the same Connection to be shared across:
@@ -94,10 +100,10 @@ This allows the same Connection to be shared across:
 
 == Updating existing workflows
 
-If you are already familiar with creating Sources and Destinations in the Debezium Platform, the overall workflow remains the same.
+If you know how to create Sources and Destinations in Debezium, the workflow is unchanged, and updating to use Connection definitions is quick and painless.
 
-The key difference is that connection-related properties are no longer embedded directly in the resource configuration.
-Instead, they are managed through reusable Connections, keeping configurations modular and easier to evolve over time.
+First, create a Connection definition with all the connection properties your existing pipeline uses. After you create and validate the Connection, 
+simply edit the workflow and select the newly defined Connection definition to link it to the pipeline. The pipeline then uses the reusable Connection definition moving forward.
 
 == Demo: Connections in action
 
@@ -115,7 +121,7 @@ The following video demonstrates how to:
 
 == More coming soon!
 
-Connections are a foundational step toward making the Debezium Platform more modular, maintainable, and scalable.
+Connections lay the foundation for making the Debezium Platform more modular, maintainable, and scalable.
 
 We'll continue to build on this with further improvements and new features in upcoming releases.