Teamkitv5 Laravel Package

Product Decisions This Supports

• Build vs. buy for back-office: teamkitv5 is a Laravel + Filament starter kit that bundles authentication, a user/admin split, and admin resources. It informs the "build our own admin, adopt a kit, or buy a SaaS back-office" decision — this package is the "adopt a kit" option.
• Platform vs. product scope: the notable item in 5.9.0 (PR #152, "Use user/admin packages for models, resources and login") moves identity and admin concerns out of the app and into separate packages. That's a scoping decision: identity/admin becomes a shared platform dependency you version and upgrade, not product code you own.
• Roadmap sequencing: if the team is greenfield on Laravel and needs an admin surface in the next sprint or two, adopting this compresses the "plumbing" phase. If the roadmap's first milestone is customer-facing, this package buys you little.
• Maintenance capacity planning: 5.9.0 is 11 of 12 changes CI/dependency housekeeping plus a Filament v5 bump and a 7-package composer update. That cadence is real ongoing work — budget upgrade time each cycle rather than treating adoption as a one-time cost.
• Not a differentiator: nothing here informs pricing, positioning, or customer-facing feature bets. Treat it purely as an execution-velocity lever.

When to Consider This Package

Consider it when:

• You're starting a new Laravel app and need an admin/back-office surface (users, admins, login) fast, on Filament v5.
• You actively want user and admin split into discrete, reusable modules — 5.9.0 makes that the default shape, which suits multi-app or multi-tenant estates.
• You're comfortable inheriting the maintainer's conventions: standardized CI, Dependabot auto-merge for minor/patch, frequent small releases.
• A spike-level commitment is acceptable — you can adopt, evaluate, and back out without architectural lock-in.

Look elsewhere when:

• You need an LTS/SLA, security-review cadence, or a documented breaking-change and deprecation policy. The 5.8.4 → 5.9.0 notes carry no migration guide despite relocating models, resources, and login.
• You require stability in your dependency graph; this project moves with upstream Filament and composer/npm churn.
• Your stack isn't on Filament v5 or you can't absorb the version constraint.
• You need auditability — "CI standardization" and Dependabot auto-merge mean changes land continuously, which some compliance regimes won't accept without extra gating.

How to Pitch It (Stakeholders)

For executives: This is a Laravel starter kit that gives us a working admin back-office — users, admins, login — out of the box, potentially saving weeks of plumbing on a new app. The trade-off is governance, not capability: it releases frequently, mostly dependency and CI churn, and this release reorganized how user/admin code is packaged without a written upgrade guide. Recommendation: run a short spike to quantify the savings, and treat it as an accelerator we can walk away from rather than a platform commitment.

For engineering: 5.8.4 → 5.9.0 is a minor bump with one structural change worth attention — models, resources, and login now come from separate user/admin packages (PR #152), alongside a Filament v5.9.0 bump and a 7-package composer update. Before upgrading, verify published config and migration paths, resource discovery/namespaces, and login route bindings against the new package-provided versions; assume the old in-app paths are gone. The remaining changes are CI workflow standardization and Dependabot config, including auto-merge for minor/patch GitHub Actions — confirm that matches our own review policy before we depend on it upstream.