How it works
- The routes are registered through Filament's own
Resource::registerRoutes(), inside each resource's route group: slug, cluster, parent resource and tenant are handled by Filament. - The page class of a resource is written on demand to
storage/framework/cache, the way Laravel's real-time facades work, and registered with Livewire. It works withroute:cache. - The relation page embeds the relation manager as Filament does in the tabs, so its state, actions and modals stay in the relation manager.