Weave Code
Nova Gutenberg Laravel Package
genealabs/nova-gutenberg
Adds a Gutenberg block editor field to Laravel Nova, letting you build rich content with WordPress-style blocks inside your admin panel. Stores block content as JSON/HTML and renders it on the front end, bringing flexible page building to Nova resources.
Implementation of the Gutenberg editor as a Laravel Nova Field based on Laraberg.
Frequently asked questions about Nova Gutenberg
- How do I install genealabs/nova-gutenberg in Laravel Nova?
- Install with composer require genealabs/nova-gutenberg, publish the package assets, and add a nullable json or longText column for the field. In your Nova resource, add Gutenberg::make('content') alongside your other fields. Because the repository is archived, verify the Composer constraints in the 0.6.1 tag against your PHP and Nova versions before scheduling the work. A proof of concept is realistically a one- to two-day task.
- Which Laravel and Nova versions does nova-gutenberg support?
- The package does not publish a support matrix; the only reliable source is the Composer constraints shipped in release 0.6.1. That release landed on 2024-03-12, and compatibility with Nova majors released after that date is unproven. Test against your exact Nova and PHP versions in a staging app, and plan an upgrade path or fork if you need the next Nova major.
- How does nova-gutenberg store content, as JSON or HTML?
- The field persists Gutenberg block output as a block document, stored as JSON or HTML in a single column. Nova and your application then treat that column as an opaque blob, so native search, sorting, filtering, and validation do not apply to its contents. Autosave and revision history are not documented, so do not assume the field protects an editor's work on a failed request.
- Is genealabs/nova-gutenberg still maintained?
- The GitHub repository is archived, and the last release was 2024-03-12, a Composer dependency fix. It has roughly 106 stars and zero dependents, which means there is no downstream population to surface breakage first and no community fork maintaining it. If you adopt it, name an internal owner and budget for forking the package and rebuilding the bundled Gutenberg and React assets yourself.
- How do I render Gutenberg block content on my Laravel frontend?
- Render either the stored block JSON through your own parser or pre-rendered HTML written to a cache column when the record is saved. Avoid parsing blocks on every request for public pages. Whichever path you choose, sanitize the output and keep the renderer under your own control.
- Is nova-gutenberg output sanitized, and what about XSS?
- Sanitization ownership is undocumented, and stored editor HTML rendered on public pages is a direct XSS consideration. Establish from the source whether the package sanitizes anything server-side, then sanitize in your renderer or Blade template regardless. Treat the field strictly as an admin authoring tool, not as a trusted HTML source.
- How do image and embed blocks resolve media in nova-gutenberg?
- The documentation does not state whether image blocks accept plain URLs, Nova file references, or disk paths, so read the source and test the behavior directly. Check what breaks when media moves between disk, CDN, or storage drivers. Prefer a stable media resolver over storing raw paths inside block JSON.
- Can I search, filter, or sort Gutenberg content in Nova?
- No, not out of the box. Nova search, sorting, filtering, and validation see the field as a blob, so indexing, querying, or transforming block content is custom application work rather than field configuration. Budget for that separately if content must be queried or used to drive listings.
- How do I migrate existing HTML or Markdown content into nova-gutenberg?
- Add a new nullable json column rather than overwriting existing content, then migrate legacy HTML or Markdown into raw-HTML or classic blocks at best. Expect fidelity loss on the first pass, and run a dry run against a production snapshot to quantify it. Keep the legacy field mounted behind a feature flag so rollback is a configuration change rather than a data restore.
- What are the alternatives to nova-gutenberg for rich content in Laravel?
- If the need is rich editing on public-facing forms rather than a Nova admin field, use Laraberg directly instead of this package. If you need only admin authoring, Nova's built-in Markdown or Text fields may be sufficient. Choose nova-gutenberg only where Laravel Nova is already a committed platform choice and you can staff an internal owner for the component.
Weaver
How can I help you explore Laravel packages today?