- How do I install panelis-php/cms in a Laravel application?
- Install it with composer require panelis-php/cms and rely on Laravel package auto-discovery for the service provider. Then publish the package's config, assets, and migrations using its documented vendor:publish commands, and register the navigation groups in your admin panel. Confirm the exact install steps and publish tags in the package README because the provided excerpt does not list them.
- Which admin panel or UI framework does Panelis CMS work with?
- The package contributes admin-panel surface area through navigation groups, which strongly suggests integration with a panel framework such as Filament. However, the provided materials do not explicitly name the supported framework or major version. Check composer.json and the package docs to confirm the exact panel dependency before adopting it.
- Which Laravel and PHP versions are supported by panelis-php/cms?
- The provided overview does not list exact PHP, illuminate/*, or panel-framework constraints. Because admin-panel packages are sensitive to major-version drift, verify the declared constraints in the package composer.json against your app. Pay particular attention to the Laravel major version and the panel framework major version, such as Filament v3 versus v4.
- How do I publish Panelis CMS configuration, assets, and migrations?
- Use the package's documented vendor:publish commands after Composer installation. The expected Laravel package flow is to publish config, frontend assets if any, and migrations before running migrations. The provided README excerpt does not include the exact publish tags, so confirm them in the repository documentation.
- What changed in panelis-php/cms v1.2.1?
- v1.2.1 is a defensive patch that defers navigation-group registration when the owning package is absent. It makes partial installs safer, including trimmed production builds or deployments that intentionally omit optional sibling packages. The change is semver-safe and has no database migration, config key, published asset, or API surface impact.
- Is panelis-php/cms safe to use in production?
- It can be a reasonable fit for Laravel apps that already use an admin panel and want lightweight CMS surface area, but the technical risk is moderate. The main concerns are v1.x maturity, a small contributor base, and implicit coupling to optional sibling packages beyond the navigation fix. Verify Composer constraints, test partial installs, and review the test matrix before production adoption.
- Can I use Panelis CMS in a headless or API-only Laravel app?
- It is a poor fit for headless or API-only services because its value is entirely in the admin UI contribution for pages, content, and site settings. If your Laravel app has no admin panel, you would be adding a UI layer you do not need. Use it only when you want CMS administration surface area inside an existing panel.
- How should I test a Panelis CMS integration in my Laravel app?
- Install with a ^1.2.1 constraint in a staging branch and verify that the service provider is auto-discovered and navigation groups register correctly. Test page, content, and site-settings management in the admin panel, then repeat with composer install --no-dev and optimized autoloaders. Also test configurations where optional sibling packages are absent, since v1.2.1 specifically addresses that case.
- What are alternatives to panelis-php/cms for Laravel CMS functionality?
- The provided materials do not include a benchmark against other Laravel CMS packages or custom admin implementations. Evaluate alternatives by whether you need a lightweight, extendable admin CMS layer versus a full CMS or a custom panel-framework admin. Also compare maintenance activity, Laravel and panel-framework version constraints, and how much CMS surface area you would otherwise build yourself.
- How actively maintained is panelis-php/cms?
- It is a v1.x package with a small contributor base and a release cadence driven by individual pull requests. The v1.2.1 patch references a single author and single PR, which suggests limited review bandwidth. Check the repository's recent commits, issue response times, test matrix, and license or fork plan before relying on it long term.