- What is ibecsystems/admin-kit-core and what does it do?
- It is a Composer-installed Laravel package that provides core utilities and abstractions for admin panels, including reusable building blocks for CRUD resources, forms, tables, filters, actions, and navigation. It is intended as the foundation for ibecsystems/admin-kit packages and custom back-office interfaces rather than a complete admin panel on its own. Treat it as a suite dependency, not a standalone product.
- How do I install ibecsystems/admin-kit-core in a Laravel app?
- Run composer require ibecsystems/admin-kit-core, confirm the service provider is auto-discovered, then publish the package config and migrations and run php artisan migrate. Mount the admin routes behind an auth guard as you would for any Laravel admin module. Because the README is thin, check the package composer.json and service provider for the exact publish tags and route registration details.
- Is admin-kit-core usable standalone or does it require other IBEC packages?
- The package describes itself as core utilities and abstractions forming the foundation for ibecsystems/admin-kit packages, so it is likely consumed by sibling modules and may be intentionally incomplete on its own. Test a standalone install first to see which features work without the companion packages. If key CRUD or navigation features depend on unpublished siblings, treat adoption as a suite decision rather than a single-package one.
- Which Laravel and PHP versions does admin-kit-core support?
- The package does not publish a clear compatibility matrix in the overview, so the authoritative source is the require and require-dev blocks in its composer.json. Resolve it against your exact Laravel and PHP versions in a throwaway project before committing to an upgrade path. Also check whether constraints are caret ranges or pinned versions, since a pinned constraint can block framework upgrades.
- What front-end stack does admin-kit-core ship with?
- The package ships publishable front-end assets, but the overview does not state whether its views are Blade, Livewire, or a JavaScript framework. That choice affects your asset pipeline, build step, and upgrade surface, so inspect the package resources and views directories before adopting. If it uses Livewire or Vue or React, confirm the matching dependencies and build tooling are compatible with your app.
- Does admin-kit-core assume a specific User model, auth guard, or roles and permissions backend?
- Admin kits are usually opinionated about authorization, and this package provides navigation and action abstractions that typically hook into a guard and a role or permission source. Verify what the service provider and config expect for the User model, guard, and any policy or permission integration. If your app uses a nonstandard auth setup, plan to override the relevant bindings rather than assume it will work out of the box.
- Where can I find documentation or a demo application for admin-kit-core?
- The repository overview and README excerpt are minimal, and no demo or reference application is mentioned, so documentation is likely limited to source code and config comments. Read the service provider, config file, and any publishable stubs to understand extension points before writing code. If docs are a hard requirement, ask the maintainer or budget time to reverse-engineer the package.
- How do I publish the config, migrations, and assets for admin-kit-core?
- Use the standard Laravel package workflow: php artisan vendor:publish with the package provider tag to publish config, migrations, and front-end assets, then run php artisan migrate. Confirm the exact tags by inspecting the service provider publishes array, since the package does not document them in the overview. Keep the published config in version control so environment-specific changes are reviewable.
- What are the maintenance and backward-compatibility risks of using admin-kit-core?
- The package is a single-maintainer, single-vendor project with few or no dependents, which means little ecosystem pressure to keep public APIs stable between releases. A recent release date suggests it is not abandoned, but a small surface can change in a patch release without wide notice. MIT licensing is the main mitigant because it lets you fork and pin the package if upstream changes become disruptive.
- How does admin-kit-core compare to Filament or Laravel Nova for admin panels?
- Filament and Nova are full admin panel products with large ecosystems, whereas admin-kit-core is a lower-level foundation intended to be composed into the IBEC suite or a custom back-office interface. It is a reasonable fit for a greenfield internal tool with no incumbent admin layer, but it rarely composes cleanly alongside an existing panel because admin kits are opinionated about routing, layout, and authorization. If you need batteries-included CRUD today, a mature panel is lower risk; choose admin-kit-core when you want reusable primitives and control over the stack.