Wordpress Core Installer Laravel Package

Product Decisions This Supports

• Build vs. Buy: Accelerates WordPress deployment by leveraging a lightweight, open-source package (avoiding custom development for core installation logic).
• Feature Expansion: Enables WordPress-specific installation paths in Laravel-based projects (e.g., multi-site setups, microservices, or headless WordPress integrations).
• DevOps/Infrastructure: Simplifies CI/CD pipelines for WordPress-heavy applications by automating core installation via Composer.
• Roadmap: Critical for projects requiring WordPress as a submodule (e.g., custom themes/plugins, hybrid Laravel-WordPress apps).
• Use Cases:
  • Installing WordPress in non-standard paths (e.g., web/edition/).
  • Standardizing WordPress deployments across a Laravel monorepo.
  • Integrating WordPress with Laravel’s dependency management.

When to Consider This Package

• Adopt if:

  • Your project uses Laravel + WordPress (e.g., custom plugins, headless CMS, or hybrid apps).
  • You need automated WordPress core installation via Composer (reducing manual setup).
  • Your team prioritizes consistency in WordPress deployments across environments.
  • You’re already using johnpbloch/wordpress-core (this package extends its functionality).

• Look elsewhere if:

  • You require full WordPress stack management (e.g., plugins, themes, DB setup)—this only handles core installation.
  • Your project doesn’t use Composer for dependency management.
  • You need multi-site or advanced WordPress configurations (consider dedicated tools like WP-CLI or Bedrock).
  • You’re not using Laravel (the package is Laravel/Composer-centric).

How to Pitch It (Stakeholders)

For Executives: "This package lets us automate WordPress core installation via Composer—saving dev time and ensuring consistency across deployments. For Laravel projects integrating WordPress (e.g., custom plugins or headless CMS), it’s a lightweight, open-source solution to replace manual setup. Low maintenance (last updated 2023) and aligned with our existing Composer workflows."

For Engineering: *"The metabolism/wordpress-core-installer extends Composer’s installer-paths to support WordPress core in custom directories (e.g., web/edition/). It pairs with johnpbloch/wordpress-core to handle WordPress updates seamlessly. Ideal for:

• Laravel + WordPress projects needing standardized installs.
• CI/CD pipelines where WordPress is a dependency.
• Teams avoiding WP-CLI or manual wp-core commands. Tradeoff: Only handles core; plugins/themes require additional tooling (e.g., WP-CLI or custom scripts)."*