r/PHP • u/UnfairBattle164 • 17h ago
Discussion Migrating a large Laravel app from CKEditor 4 to Editor.js — looking for architectural advice
Hey everyone,
I’m working on a fairly large Laravel application that currently uses CKEditor 4, and migrating to Editor.js is now a requirement.
The project uses the Repository Pattern, and CKEditor is used across multiple modules. I’m trying to figure out the right way to approach the migration without making a huge change all at once.
My main concerns are:
- Where should Editor.js-related logic live in a Repository Pattern project?
- Should I create a separate service for Editor.js, or keep things within the existing module structure?
- How should validation and sanitization be handled?
- What’s a good approach for rendering Editor.js JSON on the frontend?
- We already have a lot of CKEditor HTML stored in the database. What’s the safest way to handle/migrate that?
- Is it better to migrate module-by-module while keeping CKEditor working for the modules that haven't been migrated yet?
- What would you recommend for the overall folder/file structure?
I’m especially interested in hearing from anyone who has migrated CKEditor/TinyMCE or another HTML-based editor to Editor.js in a large Laravel application.
I’m a junior developer, so I’d really appreciate practical advice on how you would structure this rather than just “replace the editor” at the frontend level.
Thanks!