Installation & Setup
Last updated:
On this page
Installing
Until it's on Packagist, add the repositories and require the package:
"repositories": [
{ "type": "vcs", "url": "https://github.com/Javaabu/block-editor" },
{ "type": "vcs", "url": "https://github.com/Javaabu/forms" },
{ "type": "vcs", "url": "https://github.com/Javaabu/manifest" },
{ "type": "vcs", "url": "https://github.com/Javaabu/stencil" }
]
composer require javaabu/block-editor:^1.0@dev
The service provider is discovered automatically. Nothing needs configuring for the common case.
The editor's JavaScript
The package registers its assets with javaabu/manifest:
| Asset | What |
|---|---|
block-editor::styles |
The stylesheet for the editor and for rendered content |
block-editor::editor |
The Blade entry: mounts every editor on the page |
@javaabu/block-editor |
The TypeScript, for your own code and React (@javaabu/block-editor/react) |
<x-block-editor::editor> and <x-block-editor::content> ask manifest for what they need, and manifest adds the tags to the page. If your app builds with Vite, add manifest's plugin (see the manifest docs) and install the npm dependencies:
php artisan manifest:check
npm install @javaabu/onu @tiptap/core @tiptap/pm @tiptap/starter-kit @tiptap/extension-table \
@tiptap/extension-text-align @tiptap/extensions @tiptap/suggestion @tiptap/react \
@tiptap/static-renderer @tiptap/extension-image @tiptap/extension-placeholder react react-dom
Blade apps need React too: the editor uses Onu's TipTap extensions, whose module imports it. The React components also need @javaabu/forms (javaabu/react-forms). It's declared for Inertia pages only (for: 'pages'), so manifest:check asks for it only when your package.json has an Inertia adapter:
npm install github:Javaabu/react-forms#next-gen
Apps without Vite use the prebuilt files in vendor/javaabu/block-editor/dist, which manifest serves by itself.
Inertia React
With manifest's Vite plugin, import the components:
import { BlockContent, BlockEditorField } from "@javaabu/block-editor/react"
They import the stylesheet themselves, so Vite bundles it with any page that uses them: there's nothing to add for the styles.
Pass the editor config from PHP. It holds the profile's blocks and the translated strings:
return Inertia::render('Posts/Edit', [
'post' => $post,
'editor' => BlockEditor::editorConfig(),
]);
Publishing
php artisan vendor:publish --tag=block-editor-config # config/block-editor.php
php artisan vendor:publish --tag=block-editor-translations # lang/vendor/block-editor
php artisan vendor:publish --tag=block-editor-views # resources/views/vendor/block-editor