Page Bundle Laravel Package

Product Decisions This Supports

• Roadmap for a CMS-like feature set: Enables building a lightweight, Symfony-native CMS without bloated solutions like Sonata or EasyAdmin. Ideal for projects needing structured content management with visual editing.
• Build vs. Buy: Justifies building a custom page system over buying a full CMS (e.g., WordPress, Craft) when:
  • You need tight integration with Symfony’s ecosystem (e.g., Doctrine, Twig, security).
  • Visual page builder requirements are simple (blocks, not complex templates).
  • Multilingual support is critical but must align with Symfony’s i18n patterns.
• Use Cases:
  • Marketing sites: Drag-and-drop layouts for landing pages, with SEO fields and scheduling.
  • Internal tools: Structured JSON forms (e.g., contact pages, legal disclaimers) with fixed system pages.
  • Hybrid content: Mix of traditional HTML (CKEditor) and visual blocks for flexibility.
  • Cache optimization: Pre-rendered HTML reduces front-end load (critical for high-traffic sites).
• Technical Debt Mitigation:
  • Replaces ad-hoc Twig templates or manual database content tables with a maintainable, event-driven system.
  • PageSavedEvent hooks enable seamless cache invalidation (Varnish, Redis) without custom logic.
• Localization Strategy: Supports Symfony’s i18n stack (Gedmo Translatable) for per-locale slugs, SEO, and content, reducing duplication.

When to Consider This Package

• Adopt if:

  • Your team is already using Symfony 6.4+ and Aropixel Admin Bundle (or willing to adopt it).
  • You need multilingual pages with per-locale SEO and slugs, but want to avoid heavy CMS overhead.
  • Your content requires structured blocks (e.g., hero sections, testimonials) but not full template customization.
  • You prioritize pre-rendered HTML for performance (zero-cost front-end rendering).
  • Your fixed pages (e.g., homepage, legal) need programmatic access via staticCode.
  • You want to extend the page builder with custom blocks (JS + YAML) without deep frontend work.

• Look elsewhere if:

  • You need advanced templating (e.g., Twig logic in blocks, dynamic components).
  • Your project requires headless CMS capabilities (API-first, decoupled from Symfony).
  • You’re using PHP < 8.2 or Symfony < 6.4 (hard dependency).
  • Your content is highly dynamic (e.g., user-generated layouts with real-time updates).
  • You lack JavaScript build tools (Webpack Encore required for custom blocks).
  • You need collaborative editing (e.g., multiple admins editing simultaneously).
  • Your team prefers commercial support (this is MIT-only, with minimal community activity).

How to Pitch It (Stakeholders)

For Executives:

"This package lets us build a lightweight, Symfony-native CMS for our marketing sites—without the complexity of WordPress or Craft. It gives content editors a drag-and-drop builder for pages (like a simplified Webflow), while developers get structured data, multilingual support, and pre-rendered HTML for performance. Fixed pages (e.g., homepage) are locked in code, reducing risk of accidental deletion. Since it’s pre-rendered, it won’t slow down our front-end, and the PageSavedEvent hook lets us invalidate caches automatically. We’d own the tech stack fully, avoiding vendor lock-in."

Key Outcomes:

• Faster content updates for marketing teams.
• Consistent, SEO-friendly pages across languages.
• Lower hosting costs (no heavy CMS bloat).
• Future-proof for custom integrations.

For Engineering:

*"This is a Symfony-first page management system that replaces manual Twig templates or ad-hoc database tables. It offers three page types:

1. CKEditor for simple HTML (like a basic CMS).
2. Visual builder (JSON → pre-rendered HTML) for structured layouts—no runtime rendering overhead.
3. Custom JSON forms for structured data (e.g., contact pages with address/phone fields).

Why it’s a win:

• Performance: HTML is baked at save time; front-end just outputs {{ page.htmlContent|raw }}.
• Extensible: Add custom blocks via JS + YAML (no frontend framework required).
• Multilingual: Uses Gedmo Translatable for per-locale slugs/SEO/content.
• Fixed Pages: Annotate classes with #[AsFixedPage] to create system pages (e.g., /legal) that can’t be deleted.
• Cache Friendly: PageSavedEvent lets us invalidate Varnish/Redis/CDN in one place.
• Admin Integration: Works seamlessly with Aropixel Admin Bundle (if already in use).

Tradeoffs:

• Requires PHP 8.2+ and Symfony 6.4+.
• Custom blocks need Webpack Encore for JS assets.
• Limited community (1 star, but MIT-licensed and actively maintained by Aropixel).

Recommendation: Pilot this for a non-critical section (e.g., marketing pages) to validate the builder’s UX before full adoption."*

Action Items:

1. Spike: Set up the bundle in a sandbox to test the builder UX and custom block workflow.
2. Compare: Benchmark performance vs. alternative (e.g., manually managed Twig templates).
3. Align: Confirm if Aropixel Admin Bundle is a hard dependency (or if we’d need to build a custom admin UI).