- What is dedermus/open-admin-core used for?
- Dedermus OpenAdmin Core is a Laravel package that provides the foundation layer for back-office admin panels. It ships shared UI components, CRUD scaffolding, and extension hooks so your custom admin modules stay consistent and reusable. It is a base you build on rather than a finished, ready-made panel.
- How do I install dedermus/open-admin-core with Composer?
- Install it with Composer using composer require dedermus/open-admin-core. After that, follow the installation steps in the GitHub README for service provider registration, asset or config publishing, and any migration steps, since those specifics depend on the current release. Commit the updated composer.json and lock file so the setup is reproducible across environments.
- Which Laravel versions does OpenAdmin Core support?
- The package description here does not state a Laravel version range, so check the require section of its composer.json or the README before installing. Running composer require on a scratch branch is the fastest way to confirm your Laravel and PHP versions satisfy the constraints. If you maintain an older framework release, verify compatibility explicitly instead of assuming it.
- What does CRUD scaffolding in OpenAdmin Core actually give me?
- CRUD scaffolding gives you a consistent base for create, read, update, and delete screens instead of hand-writing the same listing, form, and validation wiring for every resource. Because the scaffolding comes from the core, generated modules follow the same structure and conventions. You then customize each module on that base rather than starting from zero.
- Can I add my own custom admin modules to an OpenAdmin Core panel?
- Yes, extending the admin with your own modules is the intended use of the package. The core supplies the shared components and extension hooks, and your modules plug into them so they behave consistently with the rest of the panel. Keeping module-specific logic in your own namespace or package makes core upgrades much easier.
- What are extension hooks in OpenAdmin Core?
- Extension hooks are the points where the core lets your code hook into shared admin behaviour, such as extending the standard CRUD and UI flows. They exist so you can customize the panel without editing vendor files or forking the package. Review the hooks documented in the repository before building your own workarounds.
- Does OpenAdmin Core include UI components, or do I build the front end myself?
- The package provides shared UI components for admin screens, which is one of its stated purposes. How those views are structured and how far you can override styling is covered in the repository docs and in the assets the package publishes. Expect to customize views and add your own branding rather than getting a finished theme.
- Is OpenAdmin Core a complete admin panel like Filament or Nova?
- OpenAdmin Core is described as an admin foundation, not a turnkey panel, so you build your screens, navigation, and domain modules on top of it. That makes its scope narrower than full admin builders such as Filament, Nova, or Backpack, which ship more features out of the box. Pick the core when you want a lightweight, controllable base with your own conventions.
- How do I test admin modules built on OpenAdmin Core?
- Test modules the way you test the rest of a Laravel app: feature tests that hit your admin routes and assert responses, plus unit tests for any business logic you add. Because the core handles shared CRUD wiring, cover authorization and validation on the generated endpoints in particular. If the package ships its own test helpers, the README will mention them.
- Is OpenAdmin Core production-ready and actively maintained?
- Before relying on it for a real back office, check the repository's commit history, tagged releases, and open issues to judge maintenance activity. Pin a specific version in composer.json and review the changelog before upgrading, since core changes can affect every admin module you have built. Treat it as you would any focused, small-maintainer dependency and plan for that risk.