Inspirecms Core Laravel Package

Product Decisions This Supports

• Build vs. buy for the content layer. InspireCMS is a Laravel-native CMS core — the decision it informs is whether to model content, publishing workflows, media, and an admin UI ourselves or adopt a package that sits inside our existing app. Adopting it removes a multi-sprint build of CRUD, editorial state, and admin scaffolding.
• Platform upgrade sequencing. v5.0.0 is essentially a compatibility release: PHP 8.2+ baseline, Laravel ^11 | ^12 | ^13, Filament ^5. Use it as the anchor for the framework upgrade train — the CMS bump forces (and validates) the PHP, Laravel, and Filament moves together rather than as three separate roadmap items.
• Architecture: embedded CMS vs. separate CMS. Choosing this package is a commitment to content living in the same codebase, deploy pipeline, auth model, and database as the product — versus a headless/SaaS CMS with its own hosting and integration surface.
• Dependency and vendor risk. The core package self-versions to a matching support package, so core + support must move together. That coupling is a standing constraint on how freely we can upgrade Laravel or Filament.
• Staffing and estimate inputs. A major version with breaking notes (Laravel 13 model booting behavior, Filament 5) means migration work is real and should be sized, not assumed free.
• Feature scoping. Anything we planned against older Filament admin components or Laravel < 11 is now outside the supported window; content-admin feature scope should be re-checked against Filament 5.
• Representative use cases: content/marketing sites, admin-heavy internal tools, and products with editorial workflows where the team already writes Laravel and doesn't want a second platform to operate.

When to Consider This Package

Consider it when:

• The app is on PHP 8.2+ and Laravel 11 or newer, and is on Filament 5 or can get there before adoption.
• Content needs are conventional — pages, entries, media, publishing state, admin CRUD — and building that ourselves is not differentiated work.
• You want the CMS inside the Laravel app: one deploy, one auth system, direct access to Eloquent models from product code.
• You have room in the roadmap for a major-version migration window, now and at future majors.
• You're greenfield or doing a planned platform refresh, so the upgrade cost is absorbed by work already scheduled.

Look elsewhere when:

• You're pinned to Laravel 10 or PHP 8.1, or on Filament 4 or lower with no near-term path to 5 — v5 does not help you, and staying on 4.x means running an unsupported branch.
• You've heavily customized model observers or model booting; Laravel 13's booting changes make that customization a migration risk, and a smaller, less opinionated package may be cheaper to bend.
• You need enterprise content capabilities — multi-stage approval chains, large-scale localization, a real DAM, granular editorial permissions — that a package this size doesn't claim to cover.
• Ecosystem maturity is a hard requirement: a smaller vendor with a fast major-version cadence and a self-versioned support package is a support and continuity risk worth naming explicitly.
• You want a fully managed SaaS CMS, or a monolith with a large plugin marketplace and hiring pool.

Adoption gate for v5 specifically: confirm Filament 5 first, inventory custom observer/booting code, review composer constraints on core and support before bumping, and run php artisan optimize:clear post-upgrade.

How to Pitch It (Stakeholders)

To executives (one paragraph): InspireCMS gives us a content management layer inside the Laravel application we already run, instead of a second platform to host, secure, staff, and integrate. v5.0.0 is a maintenance-driven major release: it moves us onto currently supported PHP and Laravel versions and onto Filament 5, which reduces our exposure to unsupported dependencies and security patching lag. The cost is a scheduled upgrade, not a rewrite — this is the cheapest moment to align, while we're already planning framework work.

To engineering: Treat this as a breaking major, not a patch. Baseline is PHP 8.2+ and Laravel ^11 | ^12 | ^13. Filament 5 is a prerequisite — upgrade that first if we're behind. Audit custom model observers against Laravel 13 booting behavior before bumping. Core and the support package are version-locked to each other, so bump them in the same change. Review composer constraints, then php artisan optimize:clear.

The ask: approve a timeboxed upgrade spike plus a migration ticket in the current cycle, with a go/no-go decision gated on Filament 5 readiness and the observer audit. If either fails, we stay on 4.x deliberately and record that as accepted dependency risk rather than drifting into it.