- Is Burgov CMS Bundle suitable for a headless CMS setup with a React frontend?
- Yes, the bundle is designed for API-driven content delivery, making it ideal for React or Vue frontends. It returns JSON responses by default, so you can fetch content via REST or GraphQL (with additional setup). However, you’ll need to configure routes and middleware to match your API structure.
- What Laravel versions does Burgov CMS Bundle support?
- The package appears to target Laravel 8+, but explicit version compatibility isn’t documented. Test thoroughly with your Laravel version, especially if using newer features like Symfony 6 components or PHP 8.1+. Check the `composer.json` constraints for clues.
- How do I customize the content models or database schema?
- The bundle uses Eloquent models, so you can extend or override them by publishing migrations and model configurations. However, documentation is sparse, so inspect the bundle’s default migrations and models in `vendor/` to replicate or modify structures. Use Laravel’s model events for custom logic.
- Does Burgov CMS Bundle support multi-language (localized) content?
- There’s no explicit localization support in the current documentation. For multi-language content, you’d need to implement a solution like Laravel’s built-in localization or a package like `spatie/laravel-translatable`. Custom fields or middleware could also handle language-specific routing.
- How are media files (images, PDFs) managed in this bundle?
- The bundle doesn’t include built-in media handling, so you’ll need to integrate a package like `spatie/laravel-medialibrary` or Laravel’s filesystem drivers. Store file paths or URLs in your content models and ensure your storage setup (e.g., S3, local disk) aligns with your deployment environment.
- Can I use Burgov CMS Bundle with Laravel’s built-in authentication?
- Yes, the bundle integrates with Laravel’s auth system by default, assuming you’ve configured middleware like `auth` or `can` for protected routes. For role-based access, extend the bundle’s authorization logic or use Laravel’s policy system to gate content access.
- Are there performance optimizations for content-heavy applications?
- The bundle lacks documented optimizations like query caching or eager loading, which could lead to N+1 issues. Manually optimize queries using Eloquent’s `with()` or implement caching (e.g., Redis) for frequently accessed content. Profile performance with tools like Laravel Debugbar.
- How do I deploy Burgov CMS Bundle in production?
- Follow standard Laravel deployment practices: configure `.env` for production (e.g., `APP_ENV=production`, caching drivers), optimize autoloading with `composer dump-autoload --optimize`, and ensure your server meets PHP/Laravel requirements. Test API endpoints and content delivery under load before full rollout.
- What alternatives exist if Burgov CMS Bundle lacks features like versioning?
- Consider `spatie/laravel-medialibrary` for media, `spatie/laravel-activitylog` for versioning, or full-fledged CMS packages like `backpack/crud` or `orchid/software`. For headless needs, evaluate `spatie/laravel-honeypot` for spam protection or `filament/filament` for admin panels.
- How do I extend the bundle’s core functionality, like adding custom field types?
- The bundle’s modular design suggests extension points, but documentation is minimal. Start by inspecting the bundle’s service providers and traits in `vendor/` to identify hooks for custom logic. Override or extend Eloquent models, and use Laravel’s service container to bind new field types or workflows.