- Is johnkrovitch/cms-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It is built around Symfony's kernel, dependency injection extension, compiler passes, and likely Twig and Doctrine. Laravel uses service providers, facades, Eloquent models, and Blade, so there is no drop-in integration path. Treat it as a Symfony CMS component rather than a Laravel-native solution.
- Can I use johnkrovitch/cms-bundle with Laravel?
- You can install it with Composer, but it will not just work in a Laravel application. A Symfony bundle expects Bundle class registration in config/bundles.php, Symfony DI configuration trees, and HttpKernel event subscribers. Making it run under Laravel means a dual-kernel bridge with two routers and two container graphs, which is a permanent architectural tax. That is not recommended for a one-star package with no Laravel integration.
- Which Laravel versions are supported by johnkrovitch/cms-bundle?
- No Laravel versions are officially supported. The package is a Symfony bundle and does not declare Laravel service providers, middleware, or Eloquent integration. Its last release was October 2020, so it predates modern Laravel 10 and 11 conventions and current PHP 8.x expectations. Do not count on Laravel version compatibility.
- What PHP and Symfony versions does johnkrovitch/cms-bundle require?
- The provided metadata does not list exact constraints, so verify the composer.json require block directly. Given the last release date of 2020-10-24, it is almost certainly pinned to Symfony 4.4 or 5.x and older PHP versions, both now end-of-life. Check the declared constraints before spending any evaluation time.
- Is johnkrovitch/cms-bundle maintained and safe for production?
- It is high risk for production use. The last release was in October 2020, it has one star and zero dependents, a single author, and no described documentation, test coverage, or security disclosure process. A CMS bundle likely pulls Doctrine, Twig, and asset or upload handling, each adding patch obligations you would inherit. Do not adopt it without a funded fork and a security review.
- How do I install and configure johnkrovitch/cms-bundle?
- In Symfony, you register the bundle in config/bundles.php, configure its dependency injection extension, and use its content entities with routing and Twig integration for frontend rendering. The overview describes modular CMS foundations, structured pages, and editable content, but the README excerpt here is empty, so confirm exact setup steps upstream. In Laravel this registration surface does not exist, so the Symfony install path does not apply.
- How do I create editable pages and content types with johnkrovitch/cms-bundle?
- The bundle is described as providing content management for structured pages and editable content through a bundle-based modular architecture. In Symfony you would use its content abstractions, likely Doctrine entities, plus its routing and template integration to render pages. The context does not include detailed API documentation, so check the upstream repository for the exact content type and page modeling workflow. For Laravel, you would need to reimplement that model rather than rely on the bundle.
- What are Laravel-native alternatives to johnkrovitch/cms-bundle?
- Statamic, Twill, and Filament-based admin panels are common Laravel-native options, and a thin custom content model is often enough for smaller sites. These use Laravel service providers, Eloquent, Blade, and policies instead of a Symfony kernel. Compared with a dual-kernel bridge or a port, they are lower risk and better maintained for a Laravel codebase.
- Can I reuse johnkrovitch/cms-bundle's content model in Laravel?
- Yes, but only as reference material rather than as a dependency. Read the bundle's entities and schema, then reimplement pages, content types, versioning, and media handling as Eloquent models, migrations, and policies. The assessment suggests this is a scoped two-to-four-week effort for a small CMS, and the bundle code itself is discarded. That makes it design input, not a Composer integration.
- How should I evaluate or test johnkrovitch/cms-bundle before adopting it?
- Start with the composer.json constraints, then try booting it in an isolated Symfony application on a supported PHP and Symfony pair. Review transitive dependencies, check for security advisories, and identify who would own a fork and its annual maintenance budget. For a Laravel target, prototype a native alternative in parallel because there is no Laravel test integration to rely on.