Weave Code
Blog Bundle Laravel Package
aropixel/blog-bundle
A Symfony blog management bundle for the Aropixel Admin Bundle, with posts, categories, rich content fields, SEO metadata, scheduled publication, featured image crops, multilingual translations, and customizable entities and forms.
Gestion de blog pour admin Aropixel
Frequently asked questions about Blog Bundle
- Can I use aropixel/blog-bundle in a Laravel application?
- No. Aropixel Blog Bundle is a Symfony bundle built for Symfony 6.4, 7.x, and 8.x, and it requires aropixel/admin-bundle ^3.0. Laravel's Eloquent, routing, Blade, service container, and admin panels are not supported. If you need a blog in Laravel, choose a Laravel-native package or build a custom solution.
- What Laravel versions does aropixel/blog-bundle support?
- None. It is not a Laravel package and provides no Laravel service provider, Eloquent models, migrations, or Blade views. The current v3.0 release targets Symfony 6.4, 7.x, and 8.x with Doctrine ORM 2 or 3. Laravel compatibility would require a full port, not a configuration change.
- How do I install and configure aropixel/blog-bundle?
- Installation is via Composer inside a Symfony project, following doc/installation.md, and requires aropixel/admin-bundle ^3.0. You then configure Doctrine entities, routes, admin integration, and any entity or form overrides in Symfony. There is no Laravel installation or configuration path.
- Does aropixel/blog-bundle support multilingual blog posts?
- Yes. It has documented i18n support for titles, descriptions, slugs, and related fields, built on Symfony's translation system. The admin interface is available in French, English, German, Spanish, Italian, and Czech. This i18n model is not portable to Laravel localization or spatie/laravel-translatable without a rewrite.
- What are Laravel alternatives to aropixel/blog-bundle for a blog CMS?
- Laravel-native options include a custom blog with Eloquent and Blade, Filament or Nova resources, or Laravel-oriented CMS/blog packages where they fit your needs. Compare features such as multilingual content, SEO metadata, scheduled publication, and image crops against the Symfony bundle. These alternatives avoid Symfony dependencies and integrate with Laravel routing, auth, and admin panels.
- Is aropixel/blog-bundle abandoned or actively maintained?
- The older abandonment concern is no longer accurate because v3.0.0 is an active rewrite with Symfony 6.4, 7.x, and 8.x plus Doctrine ORM 2 or 3 support. However, there is no in-place upgrade from previous versions and no Laravel support. Maintainer activity on the Symfony side does not reduce Laravel adoption risk.
- Can I integrate aropixel/blog-bundle with Filament or Laravel Nova?
- Not directly. The bundle manages posts and categories through Aropixel Admin Bundle 3.0 shared list and action macros, so Filament or Nova would require rebuilding the admin surface. You would also need to replace Doctrine entities with Eloquent models and Symfony forms with Laravel form requests. That is effectively a custom Laravel port.
- How do I test aropixel/blog-bundle, and what production concerns apply?
- Testing requires a Symfony test setup with Doctrine and AdminBundle integration; Laravel testing helpers do not apply. In production, scheduled publication, image crops, translations, and SEO metadata would all need Laravel equivalents if you attempt a port. There is no official Laravel test suite or production bridge for this bundle.
- How would I migrate aropixel/blog-bundle data to Laravel?
- You would need to map Doctrine tables for posts, categories, translations, images or crops, and SEO fields to Laravel migrations and Eloquent relationships manually. Symfony routing, forms, Twig templates, and admin macros must be rebuilt with Laravel routes, form requests, Blade or Inertia, and Filament, Nova, or custom UI. Plan an export and import process for multilingual content and publication dates because there is no official Laravel migration path.
- Should I use a Symfony microservice for aropixel/blog-bundle with a Laravel frontend?
- That is possible but adds operational complexity: a separate Symfony app, database or API boundary, authentication, caching, and content synchronization. For most Laravel projects, a Laravel-native blog or CMS is simpler and avoids maintaining two frameworks. Consider a microservice only if you already run Symfony services or need the bundle's exact admin workflow.
Weaver
How can I help you explore Laravel packages today?