Container Laravel Package

Product Decisions This Supports

• Accelerated MVP Development: Enables rapid prototyping of WordPress-based PHP applications by abstracting dependency management (e.g., services, repositories, or external APIs) into a containerized architecture. Reduces boilerplate for service wiring, allowing PMs to focus on core product logic.
• Decoupling & Modularity: Supports a microservices-like approach within WordPress, aligning with roadmaps for scalable, maintainable plugins/themes. Ideal for teams building modular products (e.g., headless CMS integrations, SaaS plugins).
• Build vs. Buy: Justifies buying this lightweight package over custom DI containers (e.g., PHP-DI) when:
  • WordPress-specific integrations (e.g., WP_Hooks, WP_Query) are needed.
  • The team lacks PHP DI expertise but needs dependency injection (DI) for non-WordPress services.
• Use Cases:
  • Plugin Development: Isolate business logic (e.g., payment processing, analytics) from WordPress core.
  • Theme Frameworks: Manage dynamic components (e.g., theme customizer services, API clients) cleanly.
  • Hybrid Apps: Bridge WordPress with Laravel/non-WP services (e.g., auth via Laravel Sanctum, caching via Redis).
  • Testing: Simplify mocking dependencies in PHPUnit by leveraging the container’s binding system.

When to Consider This Package

• Adopt When:
  • Your team is building WordPress plugins/themes requiring DI (e.g., >5 interdependent services).
  • You need WordPress-native DI but want to avoid reinventing the wheel (vs. PHP-DI or manual wiring).
  • Your roadmap includes modular components (e.g., reusable services across multiple products).
  • You’re integrating non-WP services (e.g., Stripe, Mailchimp) into WordPress without tight coupling.
• Look Elsewhere If:
  • You’re not using WordPress (this package is WP-specific; use PHP-DI or Laravel’s container instead).
  • Your project is simple (<3 services) or lacks DI needs (manual wiring may suffice).
  • You require advanced features (e.g., circular reference detection, context-aware bindings) not covered by this package.
  • Your team prefers Laravel’s ecosystem (this package isn’t Laravel-first; consider Laravel’s Illuminate/Container for cross-platform needs).

How to Pitch It (Stakeholders)

For Executives: "This package lets us ship WordPress products faster by automating dependency management—think of it as ‘Laravel’s service container, but for WordPress.’ It reduces technical debt in plugins/themes by abstracting service wiring (e.g., payments, APIs), so our devs focus on features, not plumbing. For example, if we’re building a [use case: e.g., ‘subscription plugin’], this cuts setup time by 30% while keeping the codebase clean and scalable. The MIT license and lightweight design mean no vendor lock-in, and it integrates seamlessly with our existing WordPress stack."

For Engineering: *"wp-starter/container is a minimal DI container tailored for WordPress. It’s not PHP-DI or Laravel’s container, but it’s WordPress-aware—meaning it plays nicely with hooks, filters, and the WP core. Key benefits:

• Bind services once, use anywhere: Register a StripeService in the container, and inject it into any class (plugins, themes, or custom components).
• WordPress integration: Built-in helpers for binding WP-specific classes (e.g., WP_Query, WP_REST_Request).
• Testability: Mock dependencies easily by swapping bindings in tests.
• Lightweight: ~10KB, no bloat—just what you need for DI without Laravel’s overhead.

Use it when you’re tired of newing services everywhere or fighting circular dependencies in WordPress. Avoid it if you’re doing vanilla PHP or need Laravel’s full stack."*

For Developers: *"Need to inject a UserRepository into your plugin class? No more new UserRepository()—just bind it in the container and let it handle the rest. Here’s how it works:

// Register a service
$container->bind('Stripe', function () {
    return new StripeService(config('stripe_key'));
});

// Use it anywhere
$stripe = $container->make('Stripe');

It’s like Laravel’s container but for WordPress. Perfect for:

• Plugins with complex logic (e.g., membership systems).
• Themes with dynamic components (e.g., custom post type handlers).
• Projects mixing WordPress + external APIs (e.g., Shopify, Zoom).

Pro tip: Pair it with wp-cli for easy service registration during deployments."*