## Separate PHP page entry points
- Provide independent PHP entry files for the main navigation pages, utility/form pages, event pages, every catalog category route, and every catalog product route.
- Keep shared branding, navigation, data, catalogue filtering, and templates reusable through the common renderer while preserving direct `.php` URLs.


## Laravel application structure
The project now follows a standard Laravel layout with `app`, `bootstrap`, `config`, `database`, `public`, `resources`, `routes`, `storage`, `tests`, Composer dependencies, and Artisan. `SiteController` owns requests, `LegacyPageRenderer` keeps the current designed pages working during the Blade migration, the catalogue lives under `storage/app/catalog`, and web assets live under `public/assets`. The old thousands of flat PHP wrapper files have been removed; Laravel serves their established `.php` URLs through the catch-all web route.