Weave Code
Bundles Cms Laravel Package
kunstmaan/bundles-cms
Kunstmaan CMS is a full-featured, multilingual CMS built on the Symfony full-stack framework. It offers page and form assembly, versioning, workflow, translation tools, and media management, plus integrations with community bundles.
An advanced yet user-friendly content management system, based on the full stack Symfony framework combined with a whole host of community bundles. It provides a full featured, multi-language CMS system with an innovative page and form assembling process, versioning, workflow, translation and media managers and much more.
Frequently asked questions about Bundles Cms
- Is kunstmaan/bundles-cms compatible with Laravel?
- No. Kunstmaan CMS is built on the full-stack Symfony framework and its bundles depend on Symfony components such as Twig, Doctrine, SecurityBundle, and KnpMenu. It is not a Laravel package and does not provide Laravel service providers, facades, or Blade views. You can only use it alongside Laravel through a separate Symfony application or API layer.
- Can I install kunstmaan/bundles-cms with Composer in a Laravel project?
- You can run composer require kunstmaan/bundles-cms in a Laravel project, but it will not behave as a native Laravel CMS. The package expects a Symfony application structure, Symfony bundles, and Doctrine configuration. Installing it inside Laravel would create dependency and autoloading conflicts without custom bridging work.
- How can I integrate Kunstmaan CMS with a Laravel application?
- The most practical approach is to run Kunstmaan as a separate Symfony application and expose its content through REST or GraphQL APIs. Your Laravel app then consumes those APIs as a headless frontend or backend service. Direct in-process integration would require Symfony Bridge adapters, custom service providers, and significant maintenance effort.
- Does Kunstmaan CMS use Doctrine or Eloquent?
- Kunstmaan CMS uses Doctrine ORM for its entity model, including nodes, pages, media, and translations. Laravel's default Eloquent ORM is not used. Laravel can access the same database through doctrine/dbal or laravel-doctrine, but Kunstmaan's schema and entity logic still need to be respected or migrated.
- Can I use Kunstmaan CMS as a headless CMS for Laravel?
- Yes, that is the most feasible integration pattern. Keep Kunstmaan running as a Symfony CMS and expose content via an API such as API Platform, a custom REST controller, or GraphQL. Laravel can then render the frontend or act as a middleware layer. The Symfony admin UI and Twig templates remain outside Laravel.
- Which Laravel versions does kunstmaan/bundles-cms support?
- None directly. The package targets Symfony versions, not Laravel versions, so Laravel 10, 11, or 12 support is not part of its compatibility matrix. You should check the package's Symfony and PHP requirements on Packagist and in its documentation. For Laravel compatibility, treat it as an external service rather than a Laravel dependency.
- How do I replace the Kunstmaan CMS admin panel with Laravel?
- You would need to rebuild admin features such as page assembly, media management, workflow, versioning, and ACL in Laravel, for example with Inertia.js, Vue, or Blade. Alternatively, embed or reverse-proxy the existing Symfony admin and keep it as the editorial interface. A full rebuild is a large custom project because Kunstmaan's admin is tightly coupled to Symfony, Twig, and KnpMenu.
- What are Laravel alternatives to Kunstmaan CMS?
- Laravel-native options include Statamic, October CMS, Winter CMS, AsgardCMS, and TypiCMS, depending on whether you need flat-file, database, or enterprise features. Headless alternatives such as Directus or Strapi can also sit behind a Laravel frontend. If you need Kunstmaan's specific workflow and page assembly, a Symfony microservice is usually safer than forcing it into Laravel.
- Is kunstmaan/bundles-cms still maintained and production-ready?
- It is an established Symfony CMS with CI, documentation, translations, and community bundles, and it is used for production Symfony sites. Maintenance should be verified against the latest release, Symfony version support, and open issues before adoption. For Laravel teams, the main risk is not maturity but the cost of bridging two different frameworks.
- How should I test a Kunstmaan CMS and Laravel integration?
- Test the integration at the API boundary: use Laravel HTTP tests to assert REST or GraphQL responses, authentication, caching, and error handling. Run Kunstmaan's own Symfony test suite and functional tests in its separate application. For contract testing, mock the API in Laravel unit tests and use a staging environment for end-to-end editorial workflow checks.
Weaver
How can I help you explore Laravel packages today?