Skip to content

Commit 65346de

Browse files
committed
updated admin usage page
Signed-off-by: bidi <bidi@apidemia.com>
1 parent 67ecf4d commit 65346de

1 file changed

Lines changed: 4 additions & 7 deletions

File tree

docs/book/v1/admin/usage.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,16 @@
11
# Usage
22

3-
Dotkernel API can be installed independently or together with other applications in the Dotkernel suite, based on your business requirements.
3+
Dotkernel Admin can be installed independently or together with other applications in the Dotkernel suite, based on your business requirements.
44
These components are designed to complement each other (out-of-box they are separate codebases):
55

66
- **Dotkernel API** exposes the content to 3rd-party frontends or backends.
77
- **Dotkernel Admin** (optional) manages the data (create, edit, delete).
88
- **Dotkernel Queue** (optional) queue management microservice.
99

10-
A safe bet is to start with Dotkernel API and integrate it into your existing platform.
11-
The API can manage the access permissions to keep your data secure:
12-
13-
- Admin-level users create and edit the data for your existing backend.
14-
- Regular users read the data for your frontend.
10+
You can start with Dotkernel Admin and integrate it into your existing platform.
11+
The Admin has built-in reports and graphs that can be configured and customized based on your needs.
1512

1613
Later on you can add:
1714

18-
- Dotkernel Admin for its simple table-based approach, its reports and graphs.
15+
- Dotkernel API to handle all data manipulation.
1916
- Dotkernel Queue for its asynchronous task processing.

0 commit comments

Comments
 (0)