From 9729194b51b33c91529a8d07742d1d46194ad2e5 Mon Sep 17 00:00:00 2001
From: Robert McNees <86265089+robertmcnees@users.noreply.github.com>
Date: Wed, 3 Jul 2024 07:21:45 -0400
Subject: [PATCH] Added image folder to attempt to render images properly in
 guide (#9)

---
 README.adoc                                         |  10 +++++-----
 .../output-processor-sink.png                       | Bin
 output-sink.png => images/output-sink.png           | Bin
 .../rabbitmq-processor.png                          | Bin
 rabbitmq-sink.png => images/rabbitmq-sink.png       | Bin
 .../stream-applications-layered-architecture.png    | Bin
 6 files changed, 5 insertions(+), 5 deletions(-)
 rename output-processor-sink.png => images/output-processor-sink.png (100%)
 rename output-sink.png => images/output-sink.png (100%)
 rename rabbitmq-processor.png => images/rabbitmq-processor.png (100%)
 rename rabbitmq-sink.png => images/rabbitmq-sink.png (100%)
 rename stream-applications-layered-architecture.png => images/stream-applications-layered-architecture.png (100%)

diff --git a/README.adoc b/README.adoc
index 43f0108..c9840b2 100644
--- a/README.adoc
+++ b/README.adoc
@@ -39,7 +39,7 @@ For this example, the names of the applications follow the Spring Cloud Stream c
 to the logical equivalent of the Java 8 functions (`Supplier`, `Function`, `Consumer`, respectively).
 While Spring Cloud Stream can support one or more Function instances in a Source as well as in a Sink (via function composition), we have three separate applications to demonstrate how each can work as an independent application.
 
-image::stream-applications-layered-architecture.png[]
+image::images/stream-applications-layered-architecture.png[]
 
 In this guide, we work from the back to the front. That is, we first build the Sink application, followed by the Processor, and
 finally build the Source. We use the RabbitMQ dashboard UI to test each component as we go.
@@ -79,11 +79,11 @@ include::name-sink/src/main/resources/application.properties[tag=sinkexchangecon
 
 To test the sink, we manually publish a JSON message representing a `Person` record to the newly generated exchange:
 
-image::rabbitmq-sink.png[]
+image::images/rabbitmq-sink.png[]
 
 Also, in our application logs we should see the data outputted:
 
-image::output-sink.png[]
+image::images/output-sink.png[]
 
 
 
@@ -114,11 +114,11 @@ NOTE: The output of the processor matches the input of the sink.
 
 Using the RabbitMQ dashboard, we can now send a String (name) to the processor input exchange and watch as it flows to the connected sink.
 
-image::rabbitmq-processor.png[]
+image::images/rabbitmq-processor.png[]
 
 If the processor and the sink are connected properly, you should see the output from your running sink:
 
-image::output-processor-sink.png[]
+image::images/output-processor-sink.png[]
 
 == Source Application
 
diff --git a/output-processor-sink.png b/images/output-processor-sink.png
similarity index 100%
rename from output-processor-sink.png
rename to images/output-processor-sink.png
diff --git a/output-sink.png b/images/output-sink.png
similarity index 100%
rename from output-sink.png
rename to images/output-sink.png
diff --git a/rabbitmq-processor.png b/images/rabbitmq-processor.png
similarity index 100%
rename from rabbitmq-processor.png
rename to images/rabbitmq-processor.png
diff --git a/rabbitmq-sink.png b/images/rabbitmq-sink.png
similarity index 100%
rename from rabbitmq-sink.png
rename to images/rabbitmq-sink.png
diff --git a/stream-applications-layered-architecture.png b/images/stream-applications-layered-architecture.png
similarity index 100%
rename from stream-applications-layered-architecture.png
rename to images/stream-applications-layered-architecture.png