updated content

Author: bidi47

docs/book/v1/admin/introduction.md

@@ -1,5 +1,11 @@
 # Introduction
 
+## Summary
+
+An overview of Dotkernel Admin, a skeleton application for quickly building a database-backed administration site with reports, graphs, and a PSR-compliant middleware stack.
+
+## Details
+
 Dotkernel Admin is an application (skeleton) intended for quickly setting up an administration site for your platform.
 
 Dotkernel Admin:
@@ -9,3 +15,14 @@ Dotkernel Admin:
 - Contains many graphical components to ensure an intuitive user experience.
 - Has a PSR-Compliant Middleware Stack to promote a lean, modular architecture and create a common ground between components from various sources.
 - Implements [PSR-7](https://www.php-fig.org/psr/psr-7/) (HTTP message interfaces) and [PSR-15](https://www.php-fig.org/psr/psr-15/) (HTTP Server Request Handlers) as defined by the [PHP Framework Interop Group](https://www.php-fig.org/).
+
+## FAQ
+
+**Q: What is Dotkernel Admin?**
+A: It's a skeleton application for quickly setting up an administration site to manage records in your database.
+
+**Q: Does Dotkernel Admin include reporting features?**
+A: Yes, it has built-in reports and graphs to help you monitor your platform.
+
+**Q: What standards does Dotkernel Admin implement?**
+A: PSR-7 and PSR-15, as defined by the PHP Framework Interop Group (PHP-FIG).

docs/book/v1/admin/usage.md

@@ -1,5 +1,11 @@
 # Usage
 
+## Summary
+
+Explains how Dotkernel Admin fits alongside Dotkernel API and Dotkernel Queue, and how you can start with Admin alone and add the other components later.
+
+## Details
+
 Dotkernel Admin can be installed independently or together with other applications in the Dotkernel suite, based on your business requirements.
 These components are designed to complement each other (out-of-box they are separate codebases):
 
@@ -14,3 +20,14 @@ Later on you can add:
 
 - Dotkernel API to handle all data manipulation.
 - Dotkernel Queue for its asynchronous task processing.
+
+## FAQ
+
+**Q: Can Dotkernel Admin be used on its own?**
+A: Yes, it can be installed independently and integrated into your existing platform.
+
+**Q: Are Dotkernel Admin, API, and Queue part of the same codebase?**
+A: No, out of the box they are separate codebases designed to complement each other.
+
+**Q: What do Dotkernel API and Dotkernel Queue add to Admin?**
+A: The API handles data manipulation for the platform, and Queue handles asynchronous task processing.

docs/book/v1/api/introduction.md

@@ -1,5 +1,11 @@
 # Introduction
 
+## Summary
+
+An overview of Dotkernel API, the Mezzio-based REST API at the root of the Dotkernel Headless Platform, and its PSR-compliant, standards-based architecture.
+
+## Details
+
 Dotkernel API is a REST API based on the Mezzio skeleton.
 The API is the root or the Dotkernel Headless Platform.
 
@@ -8,3 +14,14 @@ Dotkernel API:
 - Ensures that you build a cohesive system that contains an API-first backend with the same architecture and standards support as other Dotkernel tools and applications.
 - Has a PSR-Compliant Middleware Stack to promote a lean, modular architecture and create a common ground between components from various sources.
 - Implements [PSR-7](https://www.php-fig.org/psr/psr-7/) (HTTP message interfaces) and [PSR-15](https://www.php-fig.org/psr/psr-15/) (HTTP Server Request Handlers) as defined by the [PHP Framework Interop Group](https://www.php-fig.org/).
+
+## FAQ
+
+**Q: What is Dotkernel API built on?**
+A: It's a REST API based on the Mezzio skeleton.
+
+**Q: What role does Dotkernel API play in the Headless Platform?**
+A: It is the root of the Dotkernel Headless Platform.
+
+**Q: What standards does Dotkernel API implement?**
+A: PSR-7 and PSR-15, as defined by the PHP Framework Interop Group (PHP-FIG).

docs/book/v1/api/usage.md

@@ -1,5 +1,11 @@
 # Usage
 
+## Summary
+
+Explains how Dotkernel API fits alongside Dotkernel Admin and Dotkernel Queue, and how to start with API alone and add the other components later.
+
+## Details
+
 Dotkernel API can be installed independently or together with other applications in the Dotkernel suite, based on your business requirements.
 These components are designed to complement each other (out-of-box they are separate codebases):
 
@@ -17,3 +23,14 @@ Later on you can add:
 
 - Dotkernel Admin for its simple table-based approach, its reports and graphs.
 - Dotkernel Queue for its asynchronous task processing.
+
+## FAQ
+
+**Q: Should I start with Dotkernel API or Admin?**
+A: Starting with Dotkernel API is a safe bet since it can manage access permissions to keep your data secure.
+
+**Q: How does Dotkernel API separate admin and regular users?**
+A: Admin-level users create and edit the data, while regular users read the data for your frontend.
+
+**Q: What can I add to Dotkernel API later?**
+A: Dotkernel Admin for its table-based management, reports and graphs, and Dotkernel Queue for asynchronous task processing.

docs/book/v1/config-provider/benefits.md

@@ -1,5 +1,11 @@
 # Benefits
 
+## Summary
+
+Lists the benefits of using a ConfigProvider, including centralized, modular, container-friendly, and testable configuration.
+
+## Details
+
 - **Centralized setup** – Instead of hardcoding bootstrap code, you declare it in a config provider so it's easy to read, change, or extend.
 - **Modular** – Each package can ship with its own config without interfering with others.
 - **Container-friendly** – It works well with frameworks using DI containers like Laminas ServiceManager, PHP-DI, or Pimple.
@@ -8,3 +14,14 @@
 - **Testability** - The consistent, central configuration promotes isolated (e.g. per-module) testing, easier swapping of dependencies and the assertion of pipeline setup (e.g. check if a config key is present).
 
 > **Dotkernel ConfigProviders** have to be **added manually** in `config/config.php`, because all the initial ConfigProviders required to install the applications are already injected.
+
+## FAQ
+
+**Q: Why use a ConfigProvider instead of hardcoding bootstrap code?**
+A: It centralizes configuration so it's easy to read, change, or extend.
+
+**Q: Does a ConfigProvider work with dependency injection containers?**
+A: Yes, it's container-friendly and works with DI containers like Laminas ServiceManager, PHP-DI, or Pimple.
+
+**Q: Do I need to register Dotkernel ConfigProviders manually?**
+A: Yes, Dotkernel ConfigProviders must be added manually in `config/config.php`.

docs/book/v1/config-provider/functionality.md

@@ -1,5 +1,11 @@
 # How the ConfigProvider works
 
+## Summary
+
+Walks through how the ConfigProvider is picked up during bootstrap, merged, resolved, and executed within the Mezzio middleware pipeline.
+
+## Details
+
 The ConfigProvider is automatically picked up by the framework during application bootstrap.
 Let's look at it step by step:
 
@@ -21,3 +27,14 @@ $config = $container->get('config')['key'] ?? [];
 Below you can see how Mezzio and Dotkernel merge and use ConfigProviders to build the middleware pipeline and dependencies.
 
 ![Headless Platform with Core Submodule](https://docs.dotkernel.org/img/headless-platform/ConfigProvider.png)
+
+## FAQ
+
+**Q: When is the ConfigProvider picked up?**
+A: Automatically, by the framework during application bootstrap.
+
+**Q: What happens during the "Resolve item" step?**
+A: `$app->pipe()` resolves a service name from the container, wraps a middleware array, or calls a closure/invokable object.
+
+**Q: Why does the error-handling middleware run last in the pipeline?**
+A: So it can catch any exceptions raised by the preceding middleware.

docs/book/v1/config-provider/introduction.md

@@ -1,5 +1,11 @@
 # Introduction
 
+## Summary
+
+Introduces the `ConfigProvider` class, what it returns, and how it's used across Dotkernel applications and packages, with a code example.
+
+## Details
+
 In PHP, the `ConfigProvider` is a class that is part of an application's bootstrap process.
 It returns an array of configuration, settings, or anything else your application needs.
 In Dotkernel, each application module and package contains a `ConfigProvider` that normally returns:
@@ -51,3 +57,14 @@ All Dotkernel applications and packages use ConfigProviders:
 - [Dotkernel Frontend](https://docs.dotkernel.org/frontend-documentation/)
 - [Dotkernel Light](https://docs.dotkernel.org/light-documentation/)
 - [Dotkernel Packages](https://docs.dotkernel.org/packages/)
+
+## FAQ
+
+**Q: What does a ConfigProvider return in Dotkernel?**
+A: Dependency injection mappings, request handlers, and template file paths.
+
+**Q: Which Dotkernel applications use ConfigProviders?**
+A: Dotkernel API, Admin, Frontend, Light, and Packages all use ConfigProviders.
+
+**Q: Is the Dotkernel ConfigProvider approach specific to Dotkernel?**
+A: No, it follows an approach similar to Laminas/Mezzio.

docs/book/v1/core/benefits.md

@@ -1,5 +1,11 @@
 # Benefits of the Core Submodule
 
+## Summary
+
+Lists the benefits the Core submodule pattern provides as your platform grows, such as scalability and easier onboarding.
+
+## Details
+
 This design pattern ensures:
 
 - Design flexibility.
@@ -10,3 +16,14 @@ This design pattern ensures:
 
 As your platform expands, each new application connects to the Dotkernel Headless Platform via the central API which services everything the other applications require.
 This ensures consistency throughout your platform, while allowing any number of outside connections as requirements arise.
+
+## FAQ
+
+**Q: How does the Core submodule pattern help as a platform grows?**
+A: It provides design flexibility and scalability suited for both enterprise and smaller applications.
+
+**Q: Can multiple developers work on the platform using this pattern?**
+A: Yes, it allows splitting the work across multiple developers.
+
+**Q: How do new applications connect to the platform?**
+A: Each new application connects via the central API, which services everything the other applications require.

docs/book/v1/core/creation.md

@@ -1,5 +1,11 @@
 # Creating a Core Submodule
 
+## Summary
+
+A step-by-step guide to turning the Core module into a Git submodule, including adding, committing, and initializing/updating it.
+
+## Instructions
+
 The full steps for creating a submodule are described in [Git Tools – Submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules).
 
 > There is already a Core module in some of the Dotkernel applications, but it works like any other module (App, Page, or User).
@@ -38,3 +44,17 @@ git submodule update
 ```
 
 > Do not forget to delete the existing Core module before adding the submodule to other applications.
+
+## FAQ
+
+**Q: Where can I find the full steps for creating a Git submodule?**
+A: In the official Git documentation, [Git Tools – Submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules).
+
+**Q: What command creates a submodule in an application?**
+A: `git submodule add <url>`, using the URL of the new Core repository.
+
+**Q: How do I get the submodule after cloning the project?**
+A: Run `git submodule init` followed by `git submodule update`.
+
+**Q: Should I keep the existing Core module after adding the submodule?**
+A: No, delete the existing Core module before adding the submodule to other applications.

docs/book/v1/core/introduction.md

@@ -1,5 +1,11 @@
 # Introduction
 
+## Summary
+
+Introduces the Core submodule as the shared codebase and single source of truth for database entities across Dotkernel applications.
+
+## Details
+
 The Core submodule is a common codebase set up to be used by the Dotkernel applications you added to your project.
 The project setup may differ - e.g. two APIs, one Admin, 3 Frontends - but the Core submodule can be included in all of them.
 
@@ -13,3 +19,14 @@ General rules:
 - The current location of the Core submodule is `src/Core`.
 
 [Shared Core Submodule in Dotkernel Headless Platform](https://www.dotkernel.com/headless-platform/shared-core-submodule-in-dotkernel-headless-platform/)
+
+## FAQ
+
+**Q: Can the same Core submodule be used across multiple applications?**
+A: Yes, it can be included in any combination of APIs, Admins, and Frontends in your project.
+
+**Q: What is the golden rule for the Core codebase?**
+A: It's the only place that manages the database entities.
+
+**Q: Where is the Core submodule located?**
+A: At `src/Core`.