You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/Web/Blog/articles/2025-05-26-tempests-vision.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,7 +69,7 @@ And a lot more.
69
69
70
70
A core part of Tempest's philosophy is that it wants to "get out of your way" as best as possible. For starters, Tempest is designed to structure project code however you want, without making any assumptions or forcing conventions on you. You can prefer a classic MVC application, DDD or hexagonal design, microservices, or something else; Tempest works with any project structure out of the box without any configuration.
71
71
72
-
Behind Tempest's flexibility is one of its most powerful features: [discovery](../internals/discovery). Discovery gives Tempest a great number of insights into your codebase, without any handholding. Discovery handles routing, console commands, view components, event listeners, command handlers, middleware, schedules, migrations, and more.
72
+
Behind Tempest's flexibility is one of its most powerful features: [discovery](/main/internals/discovery). Discovery gives Tempest a great number of insights into your codebase, without any handholding. Discovery handles routing, console commands, view components, event listeners, command handlers, middleware, schedules, migrations, and more.
73
73
74
74
```php
75
75
final class ConsoleCommandDiscovery implements Discovery
Finally, since Tempest originated as an educational project, many Tempest features dare to rethink the things we've gotten used to. For example, [console commands](../1-essentials/04-console-commands), which in Tempest are designed to be very similar to controller actions:
113
+
Finally, since Tempest originated as an educational project, many Tempest features dare to rethink the things we've gotten used to. For example, [console commands](/main/1-essentials/04-console-commands), which in Tempest are designed to be very similar to controller actions:
114
114
115
115
```php
116
116
final readonly class BooksCommand
@@ -136,7 +136,7 @@ final readonly class BooksCommand
136
136
}
137
137
```
138
138
139
-
Or what about [Tempest's ORM](../1-essentials/03-database), which aims to have truly decoupled models:
139
+
Or what about [Tempest's ORM](/main/1-essentials/03-database), which aims to have truly decoupled models:
0 commit comments