Weave Code
Content Browser Ui Laravel Package
netgen/content-browser-ui
A reusable front-end for Netgen Content Browser that gives PHP applications a configurable content-browsing and selection interface. Browse, search, and pick content items through a clean UI designed to plug into existing Netgen Content Browser backends. Ideal for admin tools and content pickers.
Netgen Content Browser user interface
Frequently asked questions about Content Browser Ui
- Is netgen/content-browser-ui a Laravel package?
- No. It is the front-end presentation layer for Netgen Content Browser, which is native to the Netgen Layouts, Ibexa, and eZ Platform Symfony ecosystem. The package does not ship a Laravel service provider, Blade views, Eloquent integration, or a published asset pipeline for non-Symfony hosts. Treat it as a satellite UI rather than a direct Laravel dependency.
- How do I install netgen/content-browser-ui in a Laravel application?
- A Composer install alone will not produce a working browser in Laravel. The UI expects the netgen/content-browser core to be installed and configured with at least one content source, those sources to resolve through eZ or Ibexa APIs, and the host to serve expected routes and assets. The realistic options are running an isolated Symfony or Ibexa service behind an iframe or proxy, or extracting the front-end bundle and implementing the backend contract in Laravel.
- Does netgen/content-browser-ui work without netgen/content-browser?
- No. The UI depends on the core package's routes, view models, and asset pipeline, and it needs at least one configured content source before browsing or selection works. Without the core installed and configured, assets may load but the browse and select behavior will not function. Install and configure netgen/content-browser first.
- Which Laravel versions does netgen/content-browser-ui support?
- The package does not declare Laravel version support because it targets the Symfony, Twig, and Ibexa or eZ stack. Laravel version compatibility is therefore not a meaningful support matrix for this package. Check its composer.json for PHP and core version constraints, and expect tight coupling to specific netgen/content-browser versions.
- Can I use netgen/content-browser-ui with Blade instead of Twig?
- Not directly. The package ships Twig templates and or a JavaScript bundle that expects the Symfony rendering environment and the core package's view models. Using it from Blade would require either mounting the compiled UI as a JavaScript island in a Blade view or reimplementing the rendering contract in Laravel. Confirm whether the UI bundle has a clean adapter seam before planning either path.
- Does netgen/content-browser-ui provide a headless or JSON API I can consume from Laravel?
- That is not confirmed by the package overview and is the single most important unknown for Laravel adoption. If a documented headless or JSON mode exists with a clean adapter seam, Laravel could consume it over HTTP or mount the UI as a JavaScript island. If the UI is coupled to internal Symfony view models, reimplementing the backend in Laravel becomes materially more expensive. Resolve this by inspecting package.json, src entry points, and any example folder.
- What are the alternatives to netgen/content-browser-ui for a Laravel content picker?
- For a conventional Laravel application, native admin tooling, Livewire or Inertia components, or a maintained Laravel content-picker package are lower-risk options. A simple Eloquent-backed content tree can also cover many admin browse and select workflows. If you specifically need Netgen or Ibexa content, run the Content Browser as a separate service and embed it rather than forcing the Symfony UI into Laravel.
- Is netgen/content-browser-ui actively maintained and production-ready?
- Adoption signals are weak for broad production use outside its native ecosystem: 14 stars, zero dependents, a composite score of 0.1, and single-vendor maintenance by Netgen. The MIT license removes legal risk but not engineering risk. Check whether there has been a release in the last 12 months and who the committers are before committing to it.
- What is the biggest technical risk and how should I test a Laravel integration?
- The dominant risk is that the package silently does not apply to a Laravel application at all, and version coupling to netgen/content-browser means a minor core bump can break the UI with missing assets or blank views. Run a one-day spike to determine whether the package contains Twig templates, a compiled JavaScript bundle, or both, and whether a documented adapter seam exists. Pin versions, test in an isolated Symfony or Ibexa service, and verify browse, search, and select behavior before estimating further work.
- What frontend dependencies and peer requirements does netgen/content-browser-ui have?
- The overview confirms prebuilt front-end assets, reusable UI components, and consistent styling, but it does not specify peer dependencies such as React, a bundler, or a build tool. Inspect package.json and src entry points to identify the actual frontend contract. Check that contract against your existing frontend stack before adoption, because a collision would add significant integration cost.
Weaver
How can I help you explore Laravel packages today?