Reorganise content

Author: jnonino

…og/continuous-delivery/cd_process.en.png …inuous-delivery/images/cd_process.en.pngcontent/blog/continuous-delivery/cd_process.en.png renamed to content/blog/continuous-delivery/images/cd_process.en.png content/blog/continuous-delivery/cd_process.en.png renamed to content/blog/continuous-delivery/images/cd_process.en.png

@@ -29,7 +29,7 @@ Much like in [Continuous Integration]({{< ref "blog/continuous-integration" >}})
 The following figure illustrates the fundamental steps of a Continuous Delivery (CD) process. It's vital to note that an effective CD process presupposes a well-oiled [Continuous Integration (CI)]({{< ref "blog/continuous-integration" >}}) system as its foundation.
 
 {{< figure
-    src="cd_process.png"
+    src="images/cd_process.png"
     alt="CD process flowchart"
     caption="Figure 1: CD process flowchart"
     >}}

content/blog/continuous-delivery/index.en.md

@@ -55,7 +55,7 @@ A basic Continuous Integration (CI) pipeline initiates when a new code change is
 *In computer science, a "pipeline" refers to a sequence of processes or tasks linked such that the output of one becomes the input for the next.*
 
 {{< figure
-    src="ci_elements.png"
+    src="images/ci_elements.png"
     alt="Basic elements of CI"
     caption="Figure 1: Basic elements of CI"
     >}}
@@ -77,7 +77,7 @@ Every CI system should have a **notification mechanism** to relay results to the
 The figure below broadly illustrates the stages of the integration process taking place within the Continuous Integration (CI) system.
 
 {{< figure
-    src="ci_process.png"
+    src="images/ci_process.png"
     alt="CI process flowchart"
     caption="Figure 2: CI process flowchart"
     >}}