- What is idf/nova-unlayer-field used for?
- It adds a Laravel Nova form field that embeds the Unlayer drag-and-drop email and landing-page editor inside Nova resources. Authors can design responsive emails visually and persist the editor design JSON and rendered HTML through the same Eloquent resource. It is an authoring tool for Nova admin panels, not a sending, rendering, or headless content service.
- How do I install idf/nova-unlayer-field?
- Install it with Composer using composer require idf/nova-unlayer-field, then register the field class on the relevant Nova resource. You will also need a paid Nova license, a configured Unlayer project, and database columns for the design JSON and HTML output. Verify the exact namespace, field options, and asset registration steps in the repository README before wiring it into production.
- How do I configure the Unlayer field on a Nova resource?
- Add the field to your Nova resource's fields method and point it at the JSON and HTML columns you want to persist. Configure the Unlayer project and any editor options required by your templates, then test save, reload, and export flows in a non-production resource. Because the package is a thin adapter, confirm which Unlayer options are exposed by the field and which must be handled in your own code.
- Which Laravel, PHP, and Nova versions are supported?
- The available evaluation does not establish a broad compatibility matrix, so treat the package as version-sensitive. Match its Composer constraints to your Nova major version, Laravel version, and PHP runtime, and pin all three in composer.lock. Validate browser support, CSP rules, and Nova asset compilation in a staging environment before upgrading Nova or Laravel.
- Does this package save both the Unlayer design JSON and the rendered HTML?
- The field is intended to persist the Unlayer design JSON and the rendered HTML through your Nova resource, letting you reload the design later and consume the HTML elsewhere. You should confirm the exact column names, casts, and field configuration in the README, and store the JSON in a JSON or text column and the HTML in a longText column. Do not assume the package also provides production email rendering or delivery.
- How are images uploaded and stored with the Nova Unlayer field?
- Unlayer provides image selection and upload features in the editor, but the Nova package does not appear to supply a complete asset lifecycle. Plan your own storage, CDN, access control, and retention policy for uploaded images, and test upload, reload, and export behavior against your Unlayer plan limits. Confirm whether images are stored by Unlayer, your application, or both before launch.
- Is the HTML saved by Unlayer safe to render to users?
- No, saved editor HTML should not be treated as trusted markup just because it came from Nova. Sanitize it server-side with an HTML sanitizer before rendering on public pages or injecting it into outbound email templates, and enforce a Content Security Policy for editor scripts and images. The package is an authoring adapter and does not replace your application's XSS and content-security controls.
- Do I need a paid Unlayer plan and a Laravel Nova license?
- Yes, this package assumes you already have a paid Laravel Nova license because it is a Nova field. It also integrates Unlayer, so you will likely need an Unlayer account or plan; confirm which plan features, upload limits, export options, and commercial terms you require. The package's MIT license does not cover Nova or Unlayer costs.
- What are the alternatives to this package for email editing?
- If you are not standardized on Laravel Nova, use Unlayer's SDK directly, choose a different editor, or build the authoring UI in Filament or custom Livewire. For headless or API-first authoring, avoid this field because it is tied to the Nova admin form workflow. If you are on Nova but want less vendor coupling, evaluate a maintained fork or a smaller custom field that saves JSON and exports HTML separately.
- How should I test and maintain this package in production?
- Start with a proof of concept on one Nova resource and test save, reload, export, image upload, CSP behavior, and rollback before wider rollout. Pin the package, Nova, Laravel, PHP, and Unlayer SDK versions, and assign an owner for quarterly Composer and vendor updates. Because adoption is low and the project is single-maintainer, budget for fork-and-maintain support and keep a read-only fallback if the editor breaks.