- What is ozankurt/laravel-modules-blog?
- It is a drop-in blog module for Laravel applications that already use a modular structure. It provides posts, categories, slug-based public routing, and admin scaffolding built on Filament. The package is designed to slot into an existing module system alongside ozankurt/laravel-modules-core and ozankurt/laravel-modules-interactions rather than act as a standalone monolith.
- How do I install laravel-modules-blog?
- Install it with Composer as ozankurt/laravel-modules-blog. The package uses spatie/laravel-package-tools for service-provider and config registration, so registration follows the standard Laravel package conventions. Publish the config and migrations with vendor:publish before running migrations, and check the README for the exact publish tags.
- Does this package support Laravel 12 or PHP 8.3?
- No. Version 2.0.0 requires PHP ^8.4 and Laravel ^13.0, so applications still on PHP 8.3 or Laravel 12 are blocked by the version constraints. The release notes describe this as a platform-baseline release with no deprecation runway, meaning the floor was raised rather than the old stack being maintained in parallel. You would need to move the whole application before adopting it.
- Which PHP, Laravel, Pest, and Testbench versions are required?
- The v2.0.0 support matrix is PHP ^8.4, Laravel ^13.0, Pest 5, and Orchestra Testbench 11. It also pairs with ozankurt/laravel-modules-core ^2.0 and ozankurt/laravel-modules-interactions ^2.0. Those companion bumps mean all three packages generally need to move together.
- Does laravel-modules-blog work with Filament 3, 4, and 5?
- Yes. The package supports Filament 3, 4, and 5, which decouples your admin-UI decision from the blog-core decision. That breadth lets teams stage a Filament upgrade independently of the blog module itself. It is worth confirming the support horizon for the older Filament 3 line if you plan to stay on it long term.
- How does the post-by-slug cache handle view-count updates?
- The documented behaviour is that a view-count-only bump does not invalidate the post-by-slug cache, so incrementing views does not force a cache miss or rebuild. This rule is unchanged in v2.0.0. Because it is a subtle invariant, it is worth covering with a regression test at your integration boundary, since app-level caching layers can easily bypass or re-implement it.
- Do I need laravel-modules-core and laravel-modules-interactions?
- The package is built to participate in a module system, and v2.0.0 targets ozankurt/laravel-modules-core ^2.0 and ozankurt/laravel-modules-interactions ^2.0. Partial upgrades that bump only one of the three packages will typically surface as Composer resolution conflicts rather than clean errors. Confirm which package owns module discovery and registration in your setup before planning the upgrade.
- How do I publish the config and migrations?
- The package registers its config and service provider through spatie/laravel-package-tools, so it follows the standard Laravel publishing workflow. Use the vendor:publish Artisan command with the package's tags, then run php artisan migrate. Refer to the README for the exact tag names and any optional seeders or assets.
- Is laravel-modules-blog production ready and tested?
- Yes. The v2.0.0 release ships with 98 tests and 297 assertions passing unchanged, plus PHPStan at level 8, and it required no source changes for the baseline bump. The main production caveat is ecosystem maturity: PHP 8.4, Laravel 13, Pest 5, and Testbench 11 are a front-of-the-curve combination, and unrelated third-party packages without Laravel 13 support can still block your upgrade.
- What are the alternatives to using a modular blog package like this?
- The alternatives are a standalone Laravel blog package, a headless CMS, or building posts and categories yourself. This package makes sense when your app already uses the ozankurt/laravel-modules-* ecosystem and a Filament admin panel, since it drops in without imposing its own runtime opinions. If you are not on PHP 8.4 and Laravel 13, or you do not use a module system, a standalone blog package will be a simpler fit.