Download the PHP package awcodes/mason without Composer

Mason

A simple block based drag and drop page / document builder field for Filament.

Installation

You can install the package via composer:

In an effort to align with Filament's theming methodology you will need to use a custom theme to use this plugin.

[!IMPORTANT] If you have not set up a custom theme and are using a Panel follow the instructions in the Filament Docs first.

1. Import the plugin's stylesheet into your panel's custom theme css file. This will most likely be at resources/css/filament/admin/theme.css.

2. Add the plugin's views to your resources/css/filament/admin/tailwind.config.js file.

3. Rebuild your custom theme.

Configuration

You can publish the config file with:

This is the contents of the published config file:

Usage

[!IMPORTANT] Since Mason uses json to store its data in the database you will need to make sure your model's field is cast to 'array' or 'json'.

Form Field

In your Filament forms you should use the Mason component. The Mason component accepts a name prop which should be the name of the field in your model, and requires an array of actions that make up the 'bricks' available to the editor.

Infolist Entry

In your Filament infolist you should use the MasonEntry component. The Mason component accepts a name prop which should be the name of the field in your model.

To keep from having to repeat yourself when assigning bricks to the editor and the entry it would help to create sets of bricks that make sense for their use case. Then you can just use that in the bricks method.

Creating Bricks

Bricks are nothing more than Filament actions that have an associated view that is rendered in the editor with its data.

To help you get started there is a make:mason-brick command that will create a new brick for you with the necessary class and blade template in the paths specified in the config file.

This will create a new brick in the App\Mason namespace with the class Section and a blade template in the resources/views/mason directory. Bricks follow the same conventions as Filament actions. The important things to note are the fillForm method and the action method. These are how the action interacts with the editor. For bricks that do not have data you can remove the fillForm method and the form method from the brick and it will be inserted into the editor as is.

Rendering Content

You are free to render the content however you see fit. The data is stored in the database as json so you can use the data however you see fit. But the plugin offers a helper method for converting the data to html should you choose to use it.

Similar to the form field and entry components the helper needs to know what bricks are available. You can pass the bricks to the helper as the second argument. See, above about creating a collection of bricks. This will help keep your code DRY.

Testing

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Adam Weston
• All Contributors

License

The MIT License (MIT). Please see License File for more information.