Implement documentation of ci/cd pipeline

* fix review findings

BUILD_PIPELINE.md

@@ -0,0 +1 @@
+![`Build Pipeline`](`documentation/generated-documents/build-pipeline-documentation.png`)

README.md

@@ -11,8 +11,6 @@ The newest build of the shop is deployed [here](https://zeiss.github.io/angular-
 
 To get a better understanding of the style guide example, it is recommended to look into the style guide which is hosted under the repositories [wiki page](https://github.com/ZEISS/angular-styleguide/wiki).
 
-Furthermore, you can find more information about the build and deployment process [here](documentation/generated-documents/build-pipeline-documentation.png).
-
 Almost the entire app is implemented by using the [Standalone Components](https://angular.io/guide/standalone-components) approach. To cover also the classical module-based approach and to showcase the integration of both concepts, the package `catalog` is implemented module-based completely.
 
 ## Development server
@@ -26,6 +24,8 @@ Run `npm run build` to build the project.
 The build artifacts will be stored in the `dist/` directory.
 Use the `--prod` flag for a production build.
 
+Furthermore, you can find more information about the build and deployment process [here](BUILD_PIPELINE.md).
+
 ## Running unit tests
 
 Run `npm test` to execute the unit tests via [Karma](https://karma-runner.github.io).

documentation/pipeline-documentation.puml

@@ -34,7 +34,7 @@ endif
 |Build and Deploy|
 partition Deployment #lightGreen {
   :Deploy recent build and push it to branch 'gh-pages';
-  :This will trigger the action 'pages build & deployment' to host the recent build;
+  :Trigger the action 'pages build & deployment' to host the recent build;
 }
 end
 note right: End of pipeline