- How do I install jeffreyvr/dropblockeditor in a Laravel app?
- Install it via Composer with a pinned version, register the service provider as needed, and publish the package config and assets. Then mount the editor in a Blade or Livewire view and persist its JSON output in your own model or content table. Because the package is pre-1.0, pin 0.4.0 explicitly instead of using a floating constraint.
- Does Dropblockeditor support Laravel 11?
- Version 0.4.0 includes Laravel 11 compatibility work, so Laravel 11 is the most reasonable supported target to validate first. The release notes do not clearly confirm Laravel 10 support or the exact PHP version constraint, so check composer.json and test in a sandbox. Run a small integration spike before relying on it for production.
- Can I customize the available blocks in Dropblockeditor?
- Yes, Dropblockeditor is described as customizable and block-based, with Blade integration for rendering block views. You can define which block types content authors can drag into the editor and control how each block renders on the front end. Plan to test customization against the published assets and config because the package is still pre-1.0.
- How does Dropblockeditor store editor content?
- The package stores editor output as JSON, which you persist in your application's own database column or content model. That keeps the editor decoupled from a specific CMS schema, but it also means your app owns validation, sanitization, and rendering. Confirm that stored payloads remain compatible when upgrading versions.
- Does Dropblockeditor work with Livewire and Tailwind CSS?
- Dropblockeditor is built with Laravel Livewire and designed to integrate with Blade and Tailwind CSS. Fit is strongest in Laravel admin panels or CMS workflows that already use those tools. Validate the published frontend assets against your build toolchain, especially Vite and any CSP or security headers.
- Is Dropblockeditor safe to use in production?
- Treat it as a pre-1.0 package and assess it with a time-boxed integration spike rather than assuming production maturity. The main risks are API instability, sparse release documentation, and unclear backward compatibility between versions. Laravel 11 support reduces framework-version risk but does not by itself prove security posture or upgrade safety.
- How do I handle image uploads with Dropblockeditor?
- The package advertises image uploads as part of its block editor feature set, but the exact upload configuration and storage path should be confirmed against the published config and source. You will likely need to define disk, validation, and authorization rules in your Laravel app. Test uploads with your real storage driver and security headers before rollout.
- What are the alternatives to Dropblockeditor for Laravel?
- Alternatives include other Livewire-based editors, richer CMS packages, and JavaScript block editors integrated manually into Laravel. Dropblockeditor's appeal is its lightweight Laravel Livewire and Tailwind fit for simple page building and rich content editing. Compare alternatives on schema stability, sanitization, maintenance cadence, and upgrade path if content authoring is central to your product.
- How do I upgrade Dropblockeditor from 0.3.1 to 0.4.0?
- Pin the version explicitly in Composer, branch the upgrade, and republish or diff the config and assets between 0.3.1 and 0.4.0. Review the Laravel 11 pull requests for behavioral changes not covered in release notes, then run regression tests for editor load, save, validation, and rendering. Keep the upgrade separate from unrelated Laravel 11 migration work.
- Does Dropblockeditor validate or sanitize block content?
- The package provides the editing interface and JSON output, but server-side validation and HTML sanitization remain your application's responsibility unless the source shows otherwise. Validate the JSON structure and sanitize rendered block content at output time. This is especially important because the release notes do not document a built-in sanitization pipeline.