PHPackages                             will2therich/livewire-status-board - 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. [Utility & Helpers](/categories/utility)
4. /
5. will2therich/livewire-status-board

ActiveLibrary[Utility & Helpers](/categories/utility)

will2therich/livewire-status-board
==================================

Livewire component to show models/data according to its current status

081PHP

Since Sep 1Pushed 3y agoCompare

[ Source](https://github.com/will2therich/livewire-status-board)[ Packagist](https://packagist.org/packages/will2therich/livewire-status-board)[ RSS](/packages/will2therich-livewire-status-board/feed)WikiDiscussions master Synced yesterday

READMEChangelogDependenciesVersions (1)Used By (0)

Livewire Status Board
=====================

[](#livewire-status-board)

Livewire component to show records/data according to their current status

### Preview

[](#preview)

[![preview](https://github.com/asantibanez/livewire-status-board/raw/master/preview.gif)](https://github.com/asantibanez/livewire-status-board/raw/master/preview.gif)

### Installation

[](#installation)

You can install the package via composer:

```
composer require will2therich/livewire-status-board
```

### Requirements

[](#requirements)

This package uses `livewire/livewire` () under the hood.

It also uses TailwindCSS () for base styling.

Please make sure you include both of this dependencies before using this component.

### Usage

[](#usage)

In order to use this component, you must create a new Livewire component that extends from `LivewireStatusBoard`

You can use `make:livewire` to create a new component. For example.

```
php artisan make:livewire SalesOrdersStatusBoard
```

In the `SalesOrdersStatusBoard` class, instead of extending from the base Livewire `Component` class, extend from `LivewireStatusBoard`. Also, remove the `render` method. You'll have a class similar to this snippet.

```
class SalesOrdersStatusBoard extends LivewireStatusBoard
{
    //
}
```

In this class, you must override the following methods to display data

```
public function statuses() : Collection
{
    //
}

public function records() : Collection
{
    //
}
```

As you may have noticed, both methods return a collection. `statuses()` refers to all the different status values your data may have in different points of time. `records()` on the other hand, stand for the data you want to show that could be in any of those previously defined `statuses()` collection.

To show how these two methods work together, let's discuss an example of Sales Orders and their different status along the sales process: Registered, Awaiting Confirmation, Confirmed, Delivered. Each Sales Order might be in a different status at specific times. For this example, we might define the following collection for `statuses()`

```
public function statuses() : Collection
{
    return collect([
        [
            'id' => 'registered',
            'title' => 'Registered',
        ],
        [
            'id' => 'awaiting_confirmation',
            'title' => 'Awaiting Confirmation',
        ],
        [
            'id' => 'confirmed',
            'title' => 'Confirmed',
        ],
        [
            'id' => 'delivered',
            'title' => 'Delivered',
        ],
    ]);
}
```

For each `status` we define, we must return an array with at least 2 keys: `id` and `title`.

Now, for `records()` we may define a list of Sales Orders that come from an Eloquent model in our project

```
public function records() : Collection
{
    return SalesOrder::query()
        ->map(function (SalesOrder $salesOrder) {
            return [
                'id' => $salesOrder->id,
                'title' => $salesOrder->client,
                'status' => $salesOrder->status,
            ];
        });
}
```

As you might see in the above snippet, we must return a collection of array items where each item must have at least 3 keys: `id`, `title` and `status`. The last one is of most importance since it is going to be used to match to which `status` the `record` belongs to. For this matter, the component matches `status` and `records` with the following comparison

```
$status['id'] == $record['status'];
```

To render the component in a view, just use the Livewire tag or include syntax

```

```

Populate the Sales Order model and you should have something similar to the following screenshot

[![basic](https://github.com/asantibanez/livewire-status-board/raw/master/basic.jpg)](https://github.com/asantibanez/livewire-status-board/raw/master/basic.jpg)

You can render any render and statuses of your project using this approach 👍

### Sorting and Dragging

[](#sorting-and-dragging)

By default, sorting and dragging between statuses is disabled. To enable it, you must include the following props when using the view: `sortable` and `sortable-between-statuses`

```

```

`sortable` enables sorting withing each status and `sortable-between-statuses` allow drag and drop from one status to the other. Adding these two properties, allow you to have drag and drop in place.

You must also install the following JS dependencies in your project to enable sorting and dragging.

```
npm install sortablejs
```

Once installed, make them available globally in the window object. This can be done in the `bootstrap.js` file that ships with your Laravel app.

```
window.Sortable = require('sortablejs').default;
```

### Behavior and Interactions

[](#behavior-and-interactions)

When sorting and dragging is enabled, your component can be notified when any of these events occur. The callbacks triggered by these two events are `onStatusSorted` and `onStatusChanged`

On `onStatusSorted` you are notified about which `record` has changed position within it's `status`. You are also given a `$orderedIds` array which holds the ids of the `records` after being sorted. You must override the following method to get notified on this change.

```
public function onStatusSorted($recordId, $statusId, $orderedIds)
{
    //
}
```

On `onStatusChanged` gets triggered when a `record` is moved to another `status`. In this scenario, you get notified about the `record` that was changed, the new `status`, the ordered ids from the previous status and the ordered ids of the new status the record in entering. To be notified about this event, you must override the following method:

```
public function onStatusChanged($recordId, $statusId, $fromOrderedIds, $toOrderedIds)
{
    //
}
```

`onStatusSorted` and `onStatusChanged` are never triggered simultaneously. You'll get notified of one or the other when an interaction occurs.

You can also get notified when a record in the status board is clicked via the `onRecordClick` event

```
public function onRecordClick($recordId)
{
    //
}
```

To enable `onRecordClick` you must specify this behavior when rendering the component through the `record-click-enabled` parameter

```

```

### Styling

[](#styling)

To modify the look and feel of the component, you can override the `styles` method and modify the base styles returned by this method to the view. `styles()` returns a keyed array with Tailwind CSS classes used to render each one of the components. These base keys and styles are:

```
return [
    'wrapper' => 'w-full h-full flex space-x-4 overflow-x-auto', // component wrapper
    'statusWrapper' => 'h-full flex-1', // statuses wrapper
    'status' => 'bg-blue-200 rounded px-2 flex flex-col h-full', // status column wrapper
    'statusHeader' => 'p-2 text-sm text-gray-700', // status header
    'statusFooter' => '', // status footer
    'statusRecords' => 'space-y-2 p-2 flex-1 overflow-y-auto', // status records wrapper
    'record' => 'shadow bg-white p-2 rounded border', // record wrapper
    'recordContent' => '', // record content
];
```

An example of overriding the `styles()` method can be seen below

```
public function styles()
{
    $baseStyles = parent::styles();

    $baseStyles['wrapper'] = 'w-full flex space-x-4 overflow-x-auto bg-blue-500 px-4 py-8';

    $baseStyles['statusWrapper'] = 'flex-1';

    $baseStyles['status'] = 'bg-gray-200 rounded px-2 flex flex-col flex-1';

    $baseStyles['statusHeader'] = 'text-sm font-medium py-2 text-gray-700';

    $baseStyles['statusRecords'] = 'space-y-2 px-1 pt-2 pb-2';

    $baseStyles['record'] = 'shadow bg-white p-2 rounded border text-sm text-gray-800';

    return $baseStyles;
}
```

With these new styles, your component should look like the screenshot below

[![basic](https://github.com/asantibanez/livewire-status-board/raw/master/styles.jpg)](https://github.com/asantibanez/livewire-status-board/raw/master/styles.jpg)

Looks like Trello, right? 😅

### Advanced Styling and Behavior

[](#advanced-styling-and-behavior)

Base views of the component can be customized as needed by exporting them to your project. To do this, run the `php artisan vendor:publish` command and export the `livewire-status-board-views` tag. The command will publish the base views under `/resources/views/vendor/livewire-status-board`. You can modify these base components as needed keeping in mind to maintain the `data` attributes and `ids` along the way.

Another approach is copying the base view files into your own view files and pass them directly to your component

```

```

Note: Using this approach also let's you add extra behavior to your component like click events on header, footers, such as filters or any other actions

### Adding Extra Views

[](#adding-extra-views)

The component let's you add a view before and/or after the status board has been rendered. These two placeholders can be used to add extra functionality to your component like a search input or toolbar of actions. To use them, just pass along the views you want to use in the `before-status-board-view` and `after-status-board-view` props when displaying the component.

```

```

Note: These views are optional.

In the following example, a `before-status-board-view` has been specified to add a search text box and a button

[![extra-views](https://github.com/asantibanez/livewire-status-board/raw/master/extra-views.jpg)](https://github.com/asantibanez/livewire-status-board/raw/master/extra-views.jpg)

### Testing

[](#testing)

```
composer test
```

### Changelog

[](#changelog)

Please see [CHANGELOG](CHANGELOG.md) for more information what has changed recently.

Contributing
------------

[](#contributing)

Please see [CONTRIBUTING](CONTRIBUTING.md) for details.

### Security

[](#security)

If you discover any security related issues, please email  instead of using the issue tracker.

Credits
-------

[](#credits)

- [Andrés Santibáñez](https://github.com/asantibanez)
- [All Contributors](../../contributors)

License
-------

[](#license)

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.

###  Health Score

17

—

LowBetter than 6% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity9

Limited adoption so far

Community11

Small or concentrated contributor base

Maturity25

Early-stage or recently created project

 Bus Factor1

Top contributor holds 81.3% 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.

### Community

Maintainers

![](https://www.gravatar.com/avatar/10797b4583c2ea8930c9224c9262c21f26789005a197243eeaf58a56ad8c0424?d=identicon)[will2therich](/maintainers/will2therich)

---

Top Contributors

[![asantibanez](https://avatars.githubusercontent.com/u/5126648?v=4)](https://github.com/asantibanez "asantibanez (26 commits)")[![will2therich](https://avatars.githubusercontent.com/u/24435180?v=4)](https://github.com/will2therich "will2therich (3 commits)")[![aanorbel](https://avatars.githubusercontent.com/u/17911892?v=4)](https://github.com/aanorbel "aanorbel (1 commits)")[![messerli90](https://avatars.githubusercontent.com/u/3306651?v=4)](https://github.com/messerli90 "messerli90 (1 commits)")[![wilburpowery](https://avatars.githubusercontent.com/u/15817188?v=4)](https://github.com/wilburpowery "wilburpowery (1 commits)")

### Embed Badge

![Health badge](/badges/will2therich-livewire-status-board/health.svg)

```
[![Health](https://phpackages.com/badges/will2therich-livewire-status-board/health.svg)](https://phpackages.com/packages/will2therich-livewire-status-board)
```

PHPackages © 2026

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