fix: even more dead links

Author: innocenzi

src/Web/Blog/articles/2024-10-02-alpha-2.md

@@ -99,7 +99,7 @@ final readonly class RssController
 }
 ```
 
-You can read all the details about caching [in the docs](/main/tempest-in-depth/caching).
+You can read all the details about caching [in the docs](/main/features/cache).
 
 ## Discovery improvements
 

src/Web/Blog/articles/2024-11-25-alpha-4.md

@@ -11,7 +11,7 @@ I'll share some more updates about the coming months at the end of this post, bu
 
 ## Asynchronous Commands
 
-Async commands are a new feature in Tempest that allow developers to handle tasks in a background process. Tempest already came with a [command bus](/main/tempest-in-depth/commands) before this release, and running commands asynchronously is as easy as adding the `#[AsyncCommand]` attribute to a command class.
+Async commands are a new feature in Tempest that allow developers to handle tasks in a background process. Tempest already came with a [command bus](/main/essentials/console-commands) before this release, and running commands asynchronously is as easy as adding the `#[AsyncCommand]` attribute to a command class.
 
 ```php
 // app/SendMail.php

src/Web/Blog/articles/2025-03-13-request-objects-in-tempest.md

@@ -24,7 +24,7 @@ final class BookData
 }
 ```
 
-It doesn't get much simpler than this, right? We have an object representing the fields we expect from the request. Now how do we get the request data into that object? There are several ways of doing so. I'll start by showing the most verbose way, mostly to understand what's going on. This approach makes use of the `map()` function. Tempest has a built-in [mapper component](/main/2-tempest-in-depth/01-mapper), which is responsible to map data from one point to another. It could from an array to an object, object to json, one class to another, … Or, in our case: the request to our data object.
+It doesn't get much simpler than this, right? We have an object representing the fields we expect from the request. Now how do we get the request data into that object? There are several ways of doing so. I'll start by showing the most verbose way, mostly to understand what's going on. This approach makes use of the `map()` function. Tempest has a built-in [mapper component](/main/features/mapper), which is responsible to map data from one point to another. It could from an array to an object, object to json, one class to another, … Or, in our case: the request to our data object.
 
 Here's what that looks like in practice:
 

src/Web/Blog/articles/2025-05-08-beta-1.md

@@ -207,10 +207,10 @@ final readonly class OverviewMiddleware implements ConsoleMiddleware
 Finishing with a couple of smaller changes, but it's these kinds of small details that make the difference in the long run. So thanks to everyone who contributed:
 
 - We've added a couple of new commands: `make:migration` and `container:show`
-- We've added testing utilities for our [event bus](/main/tempest-in-depth/events)
+- We've added testing utilities for our [event bus](/main/features/events)
 - There's a new `Back` response class to redirect to the previous page
 - We now allow controllers to also return strings and arrays directly
-- We've added a [new storage component](/main/tempest-in-depth/storage), which is a slim wrapper around [Flysystem](https://flysystem.thephpleague.com/docs/)
+- We've added a [new storage component](/main/features/file-storage), which is a slim wrapper around [Flysystem](https://flysystem.thephpleague.com/docs/)
 - And, [a lot more](https://github.com/tempestphp/tempest-framework/releases/tag/v1.0.0-beta.1)
 
 ## In closing

src/Web/Documentation/content/main/0-getting-started/01-introduction.md

@@ -37,7 +37,7 @@ final readonly class BookController
 }
 ```
 
-The above snippet is an example of a controller. It features [attribute-based routes](../1-essentials/02-controllers), mapping a request to a data object using the [mapper](../2-tempest-in-depth/01-mapper), [URL generation](../1-essentials/02-controllers#generating-uris) and [dependency injection](../1-essentials/01-container#autowired-dependencies).
+The above snippet is an example of a controller. It features [attribute-based routes](../1-essentials/01-routing.md), mapping a request to a data object using the [mapper](../2-features/01-mapper.md), [URL generation](../1-essentials/01-routing.md#generating-uris) and [dependency injection](../1-essentials/05-container.md#autowired-dependencies).
 
 ```php
 use Tempest\Console\Console;
@@ -85,7 +85,7 @@ final readonly class MigrateUpCommand
 
 This is a [console command](../3-console/02-building-console-commands). Console commands can be defined in any class, as long as the {b`#[Tempest\Console\ConsoleCommand]`} attribute is used on a method. Command arguments are defined as the method's arguments, effectively removing the need to learn some specific framework syntax.
 
-This example also shows how to [register events globally](../2-tempest-in-depth/03-events) using the {b`#[Tempest\EventBus\EventHandler]`}.
+This example also shows how to [register events globally](../2-features/08-events.md) using the {b`#[Tempest\EventBus\EventHandler]`}.
 
 ---
 

src/Web/Documentation/content/main/1-essentials/03-database.md

@@ -93,7 +93,7 @@ final class Book
 }
 ```
 
-Such a model is not tied to the database. Tempest's [mapper](../2-tempest-in-depth/01-mapper) is able to map data from many different sources to such a model. For instance, you can specify the path to a JSON file or object to create an instance of a model, and the other way around.
+Such a model is not tied to the database. Tempest's [mapper](../2-features/01-mapper.md) is able to map data from many different sources to such a model. For instance, you can specify the path to a JSON file or object to create an instance of a model, and the other way around.
 
 ```php
 use function Tempest\map;

src/Web/Documentation/content/main/2-features/05-asset-bundling.md

@@ -162,7 +162,7 @@ final class ConfigureViteNonce implements HttpMiddleware
 }
 ```
 
-The `register` method above is an [event handler](../2-tempest-in-depth/07-events) that is called when Tempest boots. It registers the middleware on the injected {`Tempest\Router\Router`} instance, effectively registering it for every route.
+The `register` method above is an [event handler](../2-features/08-events.md) that is called when Tempest boots. It registers the middleware on the injected {`Tempest\Router\Router`} instance, effectively registering it for every route.
 
 Alternatively, you may also set the `nonce` directly in the event handler. However, keep in mind that this would be called every time the framework boots, even when only using console commands.