diff --git a/.markdownlint.json b/.markdownlint.json
new file mode 100644
index 00000000..6975f887
--- /dev/null
+++ b/.markdownlint.json
@@ -0,0 +1,6 @@
+{
+ "default": true,
+ "MD013": false,
+ "MD014": false,
+ "MD033": false
+}
diff --git a/doc/book/application-integration/usage-in-a-laminas-mvc-application.md b/doc/book/application-integration/usage-in-a-laminas-mvc-application.md
new file mode 100644
index 00000000..c3c96175
--- /dev/null
+++ b/doc/book/application-integration/usage-in-a-laminas-mvc-application.md
@@ -0,0 +1,106 @@
+# Usage in a laminas-mvc Application
+
+The following example shows _one_ potential use case of laminas-eventmanager within
+a laminas-mvc based application.
+The example creates a listener for logging errors of an application with [laminas-log](https://docs.laminas.dev/laminas-log/).
+
+Before starting, make sure laminas-log is [installed and configured](https://docs.laminas.dev/laminas-log/installation/).
+
+laminas-eventmanager is already present in laminas-mvc based applications as it is an event-driven MVC layer based on the event manager.
+
+## Create Listener
+
+Create [a listener aggregate](../aggregates.md) that defines and registers a listener, using a logger injected via its constructor to create a valid object with all required dependencies; as an example, consider the following definition in the file `module/Application/src/Listener/ErrorListener.php`:
+
+```php
+namespace Application\Listener;
+
+use Exception;
+use Laminas\EventManager\AbstractListenerAggregate;
+use Laminas\EventManager\EventManagerInterface;
+use Laminas\Log\Logger;
+use Laminas\Mvc\MvcEvent;
+
+final class ErrorListener extends AbstractListenerAggregate
+{
+ public function __construct(
+ private readonly Logger $logger
+ ) {}
+
+ public function attach(EventManagerInterface $events, $priority = 1): void
+ {
+ $this->listeners[] = $events->attach(
+ MvcEvent::EVENT_DISPATCH_ERROR,
+ [$this, 'onDispatchError']
+ );
+ }
+
+ public function onDispatchError(MvcEvent $event): void
+ {
+ /** @var Exception|null $exception */
+ $exception = $event->getParam('exception');
+ if ($exception) {
+ $this->logger->crit('Error: ' . $exception->getMessage());
+ } else {
+ $this->logger->crit('Error: ' . $event->getError());
+ }
+ }
+}
+```
+
+The listener aggregate was chosen because it is capable of [listening to multiple events](../aggregates.md#recommendations), which could prove useful in the future.
+
+NOTE: **More Events**
+All laminas-mvc events that can be triggered are listed and explained in the [laminas-mvc documentation](https://docs.laminas.dev/laminas-mvc/mvc-event/).
+
+## Register Listener
+
+To register a listener in a laminas-mvc based application, use either application or module configuration (such as `config/autoload/global.php` or `module/Application/config/module.config.php`, respectively), and define the configuration key `listeners`.
+
+This example uses module configuration, e.g. `module/Application/config/module.config.php`:
+
+
+namespace Application;
+
+return [
+ 'listeners' => [
+ Listener\ErrorListener::class,
+ ],
+ // …
+];
+
+
+All listeners registered in this way are fetched from the application service container.
+This means the listeners must be registered for the application service container to discover and create them.
+
+To register the listener for the application service container, extend the configuration of the module.
+Add the following lines to the module configuration file, e.g. `module/Application/config/module.config.php`:
+
+
+namespace Application;
+
+use Laminas\ServiceManager\AbstractFactory\ReflectionBasedAbstractFactory;
+
+return [
+ 'service_manager' => [
+ 'factories' => [
+ Listener\ErrorListener::class => ReflectionBasedAbstractFactory::class,
+ ],
+ ],
+ // …
+];
+
+
+The example uses the [reflection factory from laminas-servicemanager](https://docs.laminas.dev/laminas-servicemanager/reflection-abstract-factory/) to resolve the constructor dependencies for the listener class.
+
+If the listener has no dependencies, use the [factory `Laminas\ServiceManager\Factory\InvokableFactory`](https://docs.laminas.dev/laminas-servicemanager/configuring-the-service-manager/#factories).
+
+## Logging Message
+
+To log a message, produce a [dispatch error](https://docs.laminas.dev/laminas-mvc/mvc-event/#mvceventevent_dispatch_error-dispatcherror) by navigating to `http://localhost:8080/1234`, where a 404 page should be displayed.
+The attached listener will log a message and write it to the registered storage backend(s).
+
+## Learn More
+
+- [Listener Aggregates](../aggregates.md)
+- [The MvcEvent](https://docs.laminas.dev/laminas-mvc/mvc-event/)
diff --git a/doc/book/index.md b/doc/book/index.md
deleted file mode 120000
index fe840054..00000000
--- a/doc/book/index.md
+++ /dev/null
@@ -1 +0,0 @@
-../../README.md
\ No newline at end of file
diff --git a/doc/book/index.md b/doc/book/index.md
new file mode 100644
index 00000000..fcea8161
--- /dev/null
+++ b/doc/book/index.md
@@ -0,0 +1,21 @@
+## Installation
+
+### Using Composer
+
+```bash
+$ composer require laminas/laminas-eventmanager
+```
+
+## Learn
+
+
diff --git a/mkdocs.yml b/mkdocs.yml
index 1a3c31c4..50af5f86 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -16,6 +16,8 @@ nav:
- LazyListenerAggregate: lazy-listeners/lazy-listener-aggregate.md
- "EventManager API": api.md
- "Intercepting Filters": intercepting-filters.md
+ - "Application Integration":
+ - "Usage in a laminas-mvc Application": application-integration/usage-in-a-laminas-mvc-application.md
- "Migration Guide":
- Intro: migration/intro.md
- "Removed Functionality": migration/removed.md
@@ -25,3 +27,4 @@ site_description: 'Implement events, signal slots, aspects, and observers!'
repo_url: 'https://github.com/laminas/laminas-eventmanager'
extra:
project: Components
+ show_special_homepage: true