Core Laravel Package

Product Decisions This Supports

• Enterprise Content Management (ECM) Platform: Accelerate development of a headless CMS or digital experience platform (DXP) by leveraging Ibexa’s core content repository, APIs, and Symfony integration. Reduces time-to-market for content-heavy applications (e.g., e-commerce, publishing, or intranets).
• Build vs. Buy: Buy for teams needing a scalable, feature-rich CMS without reinventing core functionality (e.g., content modeling, multilingual support, or search). Avoid custom builds if requirements align with Ibexa’s out-of-the-box capabilities (e.g., role-based access, embeddings, or external storage).
• Roadmap Priorities:
  • Content Search & AI: Prioritize features like embedding-based search (IBX-9846) or vector similarity for AI-driven content recommendations.
  • Headless APIs: Use the PAPI (PHP API) or REST API to expose content to frontend frameworks (React, Vue) or mobile apps.
  • Multisite/Multilingual: Leverage SiteAccess and content type groups (e.g., ContentTypeGroupName criterion) for global deployments.
  • Performance: Optimize with deterministic image hashing (IBX-11383) or lazy-loading services (e.g., CriteriaConverter).
• Use Cases:
  • Digital Publishing: Structured content with versioning, workflows, and taxonomy support.
  • E-Commerce: Product catalogs with external storage (IBX-11437) for media assets.
  • Intranets/Portals: Role-based access control (RBAC) and user notifications (e.g., bulk mark-as-read).
  • Legacy Migration: Tools like ibexa:io:migrate-files for bulk content imports.

When to Consider This Package

Adopt Ibexa/Core If:

• You need a Symfony-based CMS with content modeling, search (Solr/Elasticsearch), and headless API support.
• Your use case requires multilingual content, workflows, or advanced permissions (e.g., RBAC for user groups).
• You’re building a scalable DXP and want to avoid low-level infrastructure work (e.g., content storage, indexing).
• You need embedding-based search or AI-driven content recommendations (via vector search).
• Your team prefers PHP/Symfony and wants to integrate with existing Symfony services (e.g., Twig, security).

Look Elsewhere If:

• You need a NoSQL/document store (e.g., MongoDB, CouchDB) instead of a relational content model.
• Your project is JavaScript-first (e.g., Strapi, Contentful) or requires a non-PHP backend.
• You need real-time collaboration (e.g., Google Docs-style editing) without Ibexa’s workflow layer.
• Your budget or team lacks resources for Symfony maintenance (e.g., dependency updates, security patches).
• You require offline-first or PWA capabilities (Ibexa is server-centric).

How to Pitch It (Stakeholders)

For Executives:

"Ibexa/Core is a battle-tested, enterprise-grade CMS foundation that lets us ship a scalable digital experience platform faster—without building core infrastructure from scratch. It handles:

• Content at scale: Multilingual, structured content with versioning and workflows (used by global brands like The New York Times).
• Headless flexibility: Expose content via APIs to any frontend (React, mobile) or integrate with marketing tools.
• AI-ready search: Embedding-based search (IBX-9846) enables future-proof content discovery for recommendations or chatbots.
• Cost efficiency: Avoids vendor lock-in while reducing dev time by 30–50% compared to custom builds.

Risk: Minimal—backed by Ibexa’s commercial support and active development (v5.0.x roadmap). We can start with the open-source core and add Ibexa DXP modules later for advanced features like personalization."

For Engineering:

"Ibexa/Core gives us a Symfony-powered CMS with:

• Content Repository: ACID-compliant storage with support for external storage (S3, Azure) and deterministic image hashing to avoid duplicates.
• Search Integration: Out-of-the-box Solr/Elasticsearch with embedding support (IBX-9846) for semantic search.
• APIs: PAPI (PHP) and REST endpoints for headless use cases. Example:

  $contentTypes = $contentTypeService->findContentTypes([
      new ContentTypeGroupNameCriterion('Product'),
  ]);
  

• Performance: Lazy-loaded services (e.g., CriteriaConverter) and batch processing for migrations.
• Extensibility: Custom field types, Twig extensions (ibexa_render with parameters), and event-driven architecture.

Trade-offs:

• Learning curve: Symfony + Ibexa’s domain-specific concepts (e.g., SiteAccess, ContentType).
• Dependency: Tight coupling to Symfony (but aligns with our stack).
• Migration effort: Existing content may need schema adjustments for Ibexa’s model.

Recommendation: Pilot with a headless e-commerce or multilingual portal use case to validate fit. Leverage Ibexa’s Cloud for managed hosting if needed."