Skip to content

Issue #116: User version-specific images #117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 25, 2025
Merged

Issue #116: User version-specific images #117

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/book/v4/flow/default-library-flow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
2 changes: 1 addition & 1 deletion docs/book/v4/flow/library-flow-for-email.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
2 changes: 1 addition & 1 deletion docs/book/v4/flow/middleware-flow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
4 changes: 2 additions & 2 deletions docs/book/v4/introduction/file-structure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions docs/book/v4/tutorials/token-authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
2 changes: 1 addition & 1 deletion docs/book/v5/flow/default-library-flow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
2 changes: 1 addition & 1 deletion docs/book/v5/flow/library-flow-for-email.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
2 changes: 1 addition & 1 deletion docs/book/v5/flow/middleware-flow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
4 changes: 2 additions & 2 deletions docs/book/v5/introduction/file-structure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions docs/book/v5/tutorials/token-authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions docs/book/v6/extended-features/handler-structure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
2 changes: 1 addition & 1 deletion docs/book/v6/flow/default-library-flow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
2 changes: 1 addition & 1 deletion docs/book/v6/flow/library-flow-for-email.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
2 changes: 1 addition & 1 deletion docs/book/v6/flow/middleware-flow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
4 changes: 2 additions & 2 deletions docs/book/v6/introduction/file-structure.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
4 changes: 2 additions & 2 deletions docs/book/v6/tutorials/token-authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down