This Package adds a Livewire component to your application, which will create an Editor.js instance for you.
Out of the box it already supports image uploads using Livewire and the Image plugin of Editor.js.
Packaged version of Editor.js: 2.26.5
This package requires you to have the following tools installed:
Please refer to the linked guides on how to install these.
You can install the package via composer:
composer require maxeckel/livewire-editorjsAfter composer downloaded the package, you will need to publish it's config & assets:
php artisan vendor:publish --tag=livewire-editorjs:configFor the assets you have two options:
- Already, for production, compiled assets including the above mentioned plugins:
php artisan vendor:publish --tag=livewire-editorjs:assets:compiled --forceThis will copy the compiled assets into public/vendor/livewire-editorjs.
- Publish the raw assets to include them in your own build chain:
php artisan vendor:publish --tag=livewire-editorjs:assets:rawThis will copy the raw assets into resources/js/vendor/livewire-editorjs.
Now you have to include these assets into your own build chain.
This method will be needed, if you want to further customize the editor, e.g. adding more plugins or
configure the installed ones in a different way.
For this to work, you will need to install all the plugins you want to use yourself!
This also includes the ones already configured!
The last step is to include the scripts within your views. You can do this how ever you prefer. If you have chosen option 1. you can include the scripts with a little blade directive:
@livewireEditorjsScripts
Advice
If you opted for option 1. of publishing the assets, you should make sure, that after a composer update
the assets are published again to avoid them being outdated. In order to do so update your composer.json script
configuration:
{
"scripts": {
"post-autoload-dump": [
"Illuminate\\Foundation\\ComposerScripts::postAutoloadDump",
"@php artisan package:discover --ansi",
"@php artisan vendor:publish --tag=livewire-editorjs:assets:compiled --force"
]
}
}If you opted for option 2. I wouldn't suggest to automatically republish the raw assets, as this would overwrite any changes you made. Please check the changelog after you updated this package.
@livewire('editorjs', [
'editorId' => "myEditor",
'value' => $value,
'uploadDisk' => 'public',
'downloadDisk' => 'public',
'class' => '...',
'style' => '...',
'readOnly' => true,
'placeholder' => 'Lorem ipsum dolor sit amet'
])<livewire:editorjs
editor-id="myEditor"
:value="$value"
upload-disk="public"
download-disk="public"
class="..."
style="..."
:read-only="true"
placeholder="Lorem ipsum dolor sit amet"
/>The editorId parameter is used to generate a unique events from the Livewire component,
in order for you to be able to listen for events of specific editors (in case more than 1 is used on the same page)
Important!
Don't use the passed id anywhere else as id attribute on an HTML element, as the editorId is internally used
as id on the wrapper div in which Editor.js gets initialized!
If you use the id somewhere else, the instance will break!
The value parameter sets the inital data for the editor instance.
This would be your stored JSON data of Editor.js
The uploadDisk parameter defines the disk, to which uploaded images should be stored.
This parameter is optional. The default disk to store images in is defined within the packages config file:
config/livewire-editorjs.php => default_upload_img_disk
Default: public
The downloadDisk parameter defines the disk, to which downloaded images should be stored.
Images will be downloaded from the internet when a user pasts an image URL into the Editor (see Editor.js image plugin)
This parameter is optional. The default disk to store images in is defined within the packages config file:
config/livewire-editorjs.php => default_download_img_disk
Default: `public
As the name suggests you can pass in CSS classes as you would with any other component.
For styling the Editor/Blocks, please refer to the documentation of Editor.js
Default: ""
As the name suggest you can pass in inline styles as you would with any other component.
Default: ""
You can pass this parameter with an value of "true" to set the editor into read only mode. This might be useful, if you want to display articles the same way, as they have been created.
Default: false
Using the placeholder property, you can pass a placeholder to the Editor.js instance, which will
be displayed in an empty editor.
Default: '' (set through the corresponding config option default_placeholder)
The Editor is configured to save changes to the server using its built in onChange callback.
In this callback the editor will sync its state with Livewire.
When this happens, Livewire will emitUp a save event:
editorjs-save:editorId
The editorId is substituted, with the editorId parameter you passed to the component.
With this, you can listen for the event within your Livewire Page/Component you use the editor in,
in order to save changes to your models.
protected $listeners = ['editorjs-save:editorId' => 'saveEditorState'];
public function saveEditorState($editorJsonData)
{
$this->model->data = $editorJsonData;
}In order to change the config, you'll first need to publish it:
php artisan vendor:publish --provider="Maxeckel\LivewireEditorjs\LivewireEditorjsServiceProvider" --tag="livewire-editorjs:config"
or
php artisan vendor:publish and select livewire-editorjs:config by entering its number.
<?php
return [
'enabled_component_registration' => true,
'component_name' => 'editorjs',
// Sets the default placeholder to use when a new and empty Editor.js instance is created.
'default_placeholder' => '',
/*
* Available options:
*
* VERBOSE Show all messages (default)
* INFO Show info and debug messages
* WARN Show only warn messages
* ERROR Show only error messages
*
* Taken from the offical docs of Editor.js:
* https://editorjs.io/configuration#log-level
*/
'editorjs_log_level' => 'ERROR',
// Defines on which disk images, uploaded through the editor, should be stored.
'default_img_upload_disk' => 'public',
// Defines on which disk images, downloaded by pasting an image url into the editor, should be stored.
'default_img_download_disk' => 'public',
];This option defines, whether the ServiceProvider should register the default livewire component while booting.
Set this to false when you want to disable the internal component and use your own using the make:editorjs command.
This option defines, under which name the internal component should be registered.
By default this is set to editorjs, making the component accessible via "livewire:editorjs" or "@livewire('editorjs')".
You can change this to whatever fits you best!
This option sets a global default for the placeholder property of Editor.js.
The placeholder will be displayed when an instance is created without any content.
This option sets the log level (console output) of Editor.js.
The available options are:
| Value | Definition |
|---|---|
| VERBOSE | Show all messages |
| INFO | Show info and debug messages |
| WARN | Show only warn messages |
| ERROR | Show only error messages (default) |
See Editor.js docs for reference.
This option defines, to which disk uploaded images should be stored.
Even though the disk can be changed on a per instance level, this option lets you set a global default.
This is always used, when you don't provide a disk name to the component instance through its props.
This option defines, to which disk downloaded images from the web should be stored.
Even though the disk can be changed on a per instance level, this option lets you set a global default.
This is always used, when you don't provide a disk name to the component instance through its props.
This package adds an make:editorjs command to your project.
With this command it's possible for you to create your own EditorJs livewire component.
This makes it possible for you to change and/or customize the component.
If you add your own component this way, you should disable the packages internal component registration
by setting enabled_component_registration in the livewire-editorjs.php config file to false.
Important!
By using this method to create your own component, any updates to the packages component won't affect you!
Which means any enhancements made won't be accessible to you.
If you want to customize the component or extend its functionality, the best way is to extend the component provided by this package. That way, you will receive updates and still can customize the internals.
<?php
namespace App\Http\Livewire;
use Maxeckel\LivewireEditorjs\Http\Livewire\EditorJS;
class MyCustomEditor extends EditorJS
{
// Put your custom code here
}composer testPlease see CHANGELOG for more information what has changed recently.
Please see CONTRIBUTING for details.
If you discover any security related issues, please email security@max-eckel.dev instead of using the issue tracker.
The MIT License (MIT). Please see License File for more information.
This package was generated using the Laravel Package Boilerplate.