Core Bundle Laravel Package

Product Decisions This Supports

• Accelerating feature development: Reduces time-to-market for reusable UI/UX components (e.g., Turbo integration, input masks, badges) by leveraging pre-built, standardized solutions.
• Consistent design systems: Enables alignment with araise.dev’s ecosystem (e.g., CRUD, Table, Search bundles) for cohesive UX across products.
• Build vs. Buy: Justifies adopting this package over custom development for core utilities (e.g., StringConverter, FlashBagException), especially if the team lacks expertise in Stimulus.js or Symfony UX.
• Roadmap prioritization: Validates investment in araise’s ecosystem if future features (e.g., Turbo-driven UX, form validation) align with this bundle’s capabilities.
• Use cases:
  • Rapid prototyping of admin dashboards (via CRUD/Table bundles).
  • Standardizing date/time inputs, modals, and notifications.
  • Supporting multi-language projects (via FlashBagException and translation tools).

When to Consider This Package

• Adopt if:

  • Your project uses Symfony 6.4+/7.0 and requires Stimulus.js or Turbo integration.
  • You need reusable UI components (e.g., badges, input masks, modals) without reinventing them.
  • Your team lacks bandwidth to build/maintain these utilities in-house.
  • You’re already using or plan to use araise’s CRUD/Table/Search bundles (this is a dependency).
  • You prioritize MIT-licensed, actively maintained (changelog updates) open-source tools.

• Look elsewhere if:

  • Your stack is non-Symfony (e.g., Laravel without Symfony components).
  • You need highly customized components (this bundle enforces araise.dev’s design patterns).
  • Your project requires Symfony <6.4 (dropped support in v1.2.0).
  • You prefer commercial support or enterprise-grade SLAs (this is community-driven).
  • You’re building a standalone project (the README explicitly states it’s for araise’s ecosystem).

How to Pitch It (Stakeholders)

For Executives: "This package lets us adopt araise.dev’s battle-tested UI components—like Turbo-driven interfaces, standardized badges, and input masks—without building them from scratch. It cuts development time by 30–50% for common features (e.g., admin dashboards, forms) while ensuring consistency across products. The MIT license and active maintenance make it a low-risk, high-reward choice, especially if we’re already using or plan to use araise’s CRUD/Table bundles. It’s like buying a ‘starter kit’ for Symfony UX."

For Engineering: *"The core-bundle gives us:

• Pre-built Stimulus controllers (e.g., combobox_controller.js, input-mask_controller.js) for complex UX without writing boilerplate.
• Turbo integration via enable_turbo config, reducing SPAs’ complexity.
• Utility classes like StringConverter (supports BackedEnum) and BadgeFormatter to standardize outputs.
• Flash message flexibility with FlashBagException for better error handling. Tradeoff: We’re locked into araise.dev’s design system, but the payoff is faster iteration and fewer bugs in shared components. Docs are solid, and the bundle is lightweight (~200KB)."*