Merge remote-tracking branch 'origin/main'

Author: brendt

app/Front/Code/code_preview.view.php

@@ -16,6 +16,7 @@
                 html2canvas(screenshot, {
                     allowTaint: true,
                     useCORS: true,
+                    scale: 4,
                 })
                     .then(function (canvas) {
                         screenshot.classList.remove('hero-bg-screenshot');

app/Front/Docs/Content/internals/05-package-development.md

@@ -4,7 +4,7 @@ title: Package Development
 
 Tempest comes with a handful of tools to help third-party package developers.
 
-## `#[DoNotDiscover]`
+## DoNotDiscover
 
 Tempest has an attribute called `#[DoNotDiscover]`, which you can add on classes. Any class within your package that has this attribute won't be discovered by Tempest. You can still use that class internally, or allow you package to publish it (see [installers](#installers)).
 
@@ -139,6 +139,32 @@ Finally, Installers will be discovered by Tempest, so you only need to implement
 
 As you can see in the previous examples, `$this->publishImports()` is always called within the `install()` method. Calling this method will loop over all published files, and adjust any imports that reference to published files. 
 
+## Provider classes
+
+Unlike Symfony or Laravel, Tempest doesn't have a dedicated "service provider" concept. Instead, you're encouraged to rely on discovery and initializers. However, there might be cases where you need to "set up a bunch of things for your package", and you need a place to put that code. 
+
+In order to do that, you're encouraged to simply have an event listener for the `KernelEvent::BOOTED` event. This event is triggered when Tempest's kernel has booted, but before any application code is run. It's the perfect place to hook into Tempest's internals if you need to set up stuff specifically for your package.
+
+```php
+use Tempest\Core\KernelEvent;
+use Tempest\EventBus\EventHandler;
+
+final readonly class MyPackageProvider
+{
+    public function __construct(
+        // You can inject any dependency you like
+        private Container $container,
+    ) {}
+
+    #[EventHandler(KernelEvent::BOOTED)]
+    public function init(): void
+    {
+        // Do whatever needs to be done
+        $this->container->…
+    }
+}
+```
+
 ## Testing helpers
 
 Tempest provides a class called `\Tempest\Framework\Testing\IntegrationTest`. Your PHPUnit tests can extend from it. By doing so, your tests will automatically boot the framework, and have a range of helper methods available.