Laravel Modules Blog Laravel Package

Product Decisions This Supports

• Build vs. buy for content/blog capability. The package supplies the core module system, interactions, blog content, slug routing, and Filament admin resources out of the box. A PM can treat blog/content as a solved problem and redirect engineering capacity to differentiating features rather than rebuilding CRUD, slugs, and admin screens.
• Admin/back-office roadmap. Continued support for Filament 3, 4, and 5 in the same release means the admin experience is not pinned to a single Filament major. This de-risks admin UI modernization (e.g., a Filament 4 → 5 migration) from being blocked on this package.
• Performance and infrastructure cost decisions. The preserved cache rule — a view-count-only bump does not invalidate the post-by-slug cache — is a deliberate cost/latency trade-off. PMs can rely on read-heavy content pages staying cached under traffic spikes, with only content edits triggering invalidation.
• Platform upgrade timing. v2.0.0 establishes a Laravel 13 / PHP 8.4 / Pest 5 baseline. This becomes an input to the platform-upgrade roadmap: adopting this release couples the content module to the Laravel 13 upgrade window.
• Modular architecture and reuse. The dependency on laravel-modules-core and laravel-modules-interactions signals a composable module pattern. This supports decisions about reusing the same content module across multiple products/brands rather than forking.
• Use cases well served: marketing/content sites, multi-module SaaS with an editorial back office, internal tools needing a lightweight blog/announcements module, and any product already standardized on Filament.

When to Consider This Package

Consider adopting when:

• The product is on, or is scheduled to move to, Laravel 13 and PHP 8.4. v2.0.0 is the current line and the only one aligned with the newest framework baseline.
• You need a maintained content/blog module with a Filament admin and want to avoid owning slug generation, caching, and view-count plumbing.
• You value upgrade discipline: this release required no source changes, kept the full suite green (98 passed, 297 assertions), and held PHPStan level 8 — a signal of low integration friction.
• You want Filament version flexibility (3/4/5) so admin upgrades are not gated by this dependency.
• You are comfortable with a fast-moving, framework-locked dependency whose majors track Laravel majors.

Look elsewhere or defer when:

• You are on Laravel 12 or PHP 8.3 with no near-term upgrade path. v2.0.0 is explicitly breaking: it drops Laravel 12 and PHP 8.3. Staying on v1.x means accepting an unmaintained branch.
• Your organization requires long support windows and slow, predictable upgrade cadence. This package's majors arrive in lock-step with Laravel releases, which will force repeated platform work.
• You do not use Filament, or your admin surface is bespoke/headless — much of the packaged value is admin-side.
• Content is not a core domain and a hosted CMS or SaaS blog would be cheaper than owning a dependency.
• You need guarantees this release does not speak to: it is a compatibility release with no new features, so it does not close any functional gaps you may be waiting on.

How to Pitch It (Stakeholders)

For executives: This is a maintenance release that keeps our content/blog module on the current, supported platform baseline (Laravel 13, PHP 8.4) and confirms it works across three generations of our admin framework. It adds no new features and requires no code changes on our side — the maintainer's suite and static analysis are green. The trade-off is a hard cutover: we cannot stay on Laravel 12 or PHP 8.3 and take this release, so it should be sequenced with our platform upgrade rather than treated as an independent update.

For engineering: v2.0.0 is a pure compatibility bump — new floors on PHP (^8.4), Laravel (^13.0), and the two laravel-modules core packages (^2.0), plus spatie/laravel-package-tools ^1.93 and cviebrock/eloquent-sluggable ^12||^13. Test toolchain moves to Pest 5 / Orchestra Testbench 11; CI covers PHP 8.4 × Laravel 13 × Filament 3/4/5. No source changes were needed and the full suite (98 tests, 297 assertions) plus PHPStan level 8 pass as-is. Cache semantics are unchanged, including the invariant that a view-count-only bump does not invalidate the post-by-slug cache — do not "fix" this during the upgrade. Action: treat the Laravel 12 / PHP 8.3 drop as a coordinated migration, pin the laravel-modules-* ^2.0 pair together, and verify our Filament major is in the 3/4/5 set before merging.