- What is hyperlab-be/nova-froala-field used for?
- It is a Laravel Nova field that integrates the Froala WYSIWYG editor into your Nova admin panel. It is used for rich text content with image and file uploads, configurable toolbars, full-screen editing, and clean HTML output. The field is configured per field inside your Nova resources.
- How do I install hyperlab-be/nova-froala-field?
- Install it with Composer using composer require hyperlab-be/nova-froala-field. Then add the package's Froala field to your Laravel Nova resource. Check the package's Composer constraints before installing to confirm it matches your Nova and Laravel versions.
- How do I add the Froala field to a Laravel Nova resource?
- Add the package's Froala field to the fields method of your Nova resource and call make with the attribute name. Configuration is done per field instance, so you can chain options directly on that field. Check the package README for the exact class import and available methods for your version.
- Does nova-froala-field support image and file uploads?
- Yes, the package offers image and file uploads inside the Froala editor. This lets editors insert media while creating rich text in Nova. Upload behavior depends on the field options and your application's storage setup, so review the package documentation for configuration details.
- Can I configure the Froala toolbar per field?
- Yes, the toolbar is configurable and the package is designed for per-field configuration. You can set toolbar options on each field instance in your Nova resource. This lets different resources use different editing experiences without changing global code.
- Does this Laravel Nova Froala field support full-screen editing?
- Yes, the field includes full-screen editing for the Froala editor. This is useful for longer content where more editing space helps. It is part of the editor experience provided inside Nova.
- Which Laravel and Laravel Nova versions are supported?
- The package is built for Laravel Nova, but supported Laravel and Nova versions depend on the specific release you install. Check the package's composer.json and release notes for exact version constraints. Pin a version that matches your application's Nova and Laravel versions.
- Does nova-froala-field output clean HTML, and is it safe to render?
- The package is described as producing clean HTML output from the Froala editor. Clean output is not the same as full security sanitization, so you should still sanitize stored HTML before rendering it. Treat editor content as user input and apply your application's normal XSS protections.
- How can I test a Laravel Nova resource that uses this field?
- Test persistence and validation of the underlying rich text attribute as part of your normal Nova resource tests. For browser tests, confirm the editor loads and that image or file uploads work with your configured storage. Mock or configure external editor assets and upload disks in CI so tests remain reliable.
- Is nova-froala-field production-ready, maintained, and what alternatives should I consider?
- For production use, review the package's release activity, Composer constraints, and issue history, then pin a version that matches your Nova and Laravel setup. Secure upload storage and sanitize rendered HTML as part of your deployment checklist. Alternatives include other Laravel Nova WYSIWYG fields such as Tiptap, CKEditor, or TinyMCE integrations; compare toolbar features, upload handling, and Nova compatibility. If you specifically need Froala, this package is the direct fit.