Sulu Site Configuration Bundle Laravel Package

Product Decisions This Supports

• Dynamic Site Customization: Enables per-webspace and per-locale configuration (e.g., logos, contact info, social links) without hardcoding values, reducing frontend-backend coupling.
• Multi-Tenant CMS: Critical for agencies managing multiple client sites within Sulu, allowing granular control over branding/behavior per tenant.
• Build vs. Buy: Avoids reinventing a flexible configuration system, leveraging Sulu’s existing admin UI and Doctrine ORM for data persistence.
• Localization: Supports region-specific settings (e.g., phone numbers, addresses) without duplicating codebases.
• Headless/Decoupled APIs: Provides structured data access for frontend frameworks (React, Vue) or mobile apps via PHP services or Twig templates.
• A/B Testing or Feature Flags: Could extend to environment-specific configurations (e.g., toggle features per webspace).

When to Consider This Package

• Not for Sulu: Avoid if not using Sulu CMS (v3.0+), as it’s a tightly coupled bundle.
• Simple Config Needs: Overkill for static site settings (use Symfony’s ParameterBag or environment variables instead).
• High Customization: Requires XML form definitions; prefer a YAML/JSON-based solution if your team lacks XML familiarity.
• Performance-Critical Apps: Adds a Doctrine entity and admin UI overhead; evaluate caching strategies for high-traffic sites.
• Alternative Bundles: If using Sulu, compare with Sulu’s built-in SettingsBundle for core features.
• Legacy Systems: Requires PHP 8.2+ and Symfony 7.0+; incompatible with older stacks.

How to Pitch It (Stakeholders)

For Executives: "This bundle lets us manage client-specific site settings (logos, contact info, social links) directly in Sulu’s admin panel—no code changes needed. For example, an agency managing 50 client sites can update a logo or phone number for one client without touching the backend. It’s a 10x productivity boost for marketing teams and reduces frontend-backend handoff friction. The MIT license and Sulu integration make it a low-risk, high-reward choice."

For Engineers: *"This provides a structured way to store per-webspace/per-locale configs as JSON entities with a user-friendly admin UI. Key benefits:

• Flexibility: Define custom fields via XML forms (e.g., media uploads, text inputs).
• Accessibility: Retrieve configs in Twig ({{ site_config('key') }}) or PHP ($configService->get()).
• Permissions: Role-based access control via Sulu’s existing system.
• Scalability: Built on Doctrine ORM and Symfony’s ecosystem—easy to extend or migrate later. Tradeoff: Adds a migration step and minor admin UI overhead, but saves hours of custom development. Ideal if you’re already using Sulu v3.0+."*