Laraberg aims to provide an easy way to integrate the Gutenberg editor with your Laravel projects. It is built on top of the GutenbergJS project, implements all the necessary communication and adds an easy to use API. A demo can be found at demo.laraberg.io. If you would like to see an example of how to implement Laraberg you can take a look at the code from the demo over here.
- Installation
- Updating
- Configuration
- Usage
- Search Callback
- Missing Blocks
- Updating from 0.0.1 to 0.0.2-or-later
- Contributors
Install package using composer:
composer require van-ons/larabergAdd vendor files to your project (CSS, JS & Config):
php artisan vendor:publish --provider="VanOns\Laraberg\LarabergServiceProvider"In order to store the data for the Gutenberg editor, Laraberg needs to run a database migration:
php artisan migrate
This will create the 'lb_contents' and 'lb_blocks' tables.
The package provides a JS and CSS file that should be present on the page you want to use the editor on:
<link rel="stylesheet" href="{{asset('vendor/laraberg/css/laraberg.css')}}">
<script src="{{ asset('vendor/laraberg/js/laraberg.js') }}"></script>The Gutenberg editor expects React, ReactDOM, Moment and JQuery to be in the environment it runs in. An easy way to do this would be to add the following lines to your page:
<script src="https://unpkg.com/[email protected]/umd/react.production.min.js"></script>
<script src="https://unpkg.com/[email protected]/umd/react-dom.production.min.js"></script>
<script src="https://unpkg.com/[email protected]/min/moment.min.js"></script>
<script src="https://code.jquery.com/jquery-1.12.4.min.js" integrity="sha256-ZosEbRLbNQzLpnKIkEdrPv7lOy9C27hHQ+Xp8a4MxAQ=" crossorigin="anonymous"></script>When updating Laraberg you have to publish the vendor files again by running this command:
php artisan vendor:publish --provider="VanOns\Laraberg\LarabergServiceProvider" --tag="public" --forceWhen initializing the editor there are a number of configuration options you can provide. This is still a work in progress!
It is possible to set the height, maxHeight, and minHeight of the editor by providing the desired values in the options object:
Laraberg.init('[id_here]', { height: '500px' })
Laraberg.init('[id_here]', { maxHeight: '500px' })
Laraberg.init('[id_here]', { minHeight: '500px' })After publishing the vendor files you can find the 'laraberg.php' file in your config folder. This file allows you to configure the API Routes. Here you can change the URL prefix and the middleware for the routes.
When you change the route prefix you also have to provide the prefix when you initialize the editor like this:
Laraberg.init('[id_here]', { prefix: '/[prefix_here]' })If you wish to define the routes yourself you can do that by setting 'use_package_routes' to 'false' in the config. Then you can take the following routes and make changes as you see fit:
Route::group(['prefix' => 'laraberg', 'middleware' => ['web', 'auth']], function() {
Route::apiResource('blocks', 'VanOns\Laraberg\Http\Controllers\BlockController');
Route::get('oembed', 'VanOns\Laraberg\Http\Controllers\OEmbedController');
});Laraberg supports Laravel File Manager for uploading files. To enable uploading media through Laravel File Manager the laravelFilemanager field should be set to true. This will add a 'File Manager' button to the Gutenberg media blocks that will open Laravel File Manager for uploading and selecting media files.
Laraberg.init('[id_here]', { laravelFilemanager: true })If you are not using the default routes for Laravel File Manager you can provide the location of your Laravel File Manager endpoints in the options object like this:
Laraberg.init('[id_here]', { laravelFilemanager: { prefix: '/[lfm_prefix_here]' } })Note: Laraberg does not do any configuration on your Laravel File Manager setup. By default a lot of media filetypes can not be uploaded unless they are whitelisted in the Laravel File Manager configuration file. For more information on this you can check the Laravel File Manager documentation.
The Gutenberg editor should replace an existing textarea in a form. On submit the raw content from the editor will be put in the 'value' attribute of this textarea.
<textarea id="[id_here]" name="[name_here]" hidden></textarea>In order to edit content on an already existing model we have to set the value of the textarea to the raw content that the Gutenberg editor provided.
<textarea id="[id_here]" name="[name_here]" hidden>{{$model->getRawContent()}}</textarea>To initialize the editor all we have to do is call the initialize function with the id of the textarea. You probably want to do this insde a DOMContentLoaded event.
And that's it! The editor will replace the textarea in the DOM and on a form submit the editor content will be available in the textarea's value attribute.
Laraberg.init('[id_here]')If you want to use the editor, but for some reason do not want to deal with submitting forms there is a way to get the content from the editor through JavaScript:
let content = Laraberg.getContent()In order to add the editor content to a model Laraberg provides the 'Gutenbergable' trait.
use VanOns\Laraberg\Models\Gutenbergable;
class MyModel extends Model {
use Gutenbergable;
}This adds multiple attributes to your model that will help you with creating/updating/rendering the Gutenberg content.
$content // This is the raw content from the Gutenberg editor
$model = new MyModel;
// The model has to exist or else the link between your model and the content can't be made
$model->save();
// Add or update the content
$model->lb_content = $content;
// Get the rendered HTML
$model->lb_content;
// Get the raw Gutenberg output, this should be in the target textarea when updating content
$model->lb_raw_content;Note: The old renderContent, getRawContent, getRenderedContent and setContent methods from v0.0.4-beta and lower are deprecated and will be removed in a future release.
There is always the possibility that your model already implements a method with the same name as one of the Gutenbergable methods. Luckily PHP Traits provide an easy way to rename the methods from a trait:
class MyModel extends Model {
use Gutenbergable {
renderContent as renderLBContent;
}
public function renderContent() {
// Your method
}
}In this example you can just call the 'renderLBContent' method to render the content.
Rendering the Gutenberg content is very simple and happens like this:
<div id="your_container"> <!-- The element you want to render the content in -->
{!! $page->lb_content !!}
</div>Keep in mind that in order to correctly display some of the Wordpress styling the Laraberg CSS has to be present on the page:
<link rel="stylesheet" href="{{asset('vendor/laraberg/css/laraberg.css')}}">Gutenberg allows developers to create custom blocks. For information on how to create a custom block you should read the Gutenberg documentation.
Registering custom blocks is fairly easy. A Gutenberg block requires the properties title, icon, and categories. It also needs to implement the functions edit() and save().
const myBlock = {
title: 'My First Block!',
icon: 'universal-access-alt',
category: 'my-category',
edit() {
return <h1>Hello editor.</h1>
},
save() {
return <h1>Hello saved content.</h1>
}
}
Laraberg.registerBlock('my-namespace/my-block', myBlock)If you want to add your custom block to a new category you need to add that category first:
let title = 'My Category'
let slug = 'my-category'
Laraberg.registerCategory(title, slug)Laraberg implements Laravel events that you can use to implement your own listeners. The events contain a 'content' attribute that contains the relevant Content object. For information on how Laravel events work you can read the Laravel documentation.
- VanOns\Laraberg\Events\ContentCreated
- VanOns\Laraberg\Events\ContentRendered
- VanOns\Laraberg\Events\ContentUpdated
Laraberg provides a way to put your form fields in a seperate sidebar in the Gutenberg editor. This way you can let the editor take the entire screen while still having a place for your form fields. This is done by putting the input element in a parent element with the .laraberg-sidebar class. This is currently supported for the following input types:
- Checkbox
- Radio
- Select
- Text
- Textarea
For the labels Laraberg first checks if there is a label assigned to the element and will try to use that. If there is no label assigned it will check if there is a placeholder and use that as the label.
To enable the sidebar set the sidebar option to true when initializing Laraberg:
Laraberg.init('[id_here]', { sidebar: true })<div class="laraberg-sidebar">
...
<label for="article-public">Public</label>
<input id="article-public" name="public" type="checkbox">
</div><div class="laraberg-sidebar">
...
<label for="letter-a">A</label>
<input type="radio" name="letter" id="letter-a" value="a" checked>
<label for="letter-b">B</label>
<input type="radio" name="letter" id="letter-b" value="b">
<label for="letter-c">C</label>
<input type="radio" name="letter" id="letter-c" value="c">
</div><div class="laraberg-sidebar">
...
<label for="article-month">Month</label>
<select id="article-month" name="month" class="uk-select uk-form-large ">
<option value="1">January</option>
<option value="2">February</option>
<option value="3">March</option>
<option value="4">April</option>
...
</select>
</div><div class="laraberg-sidebar">
...
<input id="article-title" type="text" name="title" placeholder="Title" />
</div><div class="laraberg-sidebar">
...
<textarea name="excerpt" id="article-excerpt" placeholder="Excerpt"></textarea>
</div>The button block has a field that searches for pages or aritcles. In order to use this functionality you can pass a
callback function when initializing Laraberg. This callback functions will receive a search, perPage and type parameter. The callback should return an array of objects that contain a title and an URL or a promise that resolves to such an array.
let customSearch = (search, perPage, type) => {
return [
{
title: 'Laraberg Demo',
url: 'demo.laraberg.io'
}
]
}
Laraberg.init('content', { searchCb: customSearch })Since we have disabled direct file uploading, some of the media blocks require a media library to operate. This means that the following blocks will only be enabled when you're using Laravel Filemanager for now:
- Cover
- Gallery
- Media & Text
In beta version 0.0.1 we used JSON column types for block titles. This was not supported by MariaDB, so we had to change that. In the releasenotes for beta version 0.0.2 you can find how to deal with this problem if you do not want to lose your data from version 0.0.1.
 |
 |
|---|---|
| Maurice Wijnia | Mike Bronner |
