Layout Bundle Laravel Package

Product Decisions This Supports

• Deprioritize new adoption; treat as a migration input rather than a build dependency. The package is explicitly deprecated and points to Enabel UX as the successor. Any roadmap item that assumes enabel/layout-bundle as a forward-looking foundation should be re-scoped to either (a) the successor package, or (b) a documented "stay on frozen version" decision with an exit plan.
• Framework fit check before anything else. Despite the brief framing this as a Laravel/PHP package, it is a Symfony bundle (Twig components, SymfonyInsight badge, Symfony application layout helpers). It is not a Laravel package and offers no service providers, Blade views, or Laravel-native integration. Any planned Laravel usage is a non-starter without a bridge layer.
• Build vs. buy: lean "reuse" only for Enabel-aligned Symfony work. The value is a pre-built Bootstrap 5 layout with Enabel's design system, alert components, theme switcher (light/dark), locale switcher, user menu, favicons, error pages, and email templates. That is a meaningful chunk of undifferentiated UI scaffolding — worth reusing if you are already in the Enabel/Symfony ecosystem and accept the visual identity it imposes.
• Roadmap implication: budget for a successor migration, not a greenfield build. Because the successor (Enabel UX) exists, the cheapest path is typically a scheduled migration task rather than an in-house reimplementation of layout and Twig components.
• Use cases it fits: internal Enabel-style Symfony admin back-offices, multilingual apps needing a locale switcher out of the box, projects wanting consistent error/email templates and a dark-mode toggle with minimal effort.

When to Consider This Package

Consider it only when all of the following hold:

• You are building or maintaining a Symfony application (not Laravel, not framework-agnostic PHP).
• You are inside, or deliberately aligning with, the Enabel design system and branding — the styling is opinionated, not neutral.
• You need the specific bundled set: responsive Bootstrap 5 layout, alerts, theme switcher, locale switcher, user menu, favicons, error pages, email templates.
• You accept the deprecated, unmaintained status: no security patches, no PHP/Symfony version guarantees going forward, and a hard dependency on an archived codebase.
• You are willing to pin versions and own the risk, ideally as a short-lived stopgap with a named migration owner.

Look elsewhere when:

• You are on Laravel — this is the wrong ecosystem entirely.
• You need a maintained dependency with a support window, CVE response, or compatibility with future Symfony/PHP releases.
• You want an unbranded or fully themeable design baseline; the Enabel styling is baked in.
• You need a single-purpose component (e.g., just a theme switcher) — pulling an entire layout bundle for one widget is poor value and increases coupling.
• You are greenfield: start directly on the recommended successor, Enabel UX, rather than adopting a package its own maintainers have retired.
• You need community support, a large contributor base, or third-party documentation — there are zero dependents and no external ecosystem to lean on.

How to Pitch It (Stakeholders)

One-liner: A deprecated Symfony UI-layout bundle from Enabel that gives you branded Bootstrap 5 scaffolding, Twig components, dark mode, locale switching, and standard error/email templates — useful as a shortcut today, but not a long-term foundation.

For executives: This is a ready-made front-end kit that saves design and template work on Symfony applications and enforces Enabel's visual standards. The catch is strategic, not technical: the maintainers have retired it and named a successor. Adopting it now means accepting an expiration date. The recommendation is to avoid new commitments to it and, where it is already in use, plan a low-risk migration to Enabel UX on a defined timeline.

For engineering: Expect a clean Symfony bundle with Twig components and decent hygiene signals (CI, Codecov, SymfonyInsight, changelog, tagged releases) — but no ongoing maintenance, no dependents, and no security backport path. It is Symfony-only; it will not work in Laravel without custom work. If you must use it, pin the version, isolate it behind your own layout abstraction so the swap to Enabel UX is a contained change, and record it as technical debt with an owner.

Ask: Approve a short spike to size the Enabel UX migration (or an equivalent in-house layout layer), and gate any new adoption of enabel/layout-bundle behind an explicit exception with a documented exit plan.