- What Laravel versions does kamoji/cms support, and does it work with PHP 8.1+?
- The package targets Laravel 8+ and requires PHP 8.0+. Check the `composer.json` for exact version constraints, as newer Laravel releases may introduce breaking changes. Always verify compatibility with your project’s PHP version before installation.
- How do I install kamoji/cms in an existing Laravel project?
- Run `composer require kamoji/cms` in your project root. The package follows Laravel conventions, so it will auto-discover and register its service provider. Run migrations (`php artisan migrate`) if you’re using the default database schema.
- Can I customize the admin panel or content models without overriding core files?
- Yes, the package is designed for extensibility. You can define custom content blocks, pages, and fields via configuration files or service providers. It avoids hardcoding UI logic, letting you theme the admin panel using Blade or frontend frameworks like Livewire.
- Does kamoji/cms integrate with Laravel’s built-in authentication (e.g., Sanctum, Breeze) or require its own?
- It integrates with Laravel’s native auth system (e.g., `Auth::user()`), so you can use existing providers like Sanctum, Breeze, or Jetstream. Access control is flexible—you can extend it with Laravel’s gates/policies for granular permissions.
- How are database migrations handled? Will it conflict with my existing schema?
- The package provides migrations for its core tables (e.g., `pages`, `blocks`). It uses Laravel’s migration system, so you can modify or extend them. Avoid naming conflicts by reviewing the migration files before running `php artisan migrate`.
- Can I use kamoji/cms with Livewire, Inertia.js, or Vue/React for the frontend?
- Absolutely. The package is frontend-agnostic and provides Blade helpers for rendering content. You can integrate it with Livewire for reactive admin panels or use Inertia.js/Vue/React for SPAs by fetching content via APIs or Blade components.
- Is there a demo or sandbox to test the package before committing to it?
- The package lacks a public demo, but you can clone the repository and run `php artisan serve` after installation to explore the default admin panel and content structures. Review the `README` for setup instructions and example configurations.
- What happens if I need to update kamoji/cms later? Are there breaking changes?
- Updates are handled via Composer (`composer update kamoji/cms`). Since it’s a lightweight package, breaking changes are rare, but always check the changelog or release notes. Backup your database and test updates in a staging environment first.
- Does kamoji/cms support multi-tenancy or content versioning?
- Out of the box, it doesn’t include multi-tenancy or versioning. However, you can extend its Eloquent models or use Laravel’s features (e.g., `SoftDeletes`, `Observers`) to implement these. The package’s modular design makes customizations like this straightforward.
- Are there alternatives to kamoji/cms for Laravel CMS needs, and why choose this one?
- Alternatives include Spatie Media Library (for media), Backpack CMS (monolithic), or Orchid (feature-rich). kamoji/cms stands out for its lightweight, package-first approach—ideal if you want to avoid bloat and keep full control over your app’s architecture. It’s best for projects needing a flexible, customizable CMS without a full-stack solution.