Download the PHP package rawilk/filament-quill without Composer

filament-quill

filament-quill offers a Quill rich text editor integration for filament admin panels and forms.

Installation

You can install the package via composer:

You can publish the config file with:

You can view the default configuration here: https://github.com/rawilk/filament-quill/blob/main/config/filament-quill.php

If you need to, you can publish the views and translations with:

For more information on setup necessary to render editor content, see the Rendering Content section.

Usage

The editor has been set up to behave like and have a similar api to the rich text editor component provided by Filament. One major difference between Filament's editor and the package's editor is Filament is using Trix for the editor, while this package is using Quill.

Here's a quick example of how to use the editor in a filament form:

This will provide an editor that will look like this in your form:

Toolbar Buttons

You may set the toolbar buttons for the editor using the toolbarButtons() method. The options shown here are the defaults. Please consult the ToolbarButton enum for a full list of available toolbar buttons.

You may alternatively use the disableToolbarButtons() method to disable specific buttons:

To completely disable all toolbar buttons, pass an empty array to toolbarButtons([]), or use the disableAllToolbarButtons() method.

You can also enable specific toolbar buttons using the enableToolbarButtons() method:

Placeholders

A requirement I often have for rich text editors is the ability to provide a list of placeholder variables that an end-user can select and insert into the editor. My most common use case for this is for email templates. I've made it simple to do this in this package. All you need to do is provide an array of placeholders to the component.

As you can see, we take care of adding the toolbar button and registering a customized.

Note: Parsing and replacing your variables in your content is outside the scope of this form component. You will need to handle that part yourself.

Surrounding Characters

By default, we will surround a variable with [ and ] before it's inserted into the editor, so a the USER_NAME variable would become [USER_NAME] when we insert it.

To change these characters, you can use the surroundPlaceholdersWith() method:

Now when a variable is inserted, it will look like {{ USER_NAME }} instead.

Placeholder Button Label

To change the text on the placeholder button, you can either modify the filament-quill::quill.placeholders.label translation, or you can pass in a label via the placeholderButtonLabel() method.

Handlers

If you want to override a handler for an existing toolbar button, you can define your custom JavaScript handlers using the handlers() method. Here's an example of how to use your own handler for the bold toolbar button:

Note: Inside your callback functions, you will have access to the quill editor instance via this.quill as long as you don't use an arrow function.

Custom Toolbar Buttons

To add your own toolbar buttons, you can use the addToolbarButton() method. You will need to provide a name, a label, and a JavaScript handler for the button. If you need a dropdown instead, you will need to provide an array of options as well.

The last parameter, showSelectedOption only applies to dropdown buttons. When set to true, when a user clicks on an option, it will show the selected option's text as the dropdown label, just like the font family or font size toolbar buttons do.

Uploading Images

When the ToolbarButton::Image button is enabled, a user will be able to insert an image into the editor. Similar to filament's rich text editor, we will upload the image to the server and use that image's url on the server instead of storing it as a base64 encoded image in the content. You can customize how and where the images are stored on the server using these methods:

Note: We do not handle tracking and managing the uploaded images. For example, if an image is deleted from the content, we will not remove it from the server, so images have a high probability of becoming orphaned. We will dispatch a quill-image-uploaded alpine event when we upload an image, and a quill-images-deleted alpine event when our JavaScript detects an image has been removed from the content. Both of these events will receive the fully qualified urls of the relevant images, and the name of the field the event was dispatched from. You could listen for these events and track the absolute urls of the images:

You could alternatively provide a callback to the saveUploadedFileAttachmentsUsing() method on the editor to help you track the files, however that route may require more work on your end.

Note: You may want to delay deleting the images from the server when listening to the quill-images-deleted event until the user triggers a save, and/or you reset the history state of the editor.

Rendering Content

To match the formatting you will see in the editor, you should wrap your user-generated content inside a container with the quill-content prose max-w-none classes on it. You will also need to make sure you have the styles for the content area from this package loaded as well. We've extracted those styles into a separate stylesheet, called content.css. Depending on how you're rendering the content, you may find it easier to bundle the content.css styles in with your theme's stylesheet. If you haven't set up a custom theme and are using a panel, you should follow the Filament docs first on how to do that.

The following will apply in both a panel and standalone as well.

1. In your stylesheet, import the content styles:

2. Add the package's views to your tailwind.config.js file.

3. Add the tawilwindcss/nesting plugin to your postcss.config.js file.

4. Rebuild your custom theme.

5. Render the content

You can also add dark:prose-invert to your container if you're supporting dark mode for the content rendering.

It's also generally a good idea to run your content through a html purifier, however that is outside the scope of these docs.

Custom Fonts

If you have the ToolbarButton::Font button enabled, we will render a dropdown allowing the user to format their content with Sans Serif, Serif, or Monospaced font families. You will need to pull in and register those font families manually, however. In a panel, you could take advantage of the panels::head.start Render Hook to accomplish this.

In the code below, we're going to pull in Fira Code and PT Serif monospace and serif fonts to use, however the process is similar to custom fonts as well.

Registering the font families

In the package's stylesheet, we configure monospace and serif font families to look for the --font-serif-family and --font-mono-family css variables in the editor area, however when rendering your own content independently, you'll need to configure your fonts in your theme's tailwind.config.js file.

Using custom font families

If you want to use custom font families, like "Times New Roman", or something like that, you can use the useFonts() method on the component:

Be sure to follow the Rendering Content section first to make sure you have everything setup for this.

Based on the registering the font families section, you will need to register the font in your tailwind config. We will map each font family value to a slug, so the "Times New Roman" font above will be mapped to "times-new-roman".

In a custom stylesheet, you will need to target the areas of the content that are formatted with this font:

Be sure to replace .ql-times-new-roman and font-times with your actual font names.

Custom font sizes

When the ToolbarButton::Size button is enabled, we will show a dropdown of font sizes the user can use to format their content with. Like with the font families, you are free to define your own sizes. You can pass an array of font sizes to the fontSizes method:

When you provide actual CSS size units, Quill will inline the text size right on the content, so no additional styling will be required. However, if you provide non-standard sizes, like "Small" or "Large", you will need to target those selectors in your css. The selectors follow a scheme of: ql-size-{size}.

Custom colors

When you have the ToolbarButton::TextColor and ToolbarButton::BackgroundColor buttons enabled, you are free to specify your own color pallet using css hex color codes.

History

By default, the editor includes toolbar buttons for undo/redo history actions. When dealing with Images or some other use-cases, you may want to reset the history state of the editor so the user can't "undo" a change back to a broken image if you removed it from the server. This can easily be accomplished by calling the clearHistory method on the component from an action, for example.

Here's an example of resetting the history state on an edit resource page form using the afterSave hook:

Behind the scenes, the editor component will dispatch the quill-history-clear browser event, which our javascript will be listening for. If you aren't able to get a component instance, you can manually dispatch the event yourself. You will just need to know the state path for the component (typically data.your_field_name).

Other Callbacks

onInit

Using the onInit callback, you are able to register additional handlers or callbacks on the quill editor instance, and more. This can be a great place to register your own Event handlers on the editor instance. All you need to do is provide a JavaScript callback to the onInit() method:

Our JavaScript will pass your callback an instance of the quill editor, as well as the alpine component instance.

Text Changed

If you just want to hook into the text-changed event that is dispatched from quill, you can use the onTextChange method:

Note that we're using a regular function here, and not an arrow function. This is so you can use this.quill for the editor instance.

In addition to the normal arguments that Quill provides, we also provide your callback an instance of the alpine component if you need it. You can prevent any processing of this event by our JavaScript if you return false from your callback.

Scripts

Setup

For convenience, you can run the setup bin script for easy installation for local development.

Formatting

Although formatting is done automatically via workflow, you can format php code locally before committing with a composer script:

Testing

Changelog

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

Contributing

Please see CONTRIBUTING for details.

Security

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

Credits

• Randall Wilk
• All Contributors

Alternatives

• Filament's Rich Editor
• Filament Tiptap Editor
• Filament Forms TinyEditor

License

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