PHPackages                             rwbuild/dashboard - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. rwbuild/dashboard

ActiveLibrary

rwbuild/dashboard
=================

A admin dashboard package

1.1.1(4y ago)064MITBlade

Since Feb 25Pushed 4y ago2 watchersCompare

[ Source](https://github.com/RWBuild/Dashboard_Package)[ Packagist](https://packagist.org/packages/rwbuild/dashboard)[ RSS](/packages/rwbuild-dashboard/feed)WikiDiscussions master Synced 1mo ago

READMEChangelog (3)Dependencies (1)Versions (5)Used By (0)

Dashboard Package
=================

[](#dashboard-package)

The Dashboard Pakcge is a plug-and-play laravel package that provides a quick and easy integration of a dashboard in your laravel project, with customizable assets built in for **Analytics**, **Users**, **Roles**, **Permissions** and **TOS** management.

Requirements
------------

[](#requirements)

Laravel [5.8](https://laravel.com/docs/5.8/)
Laratrust [5.2](https://laratrust.santigarcor.me/docs/5.2/)

Installation
------------

[](#installation)

Use the php dependency manager, [composer](https://getcomposer.org/), to install the package.

```
composer require rwbuild/dashboard

```

Setup
-----

[](#setup)

Once the installion is complete, run

```
php artisan dashboard:setup

```

This command will create a migration file in *database > migrations*. Before proceeding run the migrate command first.

```
php artisan migrate

```

Installation
------------

[](#installation-1)

### 01

[](#01)

Once the migrate command has run successfully, run the command below to get the dashboard installed in your application.

```
php artisan dashboard:install

```

then,

```
php artisan migrate

```

### 02

[](#02)

After successfully running this command, your folders structure should change and looks like:

Inside **app>Http>Controllers** , a **Dashboard** folder containing controller files will be created.

Inside **app>Http>View>Composers** will be generated view composer files that powers the blade views.

A Helper class will also be generated inside **app>Helpers** where you put your helper funtions for personal customizations.

Inside **resources>views** , a **dashboard** folder containing blade files will be created. These are customizable views that power the dashboard.

Inside **routes/web.php** and **api.php**, the files will be updated with the dashboard routes, and should look like this:

```
...
/*
|--------------------------------------------------------------------------
| Dashboard Routes
|--------------------------------------------------------------------------
*/
Route::group(['namespace' => 'Dashboard', 'prefix' => 'dashboard'], function () {
    ...
});
```

Inside the **public>css** folder, you should have the **dashboard.css** file, that contains all sylings of the dashboard.

Inside the **pubic>js** folder, you should have the **dashboard.js** and **dashboard\_analytics.js** fils.

### 03

[](#03)

Load the view composers class in **AppServiceProvider.php**

```
use App\Http\View\Composers\Dashboard\ {
    TosComposer,
    HomeComposer,
    UsersComposer,
    RolesComposer,
    ReportsComposer,
    PermissionsComposer
};
...
   public function boot()
    {
        View::composer('dashboard::assets.home', HomeComposer::class);
        View::composer('dashboard::assets.users', UsersComposer::class);
        View::composer('dashboard::assets.roles', RolesComposer::class);
        View::composer('dashboard::assets.permissions', PermissionsComposer::class);
        View::composer('dashboard::assets.tos', TosComposer::class);
        View::composer('dashboard::assets.reports', ReportsComposer::class);
    }
```

### 04

[](#04)

Add the helper file in composer.json

```
...
"files": [
    "app/Helpers/DashboardHelpers.php"
]
...

Then run composer dump-autoload
```

### 05

[](#05)

Go to **app>Http>Kernel.php** and add a midlleware to your *$routeMiddleware* array

```
...
'visit.log' => \Dashboard\Http\Middlewares\LogVisit::class
```

You should add this middleware to your web routes to get the users' on visits on your site logged.

Inside your main layout, or your entry file, include the **dashboard\_analytics.js** file,

```

```

- Features visits

    To get the analytics of **hits** or features your users visited, call the fuction **daFeatureVisit(featureName)** on your target event:

    eg.

    ```
        onclick="daFeatureVisit('apply')"
    ```

Configurations
--------------

[](#configurations)

To get the package working perfecly, check if the configurations are set properly. Inside the *config* folder, you should find the **dashboardmodels.php** that contains the configuration of your application models. This tell the package where to look for the models. Configure each key according to the namespace of the model its point to.

```
At this point, you should be able to navigate to /dashboard and get it working.
```

Deep dive
---------

[](#deep-dive)

### Accessing models inside the package's controllers

[](#accessing-models-inside-the-packages-controllers)

All action on models can be perfomed inside the dashboard controllers by:

#### Using the Model facade

[](#using-the-model-facade)

```
...
use Dashboard\Facades\Model;
...

public function index()
{
    return Model::user()::all();
}
...
```

#### Using the ModelsDefinition trait

[](#using-the-modelsdefinition-trait)

```
...
use ModelsDefinition;

public function show()
{
    return $this->user::findOrFail(1);
}
...
```

**Have fun** 😎

License
-------

[](#license)

[MIT](https://choosealicense.com/licenses/mit/)

###  Health Score

26

—

LowBetter than 43% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity8

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity56

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~84 days

Total

4

Last Release

1655d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/e3a6d635b2bda9623418d599663a429096fa7a8fb02fffaca60da4af5a8126f1?d=identicon)[CommonWorld](/maintainers/CommonWorld)

![](https://avatars.githubusercontent.com/u/45026772?v=4)[Elijah Bus](/maintainers/ElijahBus)[@ElijahBus](https://github.com/ElijahBus)

---

Top Contributors

[![ElijahBus](https://avatars.githubusercontent.com/u/45026772?v=4)](https://github.com/ElijahBus "ElijahBus (8 commits)")

### Embed Badge

![Health badge](/badges/rwbuild-dashboard/health.svg)

```
[![Health](https://phpackages.com/badges/rwbuild-dashboard/health.svg)](https://phpackages.com/packages/rwbuild-dashboard)
```

###  Alternatives

[ivanomatteo/laravel-device-tracking

a library that allow to track different devices used

28160.7k](/packages/ivanomatteo-laravel-device-tracking)[fresns/fresns

Cross-platform general-purpose multiple content forms social network service software.

4841.5k](/packages/fresns-fresns)[simplestats-io/laravel-client

Client for SimpleStats!

4515.5k](/packages/simplestats-io-laravel-client)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)