- Does flobbos/page-composer work with Laravel 10 or Livewire 3?
- No, this package requires **Laravel 13+** and **Livewire 4+**, along with PHP 8.3+. If you're on older versions, you’ll need to upgrade first, which may introduce compatibility risks or require additional migration work.
- How do I install and set up flobbos/page-composer in my Laravel project?
- Run `composer require flobbos/page-composer`, then execute `php artisan page-composer:install` to automate setup. Publish the config with `php artisan vendor:publish` and select the `PageComposerServiceProvider`. Follow the prompts for database migrations and asset configuration.
- Can I use this CMS without Tailwind CSS? What if my project uses Bootstrap or another framework?
- The package is **Tailwind-centric**, so projects not using Tailwind will need to manually override styles or adopt Tailwind. If you rely on Bootstrap or another CSS framework, expect additional frontend development effort to align with the package’s styling system.
- Is flobbos/page-composer suitable for a headless Laravel API setup?
- Yes, the package supports **decoupled content management**, meaning you can manage content via the admin panel while serving it via APIs or Blade templates. This makes it a good fit for headless architectures where content is consumed dynamically.
- What’s the impact of using flobbos/translatable-db for i18n? Can I use Laravel’s built-in localization instead?
- The package **requires flobbos/translatable-db** for translations, which may conflict with Laravel’s native localization if already in use. If your project relies on Spatie’s Laravel Translation Manager or another solution, you’ll need to evaluate compatibility or refactor.
- How do I add custom elements (e.g., a video player or accordion) to PageComposer?
- Custom elements are built as **Livewire components** and placed in `app/Livewire/PageComposer/Elements/`. Extend the base `Element` class and register them in the `PageComposerServiceProvider`. Ensure your team has Livewire expertise, as poorly optimized elements can impact performance.
- What are the performance implications of using Livewire for a CMS with many pages?
- Livewire introduces real-time interactivity but can **increase server load** for complex layouts or high-traffic sites. Test thoroughly in staging, especially if using drag-and-drop or heavy elements. Consider lazy-loading or caching strategies for production.
- Are there any breaking changes or migration risks when upgrading from 0.1.x to 1.x?
- Yes, the package has **unproven long-term stability** as of 2026, with notable changes like drag-and-drop migrations and Quill component renames. Review the [upgrading docs](https://github.com/Flobbos/page-composer#upgrading) and test thoroughly in a staging environment before deploying.
- What’s the fallback option if flobbos/page-composer doesn’t fit my project?
- Alternatives include **Laravel Nova** (for enterprise needs), **Spatie’s Media Library + custom Blade templates** (for lightweight content), or **October CMS** (if you need a more mature, non-Livewire solution). Evaluate based on your stack and customization needs.
- How do I handle Alpine.js conflicts if my project uses Alpine 2 or custom components?
- PageComposer assumes **Alpine.js 3**, which ships with Livewire 4. If your project uses Alpine 2, conflicts may arise. Audit your Alpine usage, update to v3, or isolate custom components to avoid compatibility issues during Livewire integration.