Press Laravel Package

Product Decisions This Supports

• Unified CMS + Admin Panel: Enables a Filament-powered admin interface while retaining WordPress as the content management system—ideal for teams needing a modern UI for admin tasks (e.g., user management, plugins) but leveraging WordPress for content creation (e.g., blogs, marketing sites).
• Hybrid Architecture Roadmap: Justifies a build vs. buy decision for teams migrating from WordPress to a custom Laravel backend but needing a gradual transition (e.g., preserving WordPress content while adopting Filament for internal tools).
• Developer Experience (DX) Upgrades: Supports initiatives to reduce WordPress bloat (e.g., decoupling frontend from admin) while keeping familiar workflows for content editors.
• Multi-Tenant or Headless WordPress: Useful for projects where WordPress manages content delivery (via REST API) while Filament handles internal dashboards, analytics, or SaaS portals.
• Legacy System Modernization: Allows incremental modernization of WordPress sites by replacing only the admin panel with Filament, leaving the CMS intact.

When to Consider This Package

• Avoid if:
  • You need a fully decoupled WordPress + Laravel setup (e.g., WordPress as a headless CMS with a separate frontend). This package tightly integrates WordPress into Filament’s ecosystem.
  • Your team is fully committed to Laravel for content management (e.g., using Nova, Forge, or custom admin panels). WordPress adds unnecessary complexity.
  • You require advanced WordPress multisite or custom post type integrations that aren’t yet supported (package is labeled "work in progress").
  • Your infrastructure doesn’t support shared storage (e.g., WordPress files must live alongside Laravel in the same directory structure).
• Consider if:
  • You’re using Filament for admin panels but need WordPress for content editing (e.g., marketing teams resistant to Laravel).
  • You want to modernize WordPress admin without losing existing content or plugins.
  • Your stack includes Laravel + WordPress and you need a seamless integration (e.g., shared auth, unified routing).
  • You’re deploying on Forge/Valet/Herd and can handle minor Nginx/Apache config changes.

How to Pitch It (Stakeholders)

For Executives: "This package lets us keep WordPress for content creation—where our team is already productive—while giving developers a modern, Laravel-based admin panel with Filament. It’s a low-risk way to modernize our tech stack incrementally, reducing WordPress bloat without disrupting our public-facing sites. Think of it as ‘WordPress Lite’ with a Filament-powered control center—ideal for teams that need both familiarity and progress."

For Engineering: *"Moox/Press bridges WordPress and Filament by embedding WordPress into Laravel’s ecosystem. Key benefits:

• Zero content migration: Existing WordPress sites (posts, media, users) remain intact.
• Filament admin: Replace the WordPress dashboard with Filament’s UI for plugins, users, and settings.
• Shared infrastructure: WordPress and Laravel share the same storage, reducing hosting complexity.
• Quick setup: Two commands (composer require + php artisan mooxpress:install) get you 80% there; the rest is minor Nginx/Apache config. Tradeoff: You’re coupling WordPress and Laravel tightly, so it’s best for projects where both are already in the stack. Not ideal for greenfield Laravel-only apps."*

For Content/Marketing Teams: "This keeps your WordPress workflow exactly the same—you’ll still use the familiar editor for blogs and pages—but behind the scenes, our tech team gets a faster, more powerful admin panel. No training needed; no content loss."