Merge pull request #117 from dotkernel/issue-116

alexmerlin · web-flow · commit 220b8f7168d9 · 2025-06-25T10:31:55.000+03:00
Issue #116: User version-specific images
diff --git a/docs/book/v4/flow/default-library-flow.md b/docs/book/v4/flow/default-library-flow.md
@@ -2,4 +2,4 @@
 
 The graph below demonstrates a default flow between Dotkernel's libraries.
 
-![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/dotkernel-library-flow.png)
+![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/v4/dotkernel-library-flow.png)
diff --git a/docs/book/v4/flow/library-flow-for-email.md b/docs/book/v4/flow/library-flow-for-email.md
@@ -2,4 +2,4 @@
 
 The graph below demonstrates the simplified flow between Dotkernel's libraries for sending an email.
 
-![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/dotkernel-library-flow-email.png)
+![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/v4/dotkernel-library-flow-email.png)
diff --git a/docs/book/v4/flow/middleware-flow.md b/docs/book/v4/flow/middleware-flow.md
@@ -2,4 +2,4 @@
 
 The graph below demonstrates a default flow between Dotkernel's middlewares.
 
-![Dotkernel API Middleware Flow!](https://docs.dotkernel.org/img/api/dotkernel-middleware-flow.png)
+![Dotkernel API Middleware Flow!](https://docs.dotkernel.org/img/api/v4/dotkernel-middleware-flow.png)
diff --git a/docs/book/v4/introduction/file-structure.md b/docs/book/v4/introduction/file-structure.md
@@ -4,9 +4,9 @@ Dotkernel API follows the [PSR-4](https://www.php-fig.org/psr/psr-4/) standards.
 
 It is a good practice to standardize the file structure of projects.
 
-When using Dotkernel API the following structure is installed by default:
+When using Dotkernel API, the following structure is installed by default:
 
-![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/file-structure-dk-api.png)
+![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/v4/file-structure-dk-api.png)
 
 ## Main directories
 
diff --git a/docs/book/v4/tutorials/token-authentication.md b/docs/book/v4/tutorials/token-authentication.md
@@ -44,13 +44,13 @@ The user account with **role** set to both `user` and `guest` with the following
 
 ### Note
 
-> The first two steps need to executed only once.
+> The first two steps need to be executed only once.
 > Access token should be stored and reused for all upcoming requests.
 > Refresh token should be stored and used to refresh expired access token.
 
 For a better overview of the flow, see the below image:
 
-![Token authentication flow](https://docs.dotkernel.org/img/api/token-authentication.png)
+![Token authentication flow](https://docs.dotkernel.org/img/api/v4/token-authentication.png)
 
 ## Generate admin access token
 
diff --git a/docs/book/v5/flow/default-library-flow.md b/docs/book/v5/flow/default-library-flow.md
@@ -2,4 +2,4 @@
 
 The graph below demonstrates a default flow between Dotkernel's libraries.
 
-![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/dotkernel-library-flow.png)
+![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/v5/dotkernel-library-flow.png)
diff --git a/docs/book/v5/flow/library-flow-for-email.md b/docs/book/v5/flow/library-flow-for-email.md
@@ -2,4 +2,4 @@
 
 The graph below demonstrates the simplified flow between Dotkernel's libraries for sending an email.
 
-![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/dotkernel-library-flow-email.png)
+![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/v5/dotkernel-library-flow-email.png)
diff --git a/docs/book/v5/flow/middleware-flow.md b/docs/book/v5/flow/middleware-flow.md
@@ -2,4 +2,4 @@
 
 The graph below demonstrates a default flow between Dotkernel's middlewares.
 
-![Dotkernel API Middleware Flow!](https://docs.dotkernel.org/img/api/dotkernel-middleware-flow.png)
+![Dotkernel API Middleware Flow!](https://docs.dotkernel.org/img/api/v5/dotkernel-middleware-flow.png)
diff --git a/docs/book/v5/introduction/file-structure.md b/docs/book/v5/introduction/file-structure.md
@@ -4,9 +4,9 @@ Dotkernel API follows the [PSR-4](https://www.php-fig.org/psr/psr-4/) standards.
 
 It is a good practice to standardize the file structure of projects.
 
-When using Dotkernel API the following structure is installed by default:
+When using Dotkernel API, the following structure is installed by default:
 
-![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/file-structure-dk-api.png)
+![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/v5/file-structure-dk-api.png)
 
 ## Special purpose folders
 
diff --git a/docs/book/v5/tutorials/token-authentication.md b/docs/book/v5/tutorials/token-authentication.md
@@ -46,13 +46,13 @@ The user account with **role** set to both `user` and `guest` with the following
 
 ### Note
 
-> The first two steps need to executed only once.
+> The first two steps need to be executed only once.
 > Access token should be stored and reused for all upcoming requests.
 > Refresh token should be stored and used to refresh expired access token.
 
 For a better overview of the flow, see the below image:
 
-![Token authentication flow](https://docs.dotkernel.org/img/api/token-authentication.png)
+![Token authentication flow](https://docs.dotkernel.org/img/api/v5/token-authentication.png)
 
 ## Generate admin access token
 
diff --git a/docs/book/v6/extended-features/handler-structure.md b/docs/book/v6/extended-features/handler-structure.md
@@ -38,6 +38,6 @@ In this way, the developer can easily figure out the functionality of each handl
 
 ## Mapping of the handlers
 
-The full mapping of the handlers and their current paths and actions can be found [**here**](https://docs.dotkernel.org/img/api/naming-convention.png).
+The full mapping of the handlers and their current paths and actions can be found [**here**](https://docs.dotkernel.org/img/api/v6/naming-convention.png).
 
-[![naming-convention-thumbnail](https://docs.dotkernel.org/img/api/naming-convention-thumbnail.png)](https://docs.dotkernel.org/img/api/naming-convention.png)
+[![naming-convention-thumbnail](https://docs.dotkernel.org/img/api/v6/naming-convention-thumbnail.png)](https://docs.dotkernel.org/img/api/v6/naming-convention.png)
diff --git a/docs/book/v6/flow/default-library-flow.md b/docs/book/v6/flow/default-library-flow.md
@@ -2,4 +2,4 @@
 
 The graph below demonstrates a default flow between Dotkernel's libraries.
 
-![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/dotkernel-library-flow.png)
+![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/v6/dotkernel-library-flow.png)
diff --git a/docs/book/v6/flow/library-flow-for-email.md b/docs/book/v6/flow/library-flow-for-email.md
@@ -2,4 +2,4 @@
 
 The graph below demonstrates the simplified flow between Dotkernel's libraries for sending an email.
 
-![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/dotkernel-library-flow-email.png)
+![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/v6/dotkernel-library-flow-email.png)
diff --git a/docs/book/v6/flow/middleware-flow.md b/docs/book/v6/flow/middleware-flow.md
@@ -2,4 +2,4 @@
 
 The graph below demonstrates a default flow between Dotkernel's middlewares.
 
-![Dotkernel API Middleware Flow!](https://docs.dotkernel.org/img/api/dotkernel-middleware-flow.png)
+![Dotkernel API Middleware Flow!](https://docs.dotkernel.org/img/api/v6/dotkernel-middleware-flow.png)
diff --git a/docs/book/v6/introduction/file-structure.md b/docs/book/v6/introduction/file-structure.md
@@ -4,9 +4,9 @@ Dotkernel API follows the [PSR-4](https://www.php-fig.org/psr/psr-4/) standards.
 
 It is a good practice to standardize the file structure of projects.
 
-When using Dotkernel API the following structure is installed by default:
+When using Dotkernel API, the following structure is installed by default:
 
-![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/file-structure-dk-api.png)
+![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/v6/file-structure-dk-api.png)
 
 ## Special purpose folders
 
diff --git a/docs/book/v6/tutorials/token-authentication.md b/docs/book/v6/tutorials/token-authentication.md
@@ -46,13 +46,13 @@ The user account with **role** set to both `user` and `guest` with the following
 
 ### Note
 
-> The first two steps need to executed only once.
+> The first two steps need to be executed only once.
 > Access token should be stored and reused for all upcoming requests.
 > Refresh token should be stored and used to refresh expired access token.
 
 For a better overview of the flow, see the below image:
 
-![Token authentication flow](https://docs.dotkernel.org/img/api/token-authentication.png)
+![Token authentication flow](https://docs.dotkernel.org/img/api/v6/token-authentication.png)
 
 ## Generate admin access token
 

Original file line number	Diff line number	Diff line change
`@@ -2,4 +2,4 @@`
`2`	`2`
`3`	`3`	`The graph below demonstrates a default flow between Dotkernel's libraries.`
`4`	`4`
`5`		`-![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/dotkernel-library-flow.png)`
	`5`	`+![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/v4/dotkernel-library-flow.png)`
Original file line number	Diff line number	Diff line change
`@@ -2,4 +2,4 @@`
`2`	`2`
`3`	`3`	`The graph below demonstrates the simplified flow between Dotkernel's libraries for sending an email.`
`4`	`4`
`5`		`-![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/dotkernel-library-flow-email.png)`
	`5`	`+![Dotkernel API Default Library Flow!](https://docs.dotkernel.org/img/api/v4/dotkernel-library-flow-email.png)`
Original file line number	Diff line number	Diff line change
`@@ -2,4 +2,4 @@`
`2`	`2`
`3`	`3`	`The graph below demonstrates a default flow between Dotkernel's middlewares.`
`4`	`4`
`5`		`-![Dotkernel API Middleware Flow!](https://docs.dotkernel.org/img/api/dotkernel-middleware-flow.png)`
	`5`	`+![Dotkernel API Middleware Flow!](https://docs.dotkernel.org/img/api/v4/dotkernel-middleware-flow.png)`