Nova Unlayer Field Laravel Package

Technical Evaluation

• Architecture fit: Thin Laravel Nova admin-field adapter around Unlayer’s client-side email/landing-page builder. Good fit only for Laravel applications already standardized on Nova for content operations and comfortable storing editor JSON/HTML in Eloquent models. Poor fit for API-only/headless authoring, non-Nova admin stacks, or public-facing editors.
• Integration feasibility: Feasible as a contained proof of concept: install via Composer, register the field on a Nova resource, add JSON/HTML storage columns, configure an Unlayer project, and validate save/load/export/image-upload behavior. Requires a paid Nova license and likely an Unlayer account/plan; confirm plan limits before estimating effort.
• Technical risk: Low adoption signal: 34 stars, zero dependents, and release metadata appears future-dated. Main risks are single-maintainer continuity, Nova major-version breakage, Unlayer SDK/CDN changes, CSP restrictions, image/asset lifecycle management, export fidelity, unsanitized HTML/XSS, and vendor lock-in/cost. Treat the package as a tactical accelerator, not a strategic platform dependency.
• Key questions: Which Nova, Laravel, PHP, and browser versions are supported? Does the field persist both design JSON and rendered HTML? How are images uploaded, hosted, and expired? Is export client-side or server-side? What Unlayer plan/features are required? Is rendered HTML sanitized? Who maintains compatibility? Can we fork/pin if abandoned? What are the data-residency, DPA, and content-retention terms?

Integration Approach

• Stack fit: Laravel + Nova only. Best where editors already work in Nova and content lives in MySQL/Postgres JSON/text columns. Delivery should consume exported HTML or a separate rendering service; do not assume the field provides production rendering. Avoid if the admin stack is Filament, custom Livewire, or headless/API-first.
• Migration path: Start with a non-production proof on one Nova resource. Add nullable design/HTML columns, register the field, configure Unlayer, and test persistence, image upload, export, and reload. Run in parallel with the incumbent editor, backfill by importing legacy HTML or recreating high-value templates, feature-flag access, and keep a read-only fallback plus rollback path.
• Compatibility: Pin the package, Nova, Laravel, PHP, Node/build tooling, and Unlayer SDK version. Validate CSP rules for scripts/images, browser support, database JSON support, and Nova asset compilation. Confirm there is no conflict with existing Nova fields or custom tools. Prefer a maintained fork over unpinned upstream if the package stalls.
• Sequencing: (1) license/procurement and security review; (2) isolated field and persistence POC; (3) image/asset pipeline; (4) template and approval workflow; (5) sanitize/render/delivery path; (6) content migration; (7) pilot authors; (8) production rollout with support runbook.

Operational Impact

• Maintenance: Small MIT codebase, but three moving dependencies: Nova, Unlayer, and the browser SDK. Assign an owner for quarterly upgrades, Composer updates, and Unlayer plan changes. With low stars and no dependents, budget for fork-and-maintain rather than relying on community support.
• Support: No commercial SLA from the package; Unlayer supports its platform, not the Nova integration. Authors will need training on editor behavior, image handling, templates, and export expectations. Maintain an internal runbook for editor failures, upload issues, and broken exports, with escalation to Laravel/Nova or Unlayer as appropriate.
• Scaling: Client-side editing scales reasonably with author concurrency, but storage and rendering scale separately. Plan for JSON/HTML growth, image CDN/storage, backups, and Unlayer plan limits. High-volume email sends or landing-page traffic should be decoupled from Nova authoring.
• Failure modes: Blocked CDN/SDK or CSP misconfiguration makes the field unusable; Nova upgrades can break the Vue field; invalid JSON or unsanitized HTML can produce broken or unsafe pages; expired image URLs cause missing assets; vendor outage blocks authoring; plan limits can disable export. Mitigate with validation, sanitization, backups, fallback editing, and alerting.
• Ramp-up: Laravel/Nova developers can complete a POC in days; production hardening and content migration likely take weeks depending on templates, assets, and security requirements. Non-Nova teams face materially higher cost due to admin-stack mismatch. TPM should secure Nova/Unlayer budget, security review, and content-owner training before commitment.