Laravel Inertia Vue Starter Kit Laravel Package

Product Decisions This Supports

• Build vs. buy (or rather, build vs. fork): This release makes the starter kit a more credible foundation for authenticated SaaS-style products. Email verification, registration emails, and user suspension are exactly the "table stakes" features PMs usually budget sprint time for; their inclusion shifts the build-vs-adopt calculus toward adoption for early-stage products.
• Roadmap sequencing: Because verification and suspension now ship in the kit, roadmap items like "onboarding trust gates," "abuse/moderation controls," and "transactional email lifecycle" can be pulled forward or re-scoped rather than treated as net-new engineering epics.
• Account lifecycle strategy: User suspension is an admin/trust-and-safety primitive. Its presence supports product decisions around moderation, ToS enforcement, trial abuse prevention, and paid-tier downgrade handling without bespoke build.
• Scope discipline for MVP: Teams can defer investment in custom auth flows and email infrastructure, concentrating product discovery and differentiation work elsewhere.
• Platform consistency: The "best practices" and CI/GH Actions fix signal a maintainable baseline, supporting decisions to standardize multiple internal Laravel products on one starter kit rather than bespoke scaffolds.
• Risk/velocity trade-off: Adopting an opinionated starter kit (Inertia + Vue) is itself a stack decision with long-term hiring and architecture implications — a PM should own that call, not leave it purely to engineering preference.

When to Consider This Package

Consider it when:

• You're starting a new Laravel product with server-driven pages plus a Vue front end, and Inertia's monolith-with-SPA-feel model matches your team's skills.
• You need standard auth lifecycle out of the box (registration, verification, transactional emails, suspension) and would otherwise spend 2–4 sprints replicating it.
• Your team is small and full-stack, prefers a single deployable app over separate API/SPA services, and benefits from convention over configuration.
• You want a maintained reference implementation of Laravel/Inertia best practices to standardize on across teams.
• You need basic moderation/trust-and-safety levers early, so suspension and account state management aren't an afterthought.

Look elsewhere when:

• You need a public, versioned API consumed by third parties or multiple clients — a starter kit's Inertia coupling may fight that model.
• Your product requires enterprise SSO/SAML, SCIM, complex RBAC, or fine-grained permissions beyond verification and suspension.
• You are already deep into an existing codebase — retrofitting a starter kit is generally not worth it.
• Your front end must be React, Svelte, or mobile-first, or you require a separate-headless backend architecture.
• You have strict compliance constraints (e.g., regulated identity proofing) where a scaffolded flow is insufficient and audited vendor solutions are required.
• You depend on a stable, semver-guaranteed public API; starter kits evolve with opinionated changes and are not a library contract.

How to Pitch It (Stakeholders)

For executives: This release turns a well-known Laravel starter kit into a more complete product foundation. Three of the highest-friction account features — email verification, registration/welcome emails, and user suspension — are now included rather than built from scratch. In practical terms, that's several sprints of undifferentiated engineering we don't have to fund on the next Laravel-based product, plus a working answer to trust-and-safety and abuse-prevention needs on day one. It also reduces the risk of every team hand-rolling auth differently.

For engineering: Version 7.1.0 adds an email verification flow, transactional registration emails, and user suspension, alongside best-practice cleanups and a CI/GitHub Actions fix. It's a starter kit rather than a runtime dependency, so adoption is a one-time scaffold decision, not an ongoing upgrade obligation — though it does lock in an opinionated Inertia + Vue architecture and the maintenance model of a community-maintained project.

Recommended ask: Approve a short, time-boxed spike (roughly one to two weeks) to validate the kit against our next product's requirements — particularly around roles/permissions and any API exposure — and report back with a build-vs-adopt recommendation before we commit the team to it.