Design Laravel Kit Laravel Package

Product Decisions This Supports

• Build vs buy: For Laravel/Blade teams needing a ready-made UI kit with layout, navigation, form controls, and an Italian SPID login button, this package reduces custom frontend work. New showFooter and Select $slot/placeholderDisabled options let PMs approve minimal login pages and filter UIs without one-off components.
• Roadmap: CSP nonce support via @designLaravelKitScripts unblocks adoption in security-sensitive or public-sector environments; prioritize it for releases targeting strict Content Security Policy. SPID provider validation reduces runtime surprises in identity flows.
• Use cases: Citizen-facing portals, internal admin panels, login/minimal layouts, filter-heavy lists, and Blade apps where megamenu/nav behavior should be deterministic rather than HTML-string sniffing.
• Feature tradeoffs: Prefer Blade-idiomatic APIs ($slot options) over custom JS; rely on explicit megamenu flags to avoid false positives. Docs now cover component parameters and URL policy migration, lowering integration and support cost.

When to Consider This Package

• Adopt when: stack is Laravel + Blade; you need prebuilt layout/nav/select/SPID components; you require CSP nonce support; you value fast delivery over a fully custom design system; you can accept a 0.x package and track minor migrations (e.g., 0.4 → 0.5 URL validation).
• Look elsewhere when: you need React/Vue/Inertia-first components, a mature 1.x+ dependency with formal SLAs, no SPID/Italian public-sector requirements, a design language that conflicts with the kit, or heavy white-label customization that would fork most components.
• Evaluate before adoption: maintenance cadence, test coverage beyond noted fixes, accessibility guarantees, and whether URL-policy changes in 0.5 affect existing content.

How to Pitch It (Stakeholders)

• Executives: This package accelerates delivery of Laravel UI—including SPID login and CSP-compliant script loading—while reducing bespoke frontend code and compliance risk. It is best suited to teams already on Laravel/Blade and willing to manage a 0.x dependency.
• Engineering: v0.5.2 adds practical controls (footer toggle, Blade slot options, placeholder selection), hardens megamenu detection, validates SPID provider config, and improves test isolation/docs. It remains Blade-native and configurable; confirm versioning/support expectations before standardizing.