Wordpress Bundle Laravel Package

Product Decisions This Supports

• Hybrid CMS Architecture: Enables a unified backend for WordPress (frontend) and Symfony (backend/API) without duplicating content or user management. Ideal for migrating legacy WordPress sites to a headless or decoupled architecture while preserving existing themes/plugins.
• Progressive Migration Roadmap: Allows incremental adoption of Symfony (e.g., new features, APIs, or admin panels) while retaining WordPress for content management. Reduces risk by keeping the existing site live during transition.
• Build vs. Buy: Avoids reinventing integration logic (e.g., user auth, database sync, or event hooks) between Symfony and WordPress. Saves dev time vs. custom development.
• Use Cases:
  • Headless WordPress: Use Symfony as an API layer (e.g., REST/GraphQL) while keeping WordPress for content editing.
  • Monolithic Upgrades: Gradually replace WordPress plugins with Symfony services (e.g., custom post types → Doctrine entities).
  • Multi-Tenant Systems: Share user authentication/roles between Symfony and WordPress (e.g., admin dashboards).
  • Localization: Cross-application i18n (e.g., Polylang cookie sync for language switching).
  • Password-Protected Content: Integrate WordPress password logic into Symfony templates.

When to Consider This Package

• Adopt When:

  • Your team is already using Symfony and needs to integrate with WordPress without forking core logic.
  • You require deep Symfony-WordPress interop (e.g., shared users, database access, or event dispatching) beyond simple REST APIs.
  • You’re building a hybrid system where Symfony handles business logic/APIs and WordPress manages content/themes.
  • You need incremental migration (e.g., move plugins to Symfony services over time).
  • Your project uses Symfony’s ecosystem (Twig, Doctrine, security) and wants to leverage it for WordPress-related tasks.

• Look Elsewhere If:

  • You need a pure headless solution: Use WordPress as a CMS + a separate API (e.g., WP REST API + custom Symfony client).
  • You’re not using Symfony: This bundle is Symfony-centric; alternatives like WP-API or Spatie Laravel WordPress may fit better.
  • You require real-time sync: This bundle is request-based; consider webhooks or cron jobs for async updates.
  • Your WordPress setup is highly customized: Complex plugins/themes may conflict with Symfony’s routing or template overrides.
  • You need multi-site support: This bundle targets single-site setups (check forks or custom extensions).

How to Pitch It (Stakeholders)

For Executives:

"This bundle lets us merge the best of WordPress (content management, themes) with Symfony (scalability, APIs, and modern tooling) without a full rewrite. We can:

• Keep our existing WordPress site live while gradually adding Symfony features (e.g., a new admin dashboard or API).
• Reduce technical debt by replacing custom WordPress plugins with Symfony services (e.g., Doctrine entities for posts/users).
• Unify authentication and user roles across both platforms, cutting down on siloed systems.
• Future-proof our stack by adopting Symfony’s ecosystem (e.g., Twig templates, security, or GraphQL) while preserving our content workflow. This is a low-risk way to modernize our tech stack incrementally, with minimal disruption to our live site."

For Engineers:

"This bundle provides a battle-tested bridge between Symfony and WordPress, giving us:

• Shared Infrastructure: Access WordPress databases (posts, users, etc.) via Symfony services (e.g., ekino.wordpress.manager.post). No need to write custom DB queries.
• Seamless Auth: Sync WordPress logins with Symfony’s security system (including role mapping) using the ekino-wordpress-symfony plugin.
• Event Integration: Dispatch WordPress hooks (e.g., wp_head) as Symfony events for custom logic.
• Template Flexibility: Embed WordPress headers/footers in Symfony Twig templates or vice versa.
• Migration Path: Start by using Symfony for new features (e.g., APIs) while keeping WordPress for content, then incrementally move more logic to Symfony. Trade-offs: It’s not a silver bullet—requires careful routing setup and may need tweaks for complex plugins. But it’s far faster than building this from scratch."*

For Design/Content Teams:

"This won’t change how you work with WordPress—you’ll still edit content, themes, and plugins as usual. But behind the scenes, we’re adding a layer that:

• Keeps your WordPress site stable while we build new features in Symfony.
• Lets us reuse your content in modern ways (e.g., mobile apps, custom dashboards) without rewriting everything.
• Ensures your login and permissions work the same way across both systems. No action needed from you—this is an under-the-hood improvement!"