- What is open-dxp/admin-bundle used for?
- It provides the browser-based admin interface and UI layer for OpenDXP. Teams use it to manage content, assets, objects, users, and system configuration through backend screens and navigation. It is intended for administrative workflows, not for building a public-facing website frontend.
- Is open-dxp/admin-bundle compatible with Laravel?
- It is an OpenDXP admin bundle rather than a general-purpose Laravel admin package, so Laravel compatibility depends on how OpenDXP and the bundle's dependencies are wired into your application. Review composer.json requirements and the README before assuming it can be installed in a standard Laravel project. If you need a native Laravel admin panel, consider Laravel-specific options instead.
- How do I install open-dxp/admin-bundle with Composer?
- Run composer require open-dxp/admin-bundle in the OpenDXP application that should host the admin UI. Then follow the README for any required bundle registration, configuration, or asset build steps. Because the excerpt does not list exact setup commands, verify the package documentation rather than assuming a standard Laravel service provider flow.
- Which PHP and Laravel versions does open-dxp/admin-bundle support?
- The provided package overview does not list PHP or Laravel version constraints, so do not assume compatibility. Check the repository's composer.json, README, and Packagist release metadata for supported PHP, Laravel, and OpenDXP versions before adding it to an application.
- How does open-dxp/admin-bundle integrate with OpenDXP services?
- The bundle provides the admin UI layer and is described as integrating with OpenDXP services and extensions for daily admin workflows. Exact service wiring, extension points, and configuration are defined in the package README and OpenDXP documentation. Confirm required OpenDXP packages and service configuration before installation.
- Can I customize the navigation and management screens in open-dxp/admin-bundle?
- The bundle supplies the admin interface layer, including management screens and navigation, but the provided overview does not detail customization APIs. Check the README and OpenDXP extension documentation for supported overrides, templates, and extension points. Avoid editing vendor files directly; use documented extension mechanisms so updates remain safe.
- Do I need open-dxp/admin-bundle in production?
- Yes, if administrators use the browser-based backend in production, the admin UI layer must be available there. It is not the public-facing frontend, so restrict access to trusted admin users and follow OpenDXP security guidance. For local development, include it wherever you need to manage content, assets, users, or configuration.
- How should I test admin workflows after installing open-dxp/admin-bundle?
- Install it in a staging copy of your OpenDXP application and log in with a non-production admin account. Exercise the management screens for content, assets, objects, users, and system configuration, including permissions and navigation. Add smoke tests for critical admin routes and verify integrations with your installed OpenDXP services and extensions.
- What are alternatives to open-dxp/admin-bundle?
- If you are building a standalone Laravel admin panel, packages such as Laravel Nova, Filament, and Backpack provide Laravel-native administration tools. They are not drop-in replacements for OpenDXP's admin layer and will not manage OpenDXP content or services without custom integration. If you are operating OpenDXP, use this bundle or another documented OpenDXP admin solution.
- How actively is open-dxp/admin-bundle maintained?
- Maintenance activity is not described in the provided overview, so check the GitHub repository for recent commits, releases, and issue responses. Also review Packagist release history and compatibility notes against your OpenDXP version. Treat stale releases or unanswered security issues as adoption risks.