- Can Kunstmaan CMS be used directly in a Laravel project?
- No, Kunstmaan CMS is built for Symfony, not Laravel. However, you can integrate specific features (like media management or ACL) via custom Laravel packages or use Kunstmaan as a headless CMS via REST/GraphQL APIs.
- What’s the best way to adopt Kunstmaan’s features in Laravel?
- For partial adoption, wrap Kunstmaan components (e.g., media manager) in Laravel services or use Doctrine DBAL for database access. For full CMS replacement, consider a microservices approach where Kunstmaan runs separately and exposes APIs.
- Does Kunstmaan CMS support Laravel’s Blade templating?
- No, Kunstmaan uses Twig. To integrate, rebuild the frontend in Laravel (e.g., with Inertia.js + Vue/React) or embed Kunstmaan’s admin panel via iframe/subdomain if Symfony coexistence is acceptable.
- Which Laravel versions are compatible with Kunstmaan’s database schema?
- Kunstmaan uses Doctrine ORM, which can be partially adopted in Laravel via `doctrine/dbal` or `laravel-doctrine`. However, schema migrations (e.g., Node, Page entities) would require custom Laravel migrations or duplication.
- How does Kunstmaan’s workflow system integrate with Laravel?
- Kunstmaan’s workflow is tightly coupled with Symfony. For Laravel, implement custom event listeners or database triggers to mirror workflow logic, or expose Kunstmaan’s workflow via API for remote triggering.
- Are there Laravel alternatives to Kunstmaan’s media manager?
- Yes, consider Spatie’s `laravel-medialibrary` or `spatie/laravel-activitylog` for media and versioning. Kunstmaan’s media tools can also be wrapped in a Laravel service if needed.
- Can Kunstmaan CMS handle multilingual content in Laravel?
- Kunstmaan excels at multilingual content via Symfony’s translation tools. In Laravel, use `laravel-localization` or custom middleware, but expect higher effort to replicate Kunstmaan’s translation workflow.
- What’s the performance impact of running Kunstmaan alongside Laravel?
- Running both stacks (Symfony + Laravel) introduces overhead. Mitigate this with caching (Symfony Cache or Laravel Redis) and async processing (queues) for tasks like media uploads or workflow updates.
- Is there official support for Kunstmaan in Laravel?
- No, Kunstmaan is Symfony-first. However, the community provides partial solutions (e.g., Doctrine DBAL adapters). For full integration, expect custom development or hybrid architectures.
- How do I migrate from Kunstmaan to a pure Laravel CMS?
- Start by extracting reusable components (e.g., ACL, media tools) into Laravel packages. For core features (page assembly, versioning), rewrite logic in Laravel or adopt alternatives like `spatie/laravel-permission` and `spatie/laravel-activitylog`.