Project), and I'm a bit unsure about the right way to structure the routes for a nested page.Project model, and each project is accessible via a slug (e.g. /my-cool-project).settings, so that the full path looks like:{project-slug}/settings) be registered via routes.php, or should it be part of the discoverCluster setup?settings under a model-driven path like this?/edit, /analytics, etc., should those also live under the same cluster or be managed differently?discoverCluster usage but it seems limited in terms of defining nested pages.routes config, but it doesn't seem to automatically respect the model context unless I manually fetch the Project by slug.