Download the PHP package awcodes/filament-tiptap-editor without Composer

Filament Tiptap Editor

A Tiptap integration for Filament Admin/Forms.

Installation

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.

Note If you have not set up a custom theme and are using a Panel follow the instructions in the Filament Docs first. The following applies to both the Panels Package and the standalone Forms package.

1. Import the plugin's stylesheet and tippy.js stylesheet (if not already included) into your theme's css file.

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

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

4. Rebuild your custom theme.

Upgrading from 2.x to 3.x

1. Output is now set with an Enum, please update your files to use TiptapOutput in all place where you are setting the output, including the config file.
2. barebone profile setting was renamed to minimal

Usage

The editor extends the default Field class so most other methods available on that class can be used when adding it to a form.

Rendering content in Blade files

If you are storing your content as JSON then you will likely need to parse the data to HTML for output in Blade files. To help with this there is a helper function tiptap_converter that will convert the data to one of the three supported Tiptap formats.

Styling the output is entirely up to you.

Table of Contents

If you are using the heading tool in your editor you can also generate a table of contents from the headings in the content. This is done by passing the content to the asHTML() method and setting the toc option to true. You can also pass a maxDepth option to limit the depth of headings to include in the table of contents.

Alternatively, you can use & extend the table-of-contents blade component to generate the table of contents.

Config

The plugin will work without publishing the config, but should you need to change any of the default settings you can publish the config file with the following Artisan command:

Profiles / Tools

The package comes with 3 profiles (or toolbars) out of the box. You can also use a pipe | to separate tools into groups. The default profile is the full set of tools.

See filament-tiptap-editor.php config file for modifying profiles to add / remove buttons from the editor or to add your own.

Tools can also be added on a per-instance basis by using the ->tools() modifier to overwrite the profile set for the instance. A full list of tools can be found in the filament-tiptap-editor.php config file under the default profile setting.

Media / Images

Output format

Tiptap has 3 different output formats. See: https://tiptap.dev/guide/output

If you want to change the output format that is stored in the database you can change the default config or specify it in each instance.

Note If you want to store the editor content as array / json you have to set the database column as longText or json type. And cast it appropriately in your model class.

RTL Support

In order for things like text align to work properly with RTL languages you can switch the direction key in the config to 'rtl'.

Max Content Width

To adjust the max content width of the editor globally set max_content_width key in the config to one of the tailwind max width sizes or full for full width. This could also be set on a per-instance basis with the ->maxContentWidth() method.

Overrides

The Link, Media and Grid Builder modals are built using Filament Form Component Actions. This means it is easy enough to swap them out with your own implementations.

Link Modal

You may override the default Link modal with your own Action and assign to the link_action key in the config file. Make sure the default name for your action is filament_tiptap_link.

See vendor/awcodes/filament-tiptap-editor/src/Actions/LinkAction.php for implementation.

Media Modal

You may override the default Media modal with your own Action and assign to the media_action key in the config file. Make sure the default name for your action is filament_tiptap_media.

See vendor/awcodes/filament-tiptap-editor/src/Actions/MediaAction.php for implementation.

Grid Builder Modal

You may override the default Grid Builder modal with your own Action and assign to the grid_builder_action key in the config file. Make sure the default name for your action is filament_tiptap_grid.

See vendor/awcodes/filament-tiptap-editor/src/Actions/GridBuilderAction.php for implementation.

OEmbed Modal

You may override the default OEmbed modal with your own Action and assign to the oembed_action key in the config file. Make sure the default name for your action is filament_tiptap_grid.

See vendor/awcodes/filament-tiptap-editor/src/Actions/OEmbedAction.php for implementation.

Initial height of editor field

You can add extra input attributes to the field with the extraInputAttributes() method. This allows you to do things like set the initial height of the editor.

Bubble and Floating Menus

By default, the editor uses Bubble and Floating menus to help with creating content inline, so you don't have to use the toolbar. If you'd prefer to not use the menus you can disable them on a per-instance basis or globally in the config file.

You can also provide you own tools to for the floating menu, should you choose. Defaults can be overwritten via the config file.

Grid layouts

When using the grid tool, you can customize the available layouts in the dropdown by passing them to the gridLayouts() method:

Custom Blocks

Note To use custom blocks you must store your content as JSON.

There are 3 components you need to create a custom block for Tiptap Editor.

• A block class that extends TiptapBlock and defines the settings for the block.
• A 'preview' blade file
• A 'rendered' blade file

Creating a custom block

Block class

Static blocks

If you simply need a placeholder to output a block that doesn't have settings you can simply not provide a getFormSchema method and no modal will be shown and blocks will be directly inserted into the editor.

Modal width, slide overs and icons

Note: Currently, icons will only be show on the drag and drop block panel

Preview view

Preview views are just standard blade views. Unfortunately, you cannot use Livewire components in a block preview as they will not work correctly due to the editor having to be wire:ignore.

resources/views/blocks/previews/batman.blade.php

Rendered view

Rendered views are normal blade files and can also be used to output livewire components with your block data.

resources/views/blocks/rendered/batman.blade.php

Registering your blocks with the editor

In the register method of a service provider you can add your blocks to the editor via configureUsing.

Note You will also need to add the 'blocks' key where appropriate in your profiles in the tiptap config.

By default, the drag and drop blocks panel will be open in the editor. If you want to change this you can use the collapseBlocksPanel modifier on the Editor instance or globally with configureUsing.

Merge tags

Merge tags can be used with JSON-based editor content to replace placeholders with dynamic content. Merge tags are defined in the mergeTags() method of the editor instance:

To insert a merge tag, the user can either type {{ to open an autocomplete menu, or drag a merge tag into the editor from the "blocks panel". You can remove the tags from the blocks panel using showMergeTagsInBlocksPanel(false):

Rendering merge tags

While you have full control over how the content of the merge tags are replaced, you can use the mergeTagsMap() method on the tiptap_converter helper to replace the tags with the provided data:

Usage in Standalone Forms Package

If you are using any of the tools that require a modal (e.g. Insert media, Insert video, etc.), make sure to add {{ $this->modal }} to your view after the custom form:

Custom Extensions

You can add your own extensions to the editor by creating the necessary files and adding them to the config file extensions array.

This only support CSS and JS with Vite.

You can read more about custom extensions at https://tiptap.dev/guide/custom-extensions.

JS

First, create a directory for you custom extensions at resources/js/tiptap and add your extension files.

Next, create at a file at resources/js/tiptap/extensions.js and add the following code.

Note that when adding your extension to the array you must register them a key:array set.

CSS

Create a css file for your custom extensions at resources/css/tiptap/extensions.css. All styles should be scoped to the parent class of .tiptap-content.

Vite Config

Now you need to add these to your vite.config.js file and run a build to generate the files.

PHP Parser

You will also need to create a PHP version of your extension in order for the content to be read from the database and rendered in the editor or to your front end display. You are free to create this anywhere in your app, a good place is something like app/TiptapExtensions/YourExtenion.php.

You can read more about the php parsers at https://github.com/ueberdosis/tiptap-php

Toolbar Button

You will also need to crate a dedicated view for you toolbar button. This should be placed somewhere in your app's resources/views/components directory. You are free to code the buttons as you see fit, but it is recommended to use the plugin's view components for uniformity.

Registering the Extensions

Finally, you need to register your extensions in the config file and add the new extension to the appropriate profile.

Versioning

This project follow the Semantic Versioning guidelines.

License

Copyright (c) 2022 Adam Weston and contributors

Licensed under the MIT license, see LICENSE.md for details.