Hybrid Platform Ui Core Components Laravel Package

Product Decisions This Supports

• Frontend architecture reference (not direct adoption): This is a set of Polymer-based custom elements (<ez-platform-ui-app>, <ez-navigation-hub>, <ez-toolbar>) plus an eZ.TabsMixin for markup-driven tabs. It illustrates a component contract for a platform shell — app chrome, navigation hub, and toolbar — that a PM can use as a benchmark when scoping an internal design system or admin shell, not as a dependency to ship.
• Build vs. buy for UI shell primitives: If a roadmap item is "consistent admin navigation, toolbar, and tabbed panels across a Laravel-backed application," this package is a data point for evaluating whether to build those primitives in-house (likely yes) versus inheriting a third-party element set.
• Legacy/ecosystem awareness: It is part of the eZ Platform (Ibexa) Hybrid Platform UI lineage and is archived. It informs migration and platform-consolidation decisions — e.g., "are we inheriting an eZ/Ibexa front end that depends on these elements, and what is the exit path?"
• Tabs interaction pattern decision: The eZ.TabsMixin and its ez-tabs/ez-tabs-list/ez-tabs-panel CSS contract give a concrete, low-friction model for accessible-ish tab markup that a PM can cite when writing acceptance criteria for tabbed content components.
• Not a viable candidate for new feature work: With 0 stars, 0 dependents, an archived repository, and no meaningful community, it does not support "add to stack" decisions. It supports avoidance and reference decisions.

When to Consider This Package

Consider it only as reference material when:

• You are maintaining or migrating an existing eZ Platform / Ibexa Hybrid Platform UI application and need to understand the expected DOM contract for the app shell, toolbar, or tabs.
• Your team is defining an internal component library and wants a documented precedent for a markup-driven tabs mixin and shell elements.
• You need to document a legacy dependency for an architecture review or a decommissioning plan.

Look elsewhere when:

• You are starting any new build. The repository is archived, has 0 stars and 0 dependents, and shows only basic README/docs maturity — no active maintenance, no security response, no support path. Adopting it creates unowned risk.
• You need a Laravel/PHP-side package. Despite the framing, this is a frontend web components library (Polymer custom elements), not a Composer/PHP package; it is not a Laravel integration and provides no server-side capability.
• You need modern, framework-agnostic UI primitives. Prefer actively maintained, standards-based options (native Web Components with Lit, or your framework's own component library) rather than Polymer-era custom elements.
• You need accessibility guarantees, browser support commitments, or a published versioning/deprecation policy — none are evident here.

How to Pitch It (Stakeholders)

To executives: This is an archived, zero-adoption frontend component package from the eZ Platform ecosystem — not a PHP/Laravel dependency. My recommendation is do not adopt it in any new product. It carries maintenance, security, and support risk with no upside. Its only value is as a reference artifact if we are touching or migrating a legacy eZ/Ibexa front end. Net decision: no roadmap investment; treat it as documentation, not a dependency.

To engineering: The package provides Polymer custom elements for the platform shell (<ez-platform-ui-app>, <ez-navigation-hub>, <ez-toolbar>) and an eZ.TabsMixin implementing markup-based tabs with bundled tab CSS. It is archived, unmaintained, 0 stars, 0 dependents, README/docs-only maturity, and it is a client-side web components library, not a Composer/PHP package. Use it to understand the legacy DOM contract and tab pattern if you're working in an existing Hybrid Platform UI codebase; otherwise build shell and tab primitives on maintained, standards-based tooling. Flag any current transitive dependency on it as tech debt with a defined exit plan.