rescale images, introduction.md

Signed-off-by: Howriq <[email protected]>

Author: Howriq

docs/book/v1/chapter-1.md

@@ -5,6 +5,8 @@
 The first step is to add alongside your current packages the required entries for our Doctrine installation.
 We would add the following to our `composer.json` file located in our root folder:
 
+![composer.json](images/composer.png)
+
 ```text
 "dotkernel/dot-cache": "^4.0",
 "ramsey/uuid": "^4.5.0",
@@ -45,6 +47,8 @@ After successfully installing our dependencies we now need to configure our Doct
 
 In the file `config/autoload/local.php` the structure would be updated like this:
 
+![local.php](images/local.png)
+
 ```php
 $databases = [
     'default' => [
@@ -80,6 +84,10 @@ This package takes all the provided configs from the `config/config.php` file an
 
 Our new `src/App/src/ConfigProvider.php` class would look like this now:
 
+![config-provider-1](images/config-provider-1.png)
+
+![config-provider-1](images/config-provider-2.png)
+
 ```php
 public function __invoke(): array
 {
@@ -191,6 +199,8 @@ return DependencyFactory::fromEntityManager(
 Now that everything has been configured we only need to do one last thing, to create an executable for the Doctrine CLI.
 In our case we will create a `doctrine` file inside the application's `bin` directory:
 
+![doctrine](images/doctrine.png)
+
 ```php
 #!/usr/bin/env php
 <?php
@@ -214,6 +224,8 @@ ConsoleRunner::run(new SingleManagerProvider($entityManager));
 (Optional) To keep things tidy, we recommend making an executable for the migrations of Doctrine as well.
 For this, we create `doctrine-migrations` file inside the application's `bin` directory:
 
+![doctrine-migrations](images/doctrine-migrations.png)
+
 ```php
 #!/usr/bin/env php
 <?php