wip

Author: brendt

docs/0-getting-started/01-introduction.md

@@ -96,6 +96,10 @@ final class ConsoleCommandDiscovery implements Discovery
 
 Discovery makes Tempest truly understand your codebase so that you don't have to explain the framework how to use it. Of course, discovery is heavily optimized for local development and entirely cached in production, so there's no performance overhead. Even better: discovery isn't just a core framework feature, you're encouraged to write your own project-specific discovery classes wherever they make sense. That's the Tempest way.
 
+:::info
+Read the [getting started with discovery](/blog/discovery-explained) guide if you are new to Tempest.
+:::
+
 Besides Discovery, Tempest is designed to be extensible. You'll find that any part of the framework can be replaced and hooked into by implementing an interface and plugging it into the container. No fighting the framework, Tempest gets out of your way.
 
 ```php

docs/4-internals/02-discovery.md

@@ -3,6 +3,10 @@ title: Discovery
 description: "Learn how Tempest automatically locates controller actions, event handlers, console commands, and other components of your application."
 ---
 
+:::info
+Read the [getting started with discovery](/blog/discovery-explained) guide if you are new to Tempest. 
+:::
+
 ## Overview
 
 Tempest introduces a unique approach to bootstrapping an application. Instead of requiring manual registration of project code and packages, Tempest automatically scans the codebase and detects the components that should be loaded. This process is called **discovery**.