Skip to content

Commit 220b8f7

Browse files
alexmerlinalexmerlin
authored
Merge pull request #117 from dotkernel/issue-116
Issue #116: User version-specific images
2 parents 23fff37 + 5f82cd5 commit 220b8f7

16 files changed

+23
-23
lines changed

‎docs/book/v4/flow/default-library-flow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
The graph below demonstrates a default flow between Dotkernel's libraries.
44

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)

‎docs/book/v4/flow/library-flow-for-email.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
The graph below demonstrates the simplified flow between Dotkernel's libraries for sending an email.
44

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)

‎docs/book/v4/flow/middleware-flow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
The graph below demonstrates a default flow between Dotkernel's middlewares.
44

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)

‎docs/book/v4/introduction/file-structure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@ Dotkernel API follows the [PSR-4](https://www.php-fig.org/psr/psr-4/) standards.
44

55
It is a good practice to standardize the file structure of projects.
66

7-
When using Dotkernel API the following structure is installed by default:
7+
When using Dotkernel API, the following structure is installed by default:
88

9-
![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/file-structure-dk-api.png)
9+
![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/v4/file-structure-dk-api.png)
1010

1111
## Main directories
1212

‎docs/book/v4/tutorials/token-authentication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,13 +44,13 @@ The user account with **role** set to both `user` and `guest` with the following
4444

4545
### Note
4646

47-
> The first two steps need to executed only once.
47+
> The first two steps need to be executed only once.
4848
> Access token should be stored and reused for all upcoming requests.
4949
> Refresh token should be stored and used to refresh expired access token.
5050
5151
For a better overview of the flow, see the below image:
5252

53-
![Token authentication flow](https://docs.dotkernel.org/img/api/token-authentication.png)
53+
![Token authentication flow](https://docs.dotkernel.org/img/api/v4/token-authentication.png)
5454

5555
## Generate admin access token
5656

‎docs/book/v5/flow/default-library-flow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
The graph below demonstrates a default flow between Dotkernel's libraries.
44

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/v5/dotkernel-library-flow.png)

‎docs/book/v5/flow/library-flow-for-email.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
The graph below demonstrates the simplified flow between Dotkernel's libraries for sending an email.
44

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/v5/dotkernel-library-flow-email.png)

‎docs/book/v5/flow/middleware-flow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
The graph below demonstrates a default flow between Dotkernel's middlewares.
44

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/v5/dotkernel-middleware-flow.png)

‎docs/book/v5/introduction/file-structure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@ Dotkernel API follows the [PSR-4](https://www.php-fig.org/psr/psr-4/) standards.
44

55
It is a good practice to standardize the file structure of projects.
66

7-
When using Dotkernel API the following structure is installed by default:
7+
When using Dotkernel API, the following structure is installed by default:
88

9-
![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/file-structure-dk-api.png)
9+
![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/v5/file-structure-dk-api.png)
1010

1111
## Special purpose folders
1212

‎docs/book/v5/tutorials/token-authentication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,13 +46,13 @@ The user account with **role** set to both `user` and `guest` with the following
4646

4747
### Note
4848

49-
> The first two steps need to executed only once.
49+
> The first two steps need to be executed only once.
5050
> Access token should be stored and reused for all upcoming requests.
5151
> Refresh token should be stored and used to refresh expired access token.
5252
5353
For a better overview of the flow, see the below image:
5454

55-
![Token authentication flow](https://docs.dotkernel.org/img/api/token-authentication.png)
55+
![Token authentication flow](https://docs.dotkernel.org/img/api/v5/token-authentication.png)
5656

5757
## Generate admin access token
5858

‎docs/book/v6/extended-features/handler-structure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,6 @@ In this way, the developer can easily figure out the functionality of each handl
3838

3939
## Mapping of the handlers
4040

41-
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).
41+
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).
4242

43-
[![naming-convention-thumbnail](https://docs.dotkernel.org/img/api/naming-convention-thumbnail.png)](https://docs.dotkernel.org/img/api/naming-convention.png)
43+
[![naming-convention-thumbnail](https://docs.dotkernel.org/img/api/v6/naming-convention-thumbnail.png)](https://docs.dotkernel.org/img/api/v6/naming-convention.png)

‎docs/book/v6/flow/default-library-flow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
The graph below demonstrates a default flow between Dotkernel's libraries.
44

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/v6/dotkernel-library-flow.png)

‎docs/book/v6/flow/library-flow-for-email.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
The graph below demonstrates the simplified flow between Dotkernel's libraries for sending an email.
44

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/v6/dotkernel-library-flow-email.png)

‎docs/book/v6/flow/middleware-flow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
The graph below demonstrates a default flow between Dotkernel's middlewares.
44

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/v6/dotkernel-middleware-flow.png)

‎docs/book/v6/introduction/file-structure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,9 @@ Dotkernel API follows the [PSR-4](https://www.php-fig.org/psr/psr-4/) standards.
44

55
It is a good practice to standardize the file structure of projects.
66

7-
When using Dotkernel API the following structure is installed by default:
7+
When using Dotkernel API, the following structure is installed by default:
88

9-
![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/file-structure-dk-api.png)
9+
![Dotkernel API File Structure!](https://docs.dotkernel.org/img/api/v6/file-structure-dk-api.png)
1010

1111
## Special purpose folders
1212

‎docs/book/v6/tutorials/token-authentication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,13 +46,13 @@ The user account with **role** set to both `user` and `guest` with the following
4646

4747
### Note
4848

49-
> The first two steps need to executed only once.
49+
> The first two steps need to be executed only once.
5050
> Access token should be stored and reused for all upcoming requests.
5151
> Refresh token should be stored and used to refresh expired access token.
5252
5353
For a better overview of the flow, see the below image:
5454

55-
![Token authentication flow](https://docs.dotkernel.org/img/api/token-authentication.png)
55+
![Token authentication flow](https://docs.dotkernel.org/img/api/v6/token-authentication.png)
5656

5757
## Generate admin access token
5858

0 commit comments

Comments
 (0)