Bundles Cms Laravel Package

Product Decisions This Supports

• Enterprise-Grade CMS for Symfony: Justify adoption of a full-featured, Symfony-based CMS over lightweight alternatives (e.g., WordPress plugins, Strapi) for projects requiring multi-language support, granular permissions, and workflows (e.g., government portals, e-commerce, or global brands).
• Build vs. Buy: Replace custom-built CMS solutions or legacy systems (e.g., Drupal, custom PHP) with a batteries-included, open-source framework that reduces technical debt while offering versioning, media management, and translation tools.
• Roadmap for Scalability: Enable modular expansion (e.g., adding custom admin modules, ACLs, or workflows) without forking the core codebase, aligning with long-term tech debt reduction.
• Use Cases:
  • Multi-site/multi-language portals (e.g., educational institutions, NGOs).
  • Regulated industries needing audit trails, workflows, and role-based access (e.g., healthcare, finance).
  • Headless CMS backends for decoupled frontends (React, Vue) via Symfony’s API platform.

When to Consider This Package

• Avoid if:
  • You need real-time collaboration (e.g., Google Docs-like editing) → Consider Strapi + Liveblocks or TinaCMS.
  • Your team lacks Symfony/PHP expertise → Evaluate low-code tools (e.g., Contentful, Sanity) or WordPress.
  • You require serverless deployment → Kunstmaan’s Symfony dependency may complicate cloud-native setups (e.g., AWS Lambda).
  • Your project is small-scale or MVP-focused → Overhead of Symfony/Kunstmaan may outweigh benefits; consider Laravel Nova or Directus.
• Look elsewhere for:
  • E-commerce-specific features → Use Sylius or Magento.
  • Markdown-first editing → Ghost or TinaCMS.
  • Jamstack simplicity → Netlify CMS or Contentful.

How to Pitch It (Stakeholders)

For Executives:

"Kunstmaan CMS lets us launch a feature-rich, multi-language digital experience without reinventing the wheel. It’s like WordPress for enterprises—but built on Symfony, so it scales with our tech stack. We get built-in workflows, versioning, and granular permissions out of the box, reducing time-to-market for global sites or regulated content. The MIT license and active community mean we’re not locked into a vendor, and the modular design lets us add custom features as we grow—without technical debt."

ROI Hook:

• Faster launches: Pre-built admin UI, translation tools, and media management.
• Lower risk: Open-source with enterprise-grade features (ACLs, workflows).
• Future-proof: Symfony’s ecosystem ensures long-term support.

For Engineering:

*"Kunstmaan gives us a Symfony-powered CMS with best-in-class features we’d otherwise need to build from scratch:

• Multi-language support with fallback chains and per-field translations.
• Fine-grained ACLs (object/role-based) via Symfony’s ACL system—no custom hacks.
• Drag-and-drop page building with reusable components (no need for a separate page builder like Craft CMS).
• Media library with versioning, hotlink protection, and CDN integration.
• Workflow engine for content approvals (e.g., draft → review → publish).

Trade-offs:

• Symfony dependency: Requires PHP 8.1+, Doctrine, and Symfony’s ecosystem (but aligns with our stack).
• Learning curve: Steeper than WordPress but less than a custom solution.
• Customization: Extend via bundles, menu adaptors, or ACL hooks—no core forks needed.

Migration Path:

• Start with Kunstmaan’s demo site bundle to evaluate the admin UI.
• Use Symfony’s Flex to scaffold custom bundles for domain-specific needs.
• Leverage ACL helpers to secure entities early (e.g., findAllWithPermission() in repositories).

Alternatives Considered:

• Strapi: Headless-first but lacks Symfony’s depth for complex workflows.
• Drupal: Overkill for our needs; Kunstmaan’s Symfony integration is lighter.
• Custom Laravel CMS: Would require reinventing ACLs, media management, etc.

Recommendation: Pilot Kunstmaan for our [Project X] initiative—it’s the fastest path to a scalable, multi-language CMS with enterprise features."*