- Can I use RJCMS with Laravel 11 or older versions?
- No, RJCMS requires Laravel 12 or 13 specifically due to its dependency on Livewire 4 and PHP 8.3+. If you're on an older version, you’d need to fork the package or wait for potential backporting efforts, though none are officially planned.
- How does the BREAD builder handle custom field types (e.g., API integrations or custom validation)?
- The visual BREAD builder supports standard field types (text, images, relationships, etc.), but custom logic like API integrations or validation requires extending Livewire components or overriding package views. You’d typically create a custom field type by publishing the package’s assets and extending its base classes.
- Will RJCMS work with my existing Eloquent models, or does it require its own database schema?
- RJCMS primarily manages its own schema for content types, media, and permissions, but you can integrate existing Eloquent models into the BREAD builder by defining them as relationship fields. However, schema changes (like adding custom tables) must be handled manually outside the builder.
- How scalable is the media library for high-volume uploads (e.g., thousands of images)?
- The media library uses Laravel’s default storage system, so scalability depends on your storage backend (e.g., S3, local disk). For large volumes, optimize by configuring CDNs, enabling queue-based uploads, and ensuring your storage driver supports concurrent access. Performance testing is recommended for production use.
- Can I customize the admin panel’s UI without touching Blade templates directly?
- Yes, you can override package views by publishing assets (`php artisan vendor:publish --tag=rjcms-assets`) and modifying files in `resources/views/vendor/rjcms/`. For deeper customization, extend Livewire components via service providers or middleware, though this requires familiarity with Livewire’s lifecycle.
- Does RJCMS support multi-tenancy or soft deletes out of the box?
- No, RJCMS does not include multi-tenancy or soft deletes natively. Soft deletes can be added by extending the package’s models to use Laravel’s `SoftDeletes` trait, but multi-tenancy would require custom implementation, likely involving middleware or model observers to scope data by tenant.
- How do I migrate from RJCMS to another package like Filament or Nova later?
- Migrating away from RJCMS involves exporting your content data (e.g., via Eloquent queries or the BREAD builder’s exports) and reimporting it into the new package. Since RJCMS doesn’t generate migration files for custom schemas, you’ll need to manually recreate tables or use the new package’s migration tools. Backup your database before attempting this.
- Are there any known conflicts with Laravel Mix or Vite for asset compilation?
- RJCMS publishes its own CSS/JS assets during installation, which may conflict with existing Laravel Mix or Vite setups if they target the same output directories. To avoid conflicts, either exclude RJCMS’s asset paths from your build tools or manually merge the stylesheets. The package does not version its assets by default.
- Can I use RJCMS for a headless Laravel setup (e.g., with a React/Vue frontend)?
- RJCMS is primarily designed for server-rendered admin panels using Blade and Livewire. While you could expose its data via custom API endpoints (e.g., using Laravel Sanctum), the package itself isn’t API-first. For headless setups, consider alternatives like Filament or Backpack, which offer better API integration.
- What’s the maintenance status of RJCMS, and how often are updates released?
- RJCMS is maintained by Raj Maharjan, but it lacks a public roadmap or clear update cadence. The package is actively developed for Laravel 12/13, but support for Laravel 14+ isn’t guaranteed. Check the GitHub repository for recent commits or open issues to gauge activity. For production use, monitor updates closely or consider forking.