App Bundle Laravel Package

Product Decisions This Supports

• CMS build-vs-buy. Enhavo is a Symfony-based CMS aimed at flexible, custom data structures; app-bundle is the integration layer that boots the CMS inside a Symfony application. This evaluation supports the decision to adopt a self-hosted PHP CMS versus building content and admin tooling in-house.
• Embed vs. stand alone. Because it ships as a bundle rather than a full application, it supports “can we attach CMS capability to our existing Symfony product?” — not “should we run a separate CMS platform?”
• Licensing and hosting posture. MIT-licensed and self-hosted with no per-seat cost; relevant to budget approval and data-residency requirements.
• Roadmap signal, not a dependency. This repo is a read-only subtree split of the main enhavo/enhavo monorepo, published so Composer can install a slice of it. Versioning, roadmap and support decisions must be made against the parent project; this package should never be the thing on the roadmap.
• What it does not decide. Zero stars, zero dependents and a README-only maturity marker mean no external validation. It is not evidence that “the market has chosen this.” It is a candidate for a spike.

When to Consider This Package

Consider it when:

• Your stack is already Symfony/PHP and you want CMS capability as bundles inside the app, not a second system.
• Your content model is complex or custom (arbitrary data structures, admin CRUD) rather than blog-shaped.
• You want MIT-licensed, self-hosted software without subscription or vendor lock-in.
• You accept that documentation, releases and issue tracking live in the main Enhavo repo, and your team can own upgrades.
• You can run a time-boxed spike to confirm Symfony version compatibility with your current codebase.

Look elsewhere when:

• You need an API-first/headless CMS with a broad ecosystem (Strapi, Directus, Contentful) or a mature plugin market (WordPress, Drupal).
• You need commercial support, an SLA or managed hosting.
• Your team is not Symfony-fluent — total cost shifts to in-house engineering.
• You want a standalone installable product: this split package is not that; evaluate the monorepo directly.

How to Pitch It (Stakeholders)

Executives: Enhavo is an MIT-licensed, open-source PHP/Symfony CMS built for flexible, complex content models. It removes license fees and vendor lock-in and lets us extend an existing Symfony codebase instead of operating a second platform. The trade-off is ownership: no support contract, no managed hosting, and weak external adoption signals (zero stars/dependents on this package, which is only a subtree split of the main repo). Recommendation: fund a short, time-boxed engineering spike against enhavo/enhavo before any commitment. Treat this as “validate,” not “standardize.”

Engineering: Treat enhavo/app-bundle as a Composer-level subtree split of the main monorepo — the source of truth for docs, issues and releases is enhavo/enhavo. The bundle is the composition root that wires the CMS into a Symfony app. Before adopting, verify Symfony version compatibility, the upgrade path, and how splits are kept in sync; assume you will read the monorepo for anything non-trivial. Budget for ownership: with no dependency ecosystem, community answers will be scarce.

Product/Design: It supports custom content modeling with a built-in admin UI, which suits internal tools and data-heavy back ends. It is a weaker fit for content-marketing or headless-first requirements without additional integration work.