Weave Code
Content Browser Sylius Laravel Package
netgen/content-browser-sylius
Netgen Content Browser integration for Sylius adds a unified content browsing and selection interface to the admin. Editors can search and pick items from configured content sources, with Sylius-specific setup and item type support.
Netgen Content Browser & Sylius integration
Frequently asked questions about Content Browser Sylius
- Does netgen/content-browser-sylius work with Laravel?
- No, not natively. It is a Symfony bundle that wires Sylius Doctrine repositories into Netgen Content Browser, with no Laravel service provider, Eloquent backend, or documented HTTP/JSON contract. A Laravel application could only use it by running Sylius as a separate Symfony service and exposing your own API, or by reusing the Source/Item/Backend pattern to build an equivalent picker. Price that integration work explicitly before adopting.
- How do I install netgen/content-browser-sylius in a Sylius application?
- Install it with Composer, enable the bundle in config/bundles.php, import the bundle routes under your admin firewall, and publish any required assets or translations. Then configure a Content Browser backend for each Sylius entity family you want to expose. There is no drop-in Sylius admin screen, so you must wire the picker into a form or Twig template yourself.
- What Sylius content can I browse and select with this package?
- The package registers Sylius resources such as products and taxonomies (taxons) as browsable Content Browser sources. Item mapping, labels, and previews are configurable, so you can adapt how each resource appears in the picker. The exact set depends on which backends you configure.
- Which Sylius, Symfony, and PHP versions does this bundle support?
- Support is defined by the Composer constraints on sylius/sylius, symfony/*, and netgen/content-browser, and the repository does not publish a broad supported-version matrix. You must prove the constraint set against your target Sylius and Symfony release, ideally with a spike and a CI job. Do not assume current Sylius majors are covered.
- Do I need Netgen Layouts, and can I embed the picker in a custom admin page?
- Netgen Layouts is not required; the package is a bridge to Netgen Content Browser, and Layouts is a separate consumer of that browsing layer. You can embed the picker in a custom Symfony admin controller or Twig template, though that involves manual frontend wiring. Under Layouts the friction is lowest.
- How do I register a custom Sylius entity as a Content Browser source?
- Implement or configure a Content Browser Source/Backend that reads from the relevant Sylius Doctrine repository, then register or tag it in the Symfony service container. Map the entity fields you need for item labels and previews through the package's item mapping configuration. Because there is no Laravel or Eloquent path, the backend must speak Doctrine.
- Does the Content Browser provide an HTTP or JSON API I can consume from Laravel?
- No documented headless HTTP or JSON contract is described; the integration is a Symfony bundle with routes, a config tree, and a JS/CSS picker UI. Anything a Laravel app consumes over HTTP would be an API you write yourself around the browsing endpoint. That is a meaningful scope expansion, not a package feature.
- How does netgen/content-browser-sylius handle large product catalogues and search performance?
- The evaluation notes flag this as unproven; you should verify whether the Sylius backends use server-side pagination, search, and filtering or fetch all records. Large catalogues will expose any fetch-all behaviour quickly in admin response times and memory use. Test with production-sized data before rollout.
- Is netgen/content-browser-sylius production-ready, secure, and actively maintained?
- Treat it as a reference implementation to pin or fork. Adoption signals are weak: low stars, few or no dependents, single-vendor origin, and no published supported-version matrix or strong CI signal. Secure the browsing endpoint behind the admin firewall and enforce Sylius resource-level authorization, or it becomes an information-disclosure path. Confirm maintenance cadence and bus factor with the maintainer.
- What are the alternatives to netgen/content-browser-sylius for a Laravel team?
- For a Laravel-only stack, the realistic alternatives are building a picker against your own Eloquent models, using a Laravel admin panel's built-in relationship selector, or running Sylius separately and integrating over an API. Reusing the Content Browser Source/Item/Backend pattern conceptually is reasonable, but the PHP package itself will not drop into Laravel. Evaluate the whole Netgen stack before committing.
Weaver
How can I help you explore Laravel packages today?