https://github.com/akhilh2o/neodash
Neodash is a admin panel package made for laravel on top of Laravel Breeze. It is a very simple setup for a quick start, with a separate admin panel having user, roles & permissions, posts, pages, faqs and testimonials management.
https://github.com/akhilh2o/neodash
admin admin-dashboard admin-panel admin-ui administration adminlte bootstrap laravel laravel-admin laravel-admin-panel laravel-boilerplate laravel-breeze laravel-package panel
Last synced: 2 months ago
JSON representation
Neodash is a admin panel package made for laravel on top of Laravel Breeze. It is a very simple setup for a quick start, with a separate admin panel having user, roles & permissions, posts, pages, faqs and testimonials management.
- Host: GitHub
- URL: https://github.com/akhilh2o/neodash
- Owner: akhilh2o
- Created: 2023-07-22T05:23:51.000Z (almost 3 years ago)
- Default Branch: master
- Last Pushed: 2023-07-28T10:06:43.000Z (almost 3 years ago)
- Last Synced: 2025-05-25T05:53:58.411Z (about 1 year ago)
- Topics: admin, admin-dashboard, admin-panel, admin-ui, administration, adminlte, bootstrap, laravel, laravel-admin, laravel-admin-panel, laravel-boilerplate, laravel-breeze, laravel-package, panel
- Language: Blade
- Homepage: https://packagist.org/packages/akhilesh/neodash
- Size: 5.06 MB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Introduction to Neodash
**Neodash** is a admin panel package made for laravel on top of *Laravel Breeze*. It is a very simple setup for a quick start, with a separate admin panel having user, roles & permissions, posts, pages, faqs and testimonials management. This package uses Bootstrap 4.x.
## Installation
Update your *.env* file, provide database name, user and password. Execute command given below to install **neodash admin panel**
composer require akhilesh/neodash
Run following command to quick installation
php artisan neodash:install fresh
By default default scaffold will be generated with default options, instead you can change your setting in configuration file `site.php` and run `php artisan neodash:install` once again. This will ask some questions like, if you want to migrate the fresh table or not, or you want to seed the tables or not.
After installation you will get routes in admin.php file in routes folder, models and controller with their related trait and views. To override the properties / functionalities, define your own respective function in controller. This package comes with a route middleware `GatesMiddleware::class`, admin routes will be wrapped within this middleware.
### Configurations
Add `ASSET_URL` to *.env* file, which will point to pubic directory.
public/assets: In this folder you will get all the static images, css, js and other files.
A `storage()` helper will be provided to get the url of publically stored images. If you want to change this url, you can set a property in *.env* file `STORAGE_URL`.
You can disable *install command* from *config/site.php* by setting *command* key to false. This will protect you by running the command file accidentally and replacing your existing files.
### Other packages being used
**`Alertt:`** Alertt package has been integrated for any operation alert message, for any customization in this, please refer to [takshak/alertt](https://github.com/takshaktiwari/alertt).
**`Imager:`** Takshak/Imager is integrated to generate seeds and resize and modify images at the time of upload images in different sections in the panel. This is also user to get default placeholder images and user avatars. For more information about this package, please refer to [takshak/imager](https://github.com/takshaktiwari/imager)
This package comes with some default users, roles, and permission, which are inserted using seeders. There seeders for all the modules. You will get a default admin user with email: *neodash@gmail.com* and password: *password*
- - -
## Extra functionalities
- **ReferrerMiddleware middleware:** This middleware can be used to redirect from specific route to some other route. Both routes (form, to) should be passed in the route, eg.
route(
'some.route',
[
'refer' => [
// specify the route from where the application will be redirected
'refer_from' => route('redirect.source'),
// specify the destination route where to be redirected back
'refer_to' => route('redirect.destination'),
// optional (checking the request method along with 'refer_from')
'method' => 'GET'
]
]
);
**For Example:**
route('some.route', [
'refer' => [
'refer_from' => route('redirect.source'),
'refer_to' => route('redirect.destination'),
'method' => 'GET'
]
]);
- - -
## Queries Management
You can directly submit query forms from frontend to admin panel by posting forms on `route('queries.store')`. It will be stored on the database and an email will also be send to the mail defined in env file `MAIL_PRIMARY`.
Possible input names are given below. All inputs are optional can will be defined in form if required:
- `name`: (string) You can store user's name.
- `email`: (string) You can store user's email.
- `mobile`: (string) Store user's mobile / phone.
- `subject`: (string) Subject of form or mail.
- `title`: (string) Can be used for title of the form.
- `content`: (text) Store message of content of form.
- `others`: (array) Other keys can also be specified via `name="others[input_name]"`.
- `files`: (array) You can put files specified via `name="files[resume]"`. Url of the file will be saved to database and included in mail.
- `redirect`: (string) Will be input type hidden and hold the url on which it will be redirected after submission.