Ui Kit Bundle Laravel Package

Product Decisions This Supports

• Build vs. buy for admin UI primitives. This package is a thin, opinionated layer on top of Twig: macros, a semantic nowo-ui-* class contract, and page-level components (pagination, tabs, modals). Choosing it is a decision to not build bespoke admin chrome and to not adopt a heavyweight component library (Live Components, UX Toolkit suites, Filament-style panels). It buys a small, readable surface area at the cost of ecosystem gravity.
• Multi-design-system strategy. The "class helper" abstraction (Bootstrap 5, Tailwind, Foundation, custom) is the standout product capability: it lets one template layer target several CSS frameworks. This supports a decision to ship a single admin surface that is theme-portable — useful if you expect to re-skin, white-label, or migrate frameworks without rewriting templates.
• Standardization across a bundle portfolio. The nowo-ui-* semantic layer plus shared macros is a consistency play: one visual and interaction language across internally maintained Symfony bundles and host apps. It reduces per-bundle UI drift and duplicate pagination/modal code.
• Roadmap fit for admin/back-office scope. It maps cleanly to back-office CRUD screens, settings pages, and internal tooling — not to customer-facing or high-design-fidelity product surfaces.
• Vendor/first-party alignment. This is effectively a first-party utility for Nowo's own bundle family (the description literally calls it "canonical"). It should be evaluated as an internal standard, not a community dependency.

When to Consider This Package

Consider it when:

• You are already inside the Symfony/Twig ecosystem (PHP >= 8.1, Symfony 6/7/8) and your admin UI is server-rendered Twig.
• You maintain multiple bundles or apps and want one shared UI vocabulary (nowo-ui-*) rather than copy-pasted macros.
• You need framework-agnostic class helpers — i.e., you genuinely may swap Bootstrap 5 ↔ Tailwind ↔ Foundation, or you support a custom design system.
• You value a small, hackable, MIT-licensed template layer you can fork and own, over a large dependency.
• Low absolute risk is acceptable: internal tools, admin panels, short-lived back-office work.

Look elsewhere when:

• Adoption and support risk matter. Zero stars and zero dependents means no community substrate: no Stack Overflow answers, no third-party tutorials, no informal bug triage, no proven upgrade path. With a single maintainer, bus-factor risk is real. For a long-lived product surface, that is a material liability.
• You are on Laravel or non-Twig stacks. This is a Symfony bundle; the Twig macro and bundle wiring model does not transfer. Porting is a re-implementation, not an integration.
• You need accessibility guarantees, i18n completeness, or a component test suite — none of that is evidenced here, and a 0-star package gives you no external validation.
• You need rich interactivity (complex data grids, drag-and-drop, live validation). Modals/tabs/pagination are the ceiling; reach for a JS component framework instead.
• You require enterprise support, SLAs, or a security disclosure process — none are indicated.
• You would be betting your design system on an unproven semantic CSS contract. nowo-ui-* is a private convention; migrating off it later means touching every template.

How to Pitch It (Stakeholders)

For executives: This is a small, MIT-licensed internal UI kit for our Symfony admin screens. It is not a commercial product and has essentially no external adoption (0 stars, 0 dependents), so it is best framed as an internal standard we can own, fork, and control rather than a dependency we rely on others to maintain. The upside is low cost, full source control, and a single consistent look across back-office tooling; the downside is that we, not a community, carry maintenance, security review, and upgrades. Recommend scoped adoption for internal admin surfaces only, with a named owner.

For engineering: It is a Twig macro + semantic-CSS layer with multi-framework class helpers (Bootstrap 5 / Tailwind / Foundation / custom), covering pagination, tabs, and modals — targeting PHP >= 8.1 and Symfony 6/7/8. It is a thin, readable, hackable layer, which is both the appeal (no framework lock-in at the CSS level) and the risk (no test/accessibility guarantee, single maintainer, unproven nowo-ui-* contract). Treat it as a vendored internal package: pin the version, review changes before upgrade, and be prepared to fork.

Recommendation: Position as a first-party, internal admin UI convention. Adopt where consistency across Symfony back-office bundles is the priority; do not adopt as a public-facing or long-horizon dependency without a named owner and a fork contingency. Track the adoption signal (stars/dependents) as a health metric — at 0/0, the package is unvalidated externally and should be treated accordingly.