- Can I use beeflow/markdown-editor directly in Laravel without Symfony?
- No, this package is a Symfony bundle, so it requires workarounds like using `spatie/laravel-symfony-components` or manually extracting the core Markdown logic into a Laravel service. The frontend assets (JS/CSS) may also need adaptation for Laravel’s asset pipeline.
- How do I install this package in Laravel?
- Add the Git repo to your `composer.json` under `repositories`, require `beeflow/markdown-editor` as `dev-master`, then run `composer update`. However, you’ll need to abstract Symfony dependencies or use a bridge like `spatie/laravel-symfony-components` for Laravel compatibility.
- Does this editor support Blade templates instead of Twig?
- No, the editor uses Twig by default. You’ll need to replace Twig templates with Blade views or use a frontend framework like Alpine.js to bridge the editor’s output with Laravel’s Blade. The JS/CSS assets may also require adjustments for Laravel’s asset pipeline.
- What Laravel versions does this package support?
- The package itself doesn’t specify Laravel support—it’s a Symfony bundle. However, with workarounds (like `spatie/laravel-symfony-components`), it *can* work with Laravel 8.x or 9.x. Test thoroughly, as Symfony’s DI container won’t integrate natively.
- How do I store Markdown content in a Laravel database?
- This package doesn’t include ORM integration, so you’ll need to manually store Markdown in Eloquent models (e.g., a `text` or `longtext` column). Use Laravel’s built-in Markdown parsing (if available) or a facade like `spatie/laravel-markdown` to render it later.
- Are there performance issues with large Markdown documents?
- The editor uses GitHub-Flavored Markdown (GFM), which is efficient for most use cases. However, very large documents could strain client-side rendering. Test with your expected content size, and consider lazy-loading or server-side processing for heavy workloads.
- What alternatives exist for a Laravel-compatible Markdown editor?
- Consider `tiptap` (headless, customizable), `easymde` (lightweight, no Symfony dependency), or `summernote` (WYSIWYG with Markdown support). These avoid Symfony dependencies and integrate more cleanly with Laravel’s ecosystem.
- How do I handle the JS/CSS assets in Laravel Mix or Vite?
- Copy the editor’s assets to `resources/js/` or `resources/css/` and include them in your Laravel Mix/Vite config. You may need to adjust paths or dependencies, as the package assumes a Symfony asset pipeline. Test thoroughly to avoid conflicts.
- Is this package actively maintained? Should I fork it?
- The package has minimal activity (0 stars, no recent updates). Forking is an option, but evaluate whether the effort justifies the risks. Alternatives like `tiptap` or `easymde` are more mature and Laravel-friendly.
- Can I use this editor with Livewire or Inertia.js?
- Yes, but you’ll need to adapt the editor’s frontend to work with Livewire’s Alpine.js or Inertia’s Vue/React. Bind editor events to Livewire properties or Inertia actions, and ensure the Symfony backend logic is abstracted into Laravel services.