Core Bundle Laravel Package

Product Decisions This Supports

• Standardizing CRUD Operations: Accelerate development by providing a reusable BaseEntity and FormHandler abstraction for common database operations (create, update, soft-delete), reducing boilerplate code across projects.
• Soft-Deletion & Audit Trails: Enable consistent soft-delete functionality and timestamp tracking (created/updated) without reinventing the wheel, improving data integrity and compliance.
• Pagination & Routing: Integrate KnpPaginatorBundle for seamless pagination and FoSJsRoutingBundle for clean URL routing, enhancing UX and maintainability.
• Build vs. Buy: Avoid building custom Doctrine listeners/filters for soft-deletes or timestamps, saving engineering time and reducing technical debt.
• Use Cases:
  • Internal admin panels or CMS backends where CRUD operations are repetitive.
  • Projects requiring soft-delete functionality (e.g., user accounts, content management).
  • Teams prioritizing rapid prototyping with standardized entity behaviors.

When to Consider This Package

• Avoid if:
  • Your project uses Symfony 3+ (this bundle targets Symfony2).
  • You need hard deletes (soft-delete is the only deletion strategy).
  • Your team prefers custom solutions over abstractions (e.g., existing Doctrine behaviors or libraries like API Platform).
  • You require active maintenance (0 stars, no recent commits, untested maturity).
• Look elsewhere if:
  • You need advanced validation or complex business logic—this bundle focuses on CRUD scaffolding.
  • Your stack includes non-Doctrine ORMs (e.g., Eloquent, Propel).
  • You prioritize modern PHP/Laravel features (e.g., Eloquent events, Laravel Scout).

How to Pitch It (Stakeholders)

For Executives: "This bundle cuts 30%+ of boilerplate code for common database operations in Symfony2, accelerating feature delivery. It standardizes soft-deletes and audit trails (created/updated timestamps) across entities, reducing bugs and compliance risks. Ideal for internal tools or CMS backends where CRUD is repetitive. Low risk—MIT licensed and integrates with existing Symfony2 stacks."

For Engineering: *"BaconCoreBundle provides:

1. BaseEntity with soft-delete and timestamp behaviors (no more manual Doctrine listeners).
2. FormHandler for DRY CRUD operations (create/update/delete).
3. KnpPaginator and JsRouting out-of-the-box for pagination and clean URLs. Tradeoff: Symfony2-only, minimal community support. Best for greenfield projects or legacy Symfony2 maintenance. Avoid if you need hard deletes or modern Laravel features."*