Weave Code
Cms Laravel Package
craftcms/cms
Craft CMS is a flexible, user-friendly PHP CMS for building custom web experiences. Features a Twig templating system, auto-generated GraphQL API for headless builds, ecommerce via Craft Commerce, a plugin store, and a powerful extension framework.
Build bespoke content experiences with Craft.
Frequently asked questions about Cms
- Can Craft CMS be integrated with Laravel without conflicts, or is it a standalone solution?
- Craft CMS is designed to work alongside Laravel, not as a replacement. The `compiledTemplatesPath` config lets you isolate Craft’s Twig templates from Laravel’s Blade, reducing conflicts. For shared environments, use Laravel’s `storage_path()` helper to manage template caching. The package is optimized for hybrid setups, but test template rendering in staging first.
- What Laravel versions does Craft CMS support, and are there breaking changes between versions?
- Craft CMS 5.x officially supports Laravel 9.x and 10.x, with backward compatibility for most features. Breaking changes typically involve plugin updates or template syntax. Always check the [Craft CMS docs](https://craftcms.com/docs/5.x/upgrading.html) for version-specific notes. For Laravel 11, verify compatibility with the Craft team or community forums before upgrading.
- How do I install Craft CMS via Composer in a Laravel project without breaking existing dependencies?
- Run `composer require craftcms/cms` in your Laravel project’s root. Craft CMS includes a Laravel service provider (`Craft`) that auto-registers. If conflicts arise, use `composer why-not` to diagnose dependency issues. For shared hosting, ensure PHP 8.1+ and MySQL/PostgreSQL are supported. Follow Craft’s [installation guide](https://craftcms.com/docs/5.x/install.html) for Laravel-specific steps.
- Does Craft CMS work with Laravel’s queue system (Redis, database), or does it require its own?
- Craft CMS can share Laravel’s queue system (Redis, database, etc.) by configuring the `queueConnection` setting in `config/general.php`. Fixes for queue polling in Craft 5.x reduce unnecessary API calls, lowering load on Laravel’s workers. Monitor queue metrics with tools like Laravel Horizon to avoid race conditions in high-traffic setups.
- How do I handle template conflicts between Laravel Blade and Craft Twig in the same project?
- Use Craft’s `compiledTemplatesPath` config to separate Blade and Twig caches (e.g., `storage/framework/views/craft`). This prevents filesystem permission issues and conflicts. For shared templates, structure your project with `/resources/views/laravel` and `/templates/craft` directories. Craft’s Twig environment is isolated by default, but test template inheritance in staging.
- Are there known issues with Craft CMS plugins when used in a Laravel application?
- Some third-party Craft plugins may conflict with Laravel service providers or config files. Pin plugin versions in `composer.json` and test in isolation using `composer why-not`. Craft’s plugin store lists Laravel-compatible plugins, but always verify with the plugin author. For custom plugins, check for updates to Craft 6 compatibility early.
- Can I use Craft CMS’s GraphQL API with Laravel’s frontend (e.g., Livewire, Inertia.js) for headless setups?
- Yes, Craft CMS auto-generates a GraphQL API that works seamlessly with Laravel frontends. Use Laravel’s HTTP client or GraphQL libraries (e.g., `webonyx/graphql-php`) to query Craft’s API. For Livewire/Inertia, fetch data via Alpine.js or Laravel’s API routes. Document your GraphQL schema in Craft’s control panel for frontend teams.
- How do I migrate an existing Laravel project to include Craft CMS without data loss?
- Start by backing up your Laravel database and files. Use Craft’s [migration guide](https://craftcms.com/docs/5.x/migrating.html) to adapt existing content models. For custom sections, extend Craft’s schema with Laravel migrations or use Craft’s field types. Test the `minAuthors` migration in staging first, as it may require author field updates for sections.
- What are the performance implications of running Craft CMS alongside Laravel in production?
- Craft CMS and Laravel share PHP and database resources, so monitor CPU/memory usage closely. Optimize by caching templates separately (`compiledTemplatesPath`), using Redis for queues, and enabling Craft’s asset compression. For high-traffic sites, consider separate servers or containerized deployments (e.g., Docker). Craft’s queue fixes reduce overhead, but test under load.
- Are there alternatives to Craft CMS for Laravel that offer similar flexibility but with better Laravel integration?
- Alternatives include October CMS (Laravel-based but less flexible), Strapi (Node.js, headless-focused), or custom Laravel + Filament CMS setups. Craft CMS stands out for its Twig templating, plugin ecosystem, and native Laravel synergy. For tighter Laravel integration, evaluate [Filament CMS](https://filamentphp.com/) or [Backpack for Laravel](https://backpackforlaravel.com/), but they lack Craft’s content modeling depth.
Weaver
How can I help you explore Laravel packages today?