- What is folklore/laravel-panneau and what does it do?
- Panneau is a Laravel package for creating administration dashboards and CRUD screens from code-defined resources and fields. In v5 it is the PHP reference implementation of the Panneau protocol, paired with a JavaScript admin client, so it acts as a headless admin backend rather than a Blade dashboard layer.
- Does Panneau support Laravel 11 or older Laravel versions?
- Panneau v5 requires PHP 8.3+ and Laravel 12 or 13. It does not support older Laravel versions, which excludes many existing production applications. Confirm the exact constraints in composer.json before evaluating it for an upgrade.
- How do I install Panneau and does panneau:install modify my app?
- Installation is via Composer, followed by the panneau:install command to publish assets and register the opt-in HTTP routes. The assessment flags that you should verify exactly what the installer changes in routes, middleware, and config before running it in an existing app. Test it in a clean Laravel 12 or 13 application first.
- Is Panneau a Blade or Tailwind dashboard package like Filament?
- No. Panneau v5 is not a Blade, Tailwind, or Alpine dashboard composition layer like earlier versions. It is a headless admin backend that exposes a protocol definition and CRUD endpoints, with rendering handled by the @panneau JavaScript client. That makes it a better fit for SPA or Inertia-style teams and a worse fit for Blade monoliths.
- Do Panneau resources use Eloquent models directly?
- In v5, resources are backed by repositories rather than Eloquent models directly, and ResourceQuery only accepts declared filters and sorts. This is a healthy explicit boundary, but it means adopting Panneau also means adopting its data-access pattern and protocol contract.
- Does Panneau include authentication, roles, or media management?
- No. The v5 alpha does not include authentication flows such as password reset, 2FA, passkeys, or OAuth, and it has no roles module, media API, export/import, or pages and menus in the definition. These are deferred to Phase 2 on the roadmap, so you must supply them yourself or wait.
- How does Panneau handle authorization and concurrent edits?
- Panneau v5 requires policies, validates input before it reaches the repository, and supports ETag and If-Match with HTTP 412 for optimistic concurrency. These are meaningful security improvements, but authorization misconfiguration now has a well-defined blast radius across a JSON API.
- Can I use Panneau with my own frontend instead of the @panneau JS client?
- The package exposes opt-in HTTP routes that return a protocol definition plus list, show, create, update, and delete endpoints. The official path is a JS-rendered admin page using @panneau, but a key open question is whether your own UI can consume the protocol and what support commitment exists for that. Clarify this before committing.
- Is Panneau stable enough for production?
- Treat it as pre-release. The v5 API is alpha and can change before 5.0.0, the PHP and JS packages must move together, and the protocol spec lives in a separate repository outside this package's control. It is also a low-signal package with 2 stars and 0 dependents, and the future-dated release metadata remains unresolved, though the OpenAPI contract tests and conformance kit are strong quality signals.
- How do I migrate from Panneau v4 to v5?
- There is no v4-to-v5 migration guide yet, and the assessment describes v5 as a re-implementation rather than an upgrade. Budget for a rewrite if you have existing v4-style adoption, and confirm whether v4 remains supported while the guide is pending.