Easy AdminLTE integration with Laravel
Installs: 2 483 376
Stars: 3 537
Forks: 1 013
- php: >=7.2.5
- almasaeed2010/adminlte: 3.2.*
- laravel/framework: >=7.0
- orchestra/testbench: >=4.0
- phpunit/phpunit: >=9.1
- scrutinizer/ocular: ^1.9
This package is auto-updated.
Last update: 2023-05-22 14:27:10 UTC
This package provides an easy way to quickly set up AdminLTE v3 with Laravel (7 or higher). It has no others requirements and dependencies besides Laravel, so you can start building your admin panel immediately. The package provides a blade template that you can extend and an advanced menu configuration system. Also, and optionally, the package offers a set of AdminLTE styled authentication views that you can use in replacement of the ones that are provided by the legacy laravel/ui authentication scaffolding.
If you want to use an older Laravel or AdminLTE version, review the following package releases:
- Releases 1.x: These releases supports Laravel 5 and include AdminLTE v2
- Releases 2.x: These releases supports Laravel 6 and include AdminLTE v2
- Releases 3.x (<=3.8.6): These releases supports Laravel 6 and include AdminLTE v3
All documentation is available on the Wiki Pages, we encourage you to read it. If you are new start with the Installation Guide. To update the package consult the Updating Guide.
The current package requirements are:
- Laravel >= 7.x
- PHP >= 7.2.5
Issues, Questions and Pull Requests
You can report issues or ask questions in the issues section. Please, start your issue with
[BUG] and your question with
[QUESTION] in the subject.
You may also use the issues to propose changes for the Wiki Pages, in that case use
[WIKI] at the beginning of the subject.
If you have a question, it is recommended to make a search over the closed issues first.
To submit a Pull Request, fork this repository and create a new branch to commit your new changes there. Finally, open a Pull Request from your new branch. Refer to the contribution guidelines for detailed instructions. When submitting a Pull Request take the next notes into consideration:
- Verify that the Pull Request doesn't introduce a high downgrade on the code quality.
- If the Pull Request adds a new feature, consider adding a proposal of the documentation for the Wiki.
- Keep the package focused, don't add special support to other packages or to solve very particular situations. These changes will make the package harder to maintain.