chore: clean up spaces and add more links

Author: innocenzi

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

@@ -8,7 +8,7 @@ tag: Release
 
 Two years ago, Tempest started out as an educational project during one of my livestreams. Since then, we've had 56 people contribute to the framework, merged 591 pull requests, resolved 455 issues, and have written around 50k lines of code. Two contributors joined the core team and dedicated a lot of their time to help make Tempest into something real. And today, we're tagging Tempest as beta.
 
-We have to be real though: we won't get it perfect from the start. Tempest is now in beta, which means we don't plan any breaking changes to stable components anymore, but it also means we expect there to be bugs. And this puts us in an underdog position: why would anyone want to use a framework that has fewer features and likely more bugs than other frameworks? 
+We have to be real though: we won't get it perfect from the start. Tempest is now in beta, which means we don't plan any breaking changes to stable components anymore, but it also means we expect there to be bugs. And this puts us in an underdog position: why would anyone want to use a framework that has fewer features and likely more bugs than other frameworks?
 
 It turns out, people _do_ see value in Tempest. It's the only reason I decided to work on it in the first place: there is a group of people who _want_ to use it, even when they are aware of its current shortcomings. There is interest in a framework that embraces modern PHP without 10 to 20 years of legacy to carry with it. There is interest in a project that dares to rethink what we've gotten used to over the years. There already is a dedicated community. People already are building with Tempest. Several core members have real use cases for Tempest and are working hard to be able to use it in their own projects as soon as possible. So while Tempest is the underdog, there already seems enough reason for people to use it today.
 
@@ -62,7 +62,7 @@ use Tempest\Database\IsDatabaseModel;
 final class Book
 {
     use IsDatabaseModel;
-    
+
     // …
 }
 
@@ -97,11 +97,11 @@ $data = query(Book::class)
     ->all();
 ```
 
-We've managed to truly decouple model classes from the persistence layer, while still making them really convenient to use. This is a great example of how Tempest gets out of your way. 
+We've managed to truly decouple model classes from the persistence layer, while still making them really convenient to use. This is a great example of how Tempest gets out of your way.
 
 An important note to make here is that our ORM is one of the few experimental components within Tempest. We acknowledge that there's more work to be done to make it even better, and there might be some future breaking changes still. It's one of the prime examples where we need the community to help us learn what should be improved, and how.
 
-## tempest/view changes
+## `tempest/view` changes
 
 We've added support for [dynamic view components](/main/essentials/views#dynamic-view-components), which allows you to render view components based on runtime data:
 
@@ -120,19 +120,18 @@ We've improved [boolean attributes](/main/essentials/views#boolean-attributes),
 <!-- <div data-active></div> when $isActive is truthy -->
 ```
 
-Finally, we switched from PHP's built-in DOM parser to our custom implementation. We realized that trying to parse tempest/view syntax according to the official HTML spec added more problems than it solved. After all, tempest/view syntax is a superset of HTML: it compiles to spec-compliant HTML, but in itself it is not spec-compliant.
+Finally, we switched from PHP's built-in DOM parser to our custom implementation. We realized that trying to parse {`tempest/view`} syntax according to the official HTML spec added more problems than it solved. After all, {`tempest/view`} syntax is a superset of HTML: it compiles to spec-compliant HTML, but in itself it is not spec-compliant.
 
 Moving to a custom parser written in PHP comes with a small performance price to pay, but our implementation is slightly more performant than [masterminds/html5](https://github.com/Masterminds/html5-php), the most popular PHP-based DOM parser, and everything our parser does is cached as well. You can [check out the implementation here](https://github.com/tempestphp/tempest-framework/tree/main/packages/view/src/Parser).
 
 ## Container features
 
-We've added a new interface called `HasTag`, which allows any object to manually specify its container tag. This feature is especially useful combined with config files, and allows you to define multiple config files for multiple occasions. For example, to define multiple database connections:
-
+We've added a new interface called {b`Tempest\Container\HasTag`}, which allows any object to manually specify its container tag. This feature is especially useful combined with config files, and allows you to define multiple config files for multiple occasions. For example, to define multiple database connections:
 
 ```php
 return new PostgresConfig(
     tag: 'backup',
-    
+
     // …
 );
 ```
@@ -160,7 +159,7 @@ use Tempest\Container\Proxy;
 final readonly class BookController
 {
     public function __construct(
-        #[Proxy] 
+        #[Proxy]
         private VerySlowClass $verySlowClass
     ) { /* … */ }
 }
@@ -205,21 +204,21 @@ final readonly class OverviewMiddleware implements ConsoleMiddleware
 
 ## Smaller features
 
-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: 
+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
+- We've added testing utilities for our [event bus](/main/tempest-in-depth/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, which is a slim wrapper around [Flysystem](https://flysystem.thephpleague.com/docs/)
+- We've added a [new storage component](/main/tempest-in-depth/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
 
 It's amazing to see what we've achieved in a little less than two years. Tempest has grown from being a dummy project used during livestreams, to a real framework.
 
-There's a long way to go still, but I'm confident when I see how many people are contributing to and excited about Tempest. You can follow along the beta progress on [GitHub](https://github.com/tempestphp/tempest-framework/milestone/16); and you can be part of the journey as well: [give Tempest a try](/main/getting-started/getting-started) and [join our Discord server](https://tempestphp.com/discord). 
+There's a long way to go still, but I'm confident when I see how many people are contributing to and excited about Tempest. You can follow along the beta progress on [GitHub](https://github.com/tempestphp/tempest-framework/milestone/16); and you can be part of the journey as well: [give Tempest a try](/main/getting-started/getting-started) and [join our Discord server](https://tempestphp.com/discord).
 
 See you soon!
 
-<img class="w-[1.66em] shadow-md rounded-full" src="/tempest-logo.png" alt="Tempest" />
+<img class="w-[1.66em] shadow-md rounded-full" src="/tempest-logo.png" alt="Tempest" />