Ux Laravel Package

Product Decisions This Supports

• Adopt or retain the shared layout for unauthenticated flows. The base Bootstrap layout is what login, password reset, and other shell pages render against. This release directly improves those pages, which are high-traffic, low-differentiation surfaces where a shared upstream layout is usually cheaper than an in-house one.
• Privacy and compliance posture. Dropping the jsDelivr CDN and, via theme 4, self-hosting fonts removes a third-party request that sent visitor IP addresses to Google Fonts. That is a concrete GDPR/ePrivacy exposure reduction and shrinks the scope of consent-banner and sub-processor discussions. Worth weighing as a risk-reduction item, not just a technical cleanup.
• Upgrade sequencing on the roadmap. v2.6.0 is a minor release that silently changes runtime behavior: no more CDN-provided global window.bootstrap, and Font Awesome / flag-icons are no longer bundled by the theme. Treat it as a migration task with verification, not a routine dependency bump.
• Defect triage. Duplicate Bootstrap JS produced double event handlers on dropdowns and collapses. If bug reports mention toggles firing twice or elements collapsing immediately after opening, this release likely closes them — useful evidence when prioritizing a fix.
• Build vs. buy on frontend foundations. The bundle is a thin template layer, not a component library. Each release like this is a reminder to decide whether you continue consuming upstream layout decisions or fork the base templates and own them.
• Dependency and asset-ownership policy. With importmap:update ignoring version constraints and pulling theme 4, the team needs a stated position on pinning theme 3 vs. moving to 4, and on which entrypoint owns Bootstrap and theme imports.

When to Consider This Package

Consider adoption when:

• The product is server-rendered PHP/Twig and already uses (or intends to use) the Enabel Bootstrap theme for brand consistency.
• You need a small, maintained set of base layouts and auth-page shells rather than a full design system.
• Your team owns a single JS entrypoint (app.js or equivalent) and is comfortable importing Bootstrap and the theme there.
• Accessibility and consistent defaults on login/reset pages matter more than bespoke styling.

Look elsewhere when:

• The frontend is a SPA, Inertia, Livewire, or Tailwind-based stack where Twig layout inheritance is not the rendering path.
• You need a component library with documented APIs, versioned releases, and support commitments — this is a template bundle, and the changelog is the contract.
• You cannot guarantee control over the asset entrypoint; the window.bootstrap removal will break inline scripts that assumed a CDN global.
• You rely on fa-* or fi fi-* classes and are unwilling to add and maintain those imports yourself after theme 4.
• You require strict semver guarantees; behavior-changing fixes have shipped in a minor version here.

How to Pitch It (Stakeholders)

To executives: A small, low-cost upgrade that removes an external CDN dependency and stops sending visitor IP addresses to Google Fonts from our login and password-reset pages — a real privacy and legal-risk reduction. It also fixes duplicated JavaScript that caused dropdowns and collapsible sections to misbehave on those pages. No new infrastructure, no vendor spend.

To engineering: Minor version, but behavior-affecting. The base layout no longer injects theme CSS or bootstrap.bundle.min.js from jsDelivr; stylesheets is empty and javascripts only renders importmap('app'), so assets/app.js must import bootstrap and the theme stylesheet. The CDN global window.bootstrap is gone — any inline script using it must import from bootstrap instead. Theme 4 is now allowed (^3.0.2 || ^4.0) and self-hosts fonts but drops Font Awesome and flag-icons; if templates use fa-* or fi fi-*, add those imports before running importmap:update, since it ignores version constraints and will pull theme 4. Template overrides of the stylesheets and javascripts blocks are unaffected, so existing customizations keep working. Verify auth pages first — they were the ones loading the theme twice.