chore(repo): update readme files (#2095)

Author: spetz

README.md

@@ -90,11 +90,9 @@ This is the high-level architecture of the Iggy message streaming server, where
 
 ## Version
 
-The latest released version is `0.4.300` for Iggy server, which is compatible with `0.6` Rust client SDK and the others.
+The official releases follow the regular semver (`0.5.0`) or have `latest` tag applied (`apache/iggy:latest`).
 
-The recent improvements based on the zero-copy (de)serialization, along with updated SDKs etc. will be available in the upcoming release with Iggy server `0.5.0`, Rust SDK `0.7` and all the other SDKs.
-
-You can also find the `edge` versions of SDKs that are compatible with the `edge` version of Iggy Server Docker Image, but should be used with caution as these are not based on the official release.
+We do also publish edge/dev/nightly releases (e.g. `0.5.0-edge.1` or `apache/iggy:edge`), for both, SDKs and the Docker images, which are typically compatible with the latest changes, but are not guaranteed to be stable, and as the name states, are not recommended for production use.
 
 ---
 
@@ -105,22 +103,22 @@ You can also find the `edge` versions of SDKs that are compatible with the `edge
 
 ---
 
-## Supported languages SDK (work in progress)
+## Supported languages SDK
+
+- [Rust](https://crates.io/crates/iggy)
+- [C#](https://www.nuget.org/packages/Apache.Iggy/)
+- [Java](https://repository.apache.org/#nexus-search;quick~iggy)
+- [Python](https://pypi.org/project/apache-iggy/)
+- [Node.js (TypeScript)](https://www.npmjs.com/package/apache-iggy)
+- [Go](https://pkg.go.dev/github.com/apache/iggy/foreign/go)
 
-- Rust
-- C#
-- Java
-- Go
-- Python
-- Node
-- C++
-- Elixir
+C++ and Elixir are work in progress.
 
 ---
 
 ## CLI
 
-The brand new, rich, interactive CLI is implemented under the `cli` project, to provide the best developer experience. This is a great addition to the Web UI, especially for all the developers who prefer using the console tools.
+The interactive CLI is implemented under the `cli` project, to provide the best developer experience. This is a great addition to the Web UI, especially for all the developers who prefer using the console tools.
 
 Iggy CLI can be installed with `cargo install iggy-cli` and then simply accessed by typing `iggy` in your terminal.
 
@@ -175,7 +173,9 @@ The [Model Context Protocol](https://modelcontextprotocol.io) (MCP) is an open p
 
 ## Docker
 
-The official images can be found in [Docker Hub](https://hub.docker.com/r/apache/iggy), simply type `docker pull apache/iggy` to pull the image.
+The official Apache Iggy images can be found in [Docker Hub](https://hub.docker.com/r/apache/iggy), simply type `docker pull apache/iggy` to pull the image.
+
+You can also find the images for all the different tooling such as Connectors, MCP Server etc. [here](https://hub.docker.com/u/apache?page=1&search=iggy).
 
 Please note that the images tagged as `latest` are based on the official, stable releases, while the `edge` ones are updated directly from latest version of the `master` branch.
 
@@ -313,7 +313,7 @@ let mut producer = client
 producer.init().await?;
 
 // Send some messages to the topic
-let messages = vec![Message::from_str("Hello Apache Iggy")?];
+let messages = vec![IggyMessage::from_str("Hello Apache Iggy")?];
 producer.send(messages).await?;
 
 // Create a consumer for the given stream and one of its topics

core/ai/mcp/README.md

@@ -60,3 +60,5 @@ Here's the example configuration to be used with Claude Desktop:
 ```
 
 **Remember to use the appropriate Iggy account credentials for your environment** (e.g. create the user with read-only permissions to avoid modifying the data). On top of this, you can also configure the `permissions` for the MCP server to control which operations are allowed (this will be checked first, before forwarding the actual request to the Iggy server).
+
+![MCP](../../../assets/iggy_mcp_server.png)

core/bench/README.md

@@ -0,0 +1,7 @@
+# Apache Iggy Bench CLI
+
+The interactive Bench CLI allows you to perform various benchmarking on the Apache Iggy server.
+
+Iggy Bench CLI can be installed with `cargo install iggy-bench` and then simply accessed by typing `iggy-bench` in your terminal.
+
+![CLI](../../assets/bench.png)

core/bench/dashboard/README.md

@@ -18,6 +18,8 @@ A modern, high-performance benchmark results dashboard for Iggy, built with Rust
 - 🚀 High-performance Rust backend
 - ⚡ Fast, modern web frontend built with Yew
 
+![Dashboard](../../../assets/benchmarking_platform.png)
+
 ## Project Structure
 
 The project is organized as a Rust workspace with four main components:

core/cli/README.md

@@ -0,0 +1,9 @@
+# Apache Iggy CLI
+
+The interactive CLI allows you to interact with the Apache Iggy server from the command line.
+
+This is a great addition to the Web UI, especially for all the developers who prefer using the console tools.
+
+Iggy CLI can be installed with `cargo install iggy-cli` and then simply accessed by typing `iggy` in your terminal.
+
+![CLI](../../assets/cli.png)

core/connectors/sinks/README.md

@@ -27,7 +27,7 @@ pub trait Sink: Send + Sync {
 
 ## Configuration
 
-Sink is configured in the default `config` file used by runtime. Each sink configuration, is part of the map of <String, SinkConfig>, which can be represented using toml, json, or yaml.
+Sink is configured in the default `config` file used by runtime. Each sink configuration, is part of the map of `<String, SinkConfig>`, which can be represented using toml, json, or yaml.
 
 ```rust
 pub struct SinkConfig {

core/connectors/sources/README.md

@@ -22,7 +22,7 @@ pub trait Source: Send + Sync {
 
 ## Configuration
 
-Source is configured in the default `config` file used by runtime. Each source configuration, is part of the map of <String, SourceConfig>, which can be represented using toml, json, or yaml.
+Source is configured in the default `config` file used by runtime. Each source configuration, is part of the map of `<String, SourceConfig>`, which can be represented using toml, json, or yaml.
 
 ```rust
 pub struct SourceConfig {

core/server/README.md

@@ -0,0 +1,9 @@
+# Apache Iggy Server
+
+This is the core server component of Apache Iggy. You can run it directly with `cargo run --bin iggy-server --release` or use the Docker image `apache/iggy:latest` (the `edge` tag is for the latest development version).
+
+The configuration file is located at [core/configs/server.toml](https://github.com/apache/iggy/blob/master/core/configs/server.toml). You can customize the server settings by modifying this file or by using environment variables e.g. `IGGY_TCP_ADDRESS=0.0.0.0:8090`.
+
+![Server](../../assets/server.png)
+
+![Architecture](../../assets/iggy_architecture.png)

examples/README.md

@@ -0,0 +1,5 @@
+# Apache Iggy Examples
+
+Here you can find the examples of how to use Apache Iggy with the different programming languages. Please note that the features available in each language may vary.
+
+![Sample](../assets/sample.png)

web/README.md

@@ -1,12 +1,8 @@
-# Apache Iggy (Incubating) Web UI
+# Apache Iggy Web UI
 
-This proejcts hosts the web user interface for Apache Iggy. The web UI is built using SvelteKit.
+This project hosts the web user interface for Apache Iggy. The web UI is built using SvelteKit.
 
-![iggy](static/signIn.png)
-![iggy](static/stats.png)
-![iggy](static/permissions.png)
-![iggy](static/streams.png)
-![iggy](static/streamsLight.png)
+![Web](../assets/web_ui.png)
 
 ## Overview
 
@@ -24,20 +20,20 @@ The Iggy Web UI provides a user-friendly panel for managing various aspects of t
    docker run -p 3000:3000 -p 8090:8090 apache/iggy:latest
    ```
 
-1. **Clone the repository:**
+2. **Clone the repository:**
 
    ```sh
    git clone https://github.com/apache/iggy.git
    ```
 
-1. **Build the project:**
+3. **Build the project:**
 
    ```sh
-   cd iggy-web-ui
+   cd web
    npm install
    ```
 
-1. **Run the project:**
+4. **Run the project:**
 
    ```sh
    npm run dev