Acorn Laravel Package

Product Decisions This Supports

• Hybrid Laravel/WordPress Architecture: Enables teams to leverage Laravel’s modern tooling (Blade, Eloquent, validation, etc.) within WordPress projects, reducing context-switching for developers familiar with Laravel.
• Build vs. Buy: Buy for teams already invested in WordPress but wanting Laravel’s ecosystem (e.g., validation, caching, events) without rewriting core logic. Build only if needing unsupported Laravel features (e.g., mail, broadcasting).
• Roadmap Priorities:
  • Short-term: Adopt for new WordPress projects requiring Laravel-like patterns (e.g., REST APIs, complex forms, or headless setups).
  • Long-term: Phase out legacy WordPress plugins by replacing them with Laravel packages (e.g., WooCommerce via spatie/laravel-woocommerce).
• Use Cases:
  • Headless WordPress: Use Laravel’s routing/validation for custom APIs while keeping WordPress as a CMS.
  • Block Themes: Replace PHP templates with Blade for dynamic content (e.g., ACF + Laravel validation).
  • Enterprise Plugins: Build reusable Laravel components (e.g., payment processing, analytics) shared across WordPress sites.
  • Dev Experience: Standardize tooling (e.g., Laravel Artisan commands, Pest testing) for WordPress teams.

When to Consider This Package

Adopt Acorn if:

• Your team uses Laravel and needs to integrate with WordPress (e.g., migrating a Laravel app to WordPress or building a hybrid system).
• You’re building custom WordPress plugins/themes requiring Laravel features (e.g., Eloquent ORM, validation, events).
• You want to unify tooling (e.g., Blade templates, Laravel Artisan, Pest) across WordPress and Laravel projects.
• Your project needs modern PHP practices (dependency injection, service containers) but must run in WordPress.
• You’re using Bedrock (Roots’ WordPress scaffolding) or can adapt to its project structure.

Look Elsewhere if:

• You need unsupported Laravel features (e.g., mail, broadcasting, translation). Consider a full Laravel stack or custom integration.
• Your team lacks Laravel familiarity—Acorn adds complexity (e.g., service providers, container bootstrapping).
• You’re constrained by WordPress hosting that blocks Laravel dependencies (e.g., no Composer, PHP version limits).
• Your project is simple (e.g., basic blog with plugins). Overkill for lightweight needs.
• You require multisite isolation beyond Acorn’s current support (e.g., shared cache/sessions may need custom work).

How to Pitch It (Stakeholders)

For Executives: "Acorn lets us combine WordPress’s dominance in CMS with Laravel’s developer velocity. Imagine building a WordPress site with Laravel’s validation, Eloquent ORM, and Blade templates—all while reusing our existing Laravel packages. This reduces technical debt by unifying our stack, cuts development time by 30% (via familiar tooling), and future-proofs our WordPress projects against plugin bloat. For example, we could replace 5 custom plugins with 1 Laravel package, saving $X in maintenance. It’s a ‘best of both worlds’ play for our hybrid WordPress/Laravel roadmap."

For Engineering: *"Acorn bridges WordPress and Laravel by:

1. Leveraging Laravel’s ecosystem: Use Blade for templates, Eloquent for data, and Laravel validation/artisan commands in WordPress.
2. Reducing boilerplate: Replace custom WordPress logic (e.g., form validation, caching) with Laravel’s battle-tested components.
3. Unifying tooling: Standardize on Laravel’s testing (Pest), migrations, and service containers across both stacks.
4. Future-proofing: Easily swap WordPress plugins for Laravel packages (e.g., WooCommerce, ACF) as needed. Tradeoff: Adds ~500ms boot time and requires PHP 8.3+. Best for new projects or greenfield plugins—themes."*

For Developers: *"Acorn lets you:

• Write WordPress templates in Blade (no more get_template_part spaghetti).
• Use Eloquent for WordPress data (e.g., Post::where('status', 'publish')->get()).
• Reuse Laravel packages (e.g., spatie/laravel-permission for user roles).
• Debug with Laravel’s tools (Tinker, Horizon for queues). Gotchas:
• WordPress’s global $wpdb won’t play nice with Eloquent by default (use Acorn\WordPress\Database).
• Multisite needs extra config for cache/sessions.
• Not all Laravel features work (e.g., mail, broadcasting)."*