Kunstmaan Config Bundle Laravel Package

Product Decisions This Supports

• Accelerated CMS Deployment: Reduces manual configuration time for Kunstmaan CMS by standardizing filesystem adapter and LiipImagineBundle integration, enabling faster MVP launches or iterative updates.
• Consistency Across Environments: Eliminates configuration drift between dev/staging/prod by enforcing opinionated defaults (e.g., webroot paths) for media handling.
• Build vs. Buy: Justifies buying this lightweight bundle over custom dev work for teams already using Kunstmaan + LiipImagine, avoiding reinventing configuration patterns.
• Use Cases:
  • Agencies: Rapid client project kickoffs with pre-configured media pipelines.
  • Internal Tools: Non-CMS teams adopting Kunstmaan for content-heavy apps (e.g., documentation portals) where media optimization is critical.
  • Legacy Migration: Standardizing configurations during transitions from custom CMS setups.

When to Consider This Package

• Avoid if:
  • Your project requires custom media storage backends (e.g., S3, Azure Blob) beyond LiipImagine’s filesystem adapter—this bundle enforces a single opinion.
  • You’re not using LiipImagineBundle (the bundle’s sole value is its integration with it).
  • Your team prefers explicit over convention (e.g., you want to manually configure webroot paths per environment).
  • Kunstmaan CMS is deprecated in your stack (this bundle is archived; evaluate long-term support risks).
• Look elsewhere if:
  • You need dynamic configuration (e.g., environment-specific paths via .env files) instead of static parameters.yml.dist values.
  • Your media workflows require advanced features (e.g., CDN integration, custom resolvers) beyond the bundle’s scope.

How to Pitch It (Stakeholders)

For Executives: "This bundle cuts 2–3 hours of manual setup per Kunstmaan project by automating media configuration—critical for hitting deadlines without sacrificing quality. It’s a low-risk, MIT-licensed shortcut for teams already using LiipImagine, with no vendor lock-in. Ideal for rapid deployments or standardizing our CMS footprint across teams."

For Engineering: "This provides a single-source-of-truth for Kunstmaan + LiipImagine media paths, reducing ‘works on my machine’ issues. The tradeoff? You cede control over webroot to a convention (rooted at kernel.root_dir/../web). Perfect if you’re okay with the defaults and want to avoid reinventing this wheel. Note: Archived repo—vet long-term maintenance with the team before adopting."