Site Bundle Laravel Package

Product Decisions This Supports

• Microservices-First Architecture: Enables a modular, lightweight CMS layer for aggregating business logic microservices, reducing monolithic CMS complexity.
• Headless CMS Strategy: Ideal for decoupling content management from presentation, allowing teams to use best-of-breed tools (e.g., GitHub, Dropbox) for collaboration.
• Developer Experience (DX): Lowers onboarding friction for developers unfamiliar with traditional CMS platforms by leveraging familiar PHP/Symfony tools.
• Roadmap for Composable Systems: Supports incremental adoption—start with CoralSiteBundle for routing/content rendering, then expand with other Coral bundles (e.g., authentication, media).
• Build vs. Buy: Avoids reinventing a full CMS; instead, "buys" a lightweight abstraction layer to integrate with existing microservices.
• Use Cases:
  • Enterprise portals with dynamic content needs.
  • Multi-brand/multi-region sites requiring flexible content routing.
  • Teams prioritizing developer velocity over out-of-the-box CMS features.

When to Consider This Package

• Adopt if:

  • Your architecture leans toward microservices, and you need a lightweight CMS layer to glue them together.
  • Your team prefers code-over-configuration (e.g., YAML/JSON for content structures) and avoids proprietary CMS backends.
  • You require multi-repository collaboration (e.g., GitHub for content branching) or mobile-friendly editing (e.g., VS Code for content management).
  • Your priority is developer productivity over marketing-ready CMS features (e.g., WYSIWYG editors, drag-and-drop).
  • You’re using Symfony and want to avoid vendor lock-in with monolithic CMS solutions.

• Look elsewhere if:

  • You need a turnkey CMS with built-in user roles, workflows, or media libraries (e.g., Strapi, Directus).
  • Your team lacks PHP/Symfony expertise or requires a JavaScript-based solution.
  • You need real-time collaboration features (e.g., concurrent editing) beyond Dropbox/GitHub integrations.
  • Your project timeline demands active maintenance (last release: 2022; no dependents).
  • You require scalable authoring tools (e.g., for non-technical content editors).

How to Pitch It (Stakeholders)

For Executives: "CoralSiteBundle lets us treat content like code—stored in GitHub, edited in VS Code, and deployed via CI/CD—while keeping our microservices architecture intact. It’s a lightweight alternative to bloated CMS platforms, reducing dev overhead and enabling faster iterations. Think of it as ‘Git for content,’ but with Symfony’s reliability. The MIT license and modular design mean we own our stack, and the focus on developer experience aligns with our tech talent strategy."

For Engineering: *"This bundle gives us a Symfony-native way to handle content routing and rendering without locking us into a monolithic CMS. Key benefits:

• No UI constraints: Use your favorite editor (even mobile) for content.
• Microservice-friendly: Content lives alongside business logic, not in a separate silo.
• Future-proof: Coral’s design assumes a microservices world—we’re not betting on a dying architecture.
• Low risk: MIT license, tested code, and Docker support for easy local dev. Tradeoff: We’ll need to build custom workflows for non-dev users, but the payoff is flexibility and control. Let’s prototype a single page type to validate the DX before committing."*