Content Browser Laravel Package

Product Decisions This Supports

• PHP 8 migration / platform sustainment: This release is primarily a compatibility and packaging release: the 1.4 line is now published as se7enxweb/content-browser, replaces netgen/content-browser, and allows PHP 8.0 for Platform 2.5 installs on PHP 8.0 (CJW Exponential Platform Nexus). It supports the roadmap decision to keep a legacy Platform 2.5 deployment on a supported PHP runtime without rebuilding content-browsing functionality.
• Build vs. buy / fork decision: For teams needing Netgen Content Browser behavior on Platform 2.5 + PHP 8.0, adopting this fork is likely cheaper than building a custom content-selection UI. The trade-off is dependency on a community/third-party fork rather than the original vendor package.
• Feature use cases: Supports editorial workflows that require browsing, selecting, and embedding existing content into pages or other content structures. The PM should treat it as admin/editorial infrastructure, not as a differentiating product feature.
• Dependency and supply-chain management: The package-name change from netgen/content-browser to se7enxweb/content-browser is the most important product signal. It affects Composer requirements, upgrade planning, security monitoring, and long-term maintenance ownership.
• Release scope: 1.4.2 is based on Netgen Content Browser 1.4.1 and appears to be a maintenance/fork publication rather than a feature release. Do not position it as a new capability; position it as an upgrade enabler and risk decision.

When to Consider This Package

Consider se7enxweb/content-browser when:

• You run an eZ Platform 2.5 / CJW Exponential Platform Nexus deployment on PHP 8.0 and need existing Content Browser functionality.
• You currently depend on netgen/content-browser and need a PHP 8.0-compatible 1.4.x line.
• You can accept a third-party/community fork, including the package rename and the need to track upstream Netgen releases.
• Your editorial product depends on content browsing/selection inside the admin experience, and replacing it would create meaningful delivery delay.
• You are prepared to pin the version, test upgrade paths, and monitor fork maintenance and security posture.

Look elsewhere when:

• You are building a standard Laravel application outside the eZ Platform/Ibexa ecosystem; this package is not a general-purpose Laravel content browser.
• You are on a newer eZ/Ibexa version with an officially maintained Content Browser path.
• You require PHP 8.1+ support, formal long-term support, security SLAs, or vendor-backed maintenance.
• Your organization cannot tolerate a package rename, fork governance risk, or divergence from upstream.
• Your needs are simple enough for native admin selection or a small custom picker; a fork dependency may be disproportionate.

How to Pitch It (Stakeholders)

Executive summary: This release unblocks PHP 8.0 for Platform 2.5 deployments that rely on Netgen Content Browser by publishing the 1.4 line as se7enxweb/content-browser. It is a pragmatic sustainment move, not a strategic feature investment. It avoids a custom content-browser build for a constrained legacy platform, but it introduces fork and package-rename risk. Approve it only where Platform 2.5 + PHP 8.0 compatibility is a near-term need, and require a dependency owner, version pinning, and a plan to reassess against upstream or a supported platform path.

Engineering summary: Replace netgen/content-browser with se7enxweb/content-browser where appropriate, validate PHP 8.0 and Platform 2.5 behavior, test content selection/embedding workflows, and monitor upstream Netgen 1.4.x changes. Treat this as a maintenance dependency with constrained scope—not a standard package for the broader Laravel/PHP estate.