Producing content diff to compare revisions is harder to configure when using view modes.It can be harder to debug with content moderation.If asymmetrical translation is chosen, it can introduce impediments if there is a need to re-translate content/update translations.Basically, we need to decide if Paragraphs will be synced between translations or not, and it can be hard to explain configuration choices to project stakeholders, especially with nested Paragraphs. The translation choice needs to be done at the beginning of the project and changing after can come with a significant cost.Performances are then harder to handle on the backend, frontend, APIs, and content indexing. In some cases, we can expect high load on the database. It can be challenging when entities are starting to grow, with many Paragraphs.Paragraphs can come with some complexity: Some modules are even proposing an experience that is close to Gutenberg with the block selector, re-ordering and frontend like WYSIWYG (example: Geysir) There are multiple ways to enhance it with other contributed modules, and it integrates well with all Drupal subsystems (entities, moderation, translation, etc.). I really loved Paragraphs, there is a vibrant ecosystem, and it is widely adopted (more than 210K reported installations). But plugins can be complex to write, and it might take time for the plugin ecosystem to grow. Briefly: it has the same potential as Gutenberg and can use a single field to represent complex layouts. It looks similar to version 4, but is a much more powerful editor when it comes to extensions.Īmazee Labs was an early adopter of CKEditor 5, since Drupal 8, and we've built great EX with the implementation of CK5 Sections that even came with a GraphQL integration. We've seen that it comes out of the box with Drupal 10. Let's start with the big picture, what are the solutions out there? It’s impossible to list them all, but let’s focus on 4 popular ones. Now we can dive into the tool that the Content Editors will face every day: the edit form.

And we can also appreciate all the love that the community brought to Drupal.

This was a pretty long introduction, but it's important to know about this evolution, to evaluate the journey to a better EX. Here is a screenshot of the good ol' times, look ma, no WYSIWYG out of the box 😱 Let's travel back in time a bit and do a role-playing game, to experience what it was like to be a first-time evaluator, trying to determine if Drupal was the right match for an editorial team. I often heard that the Drupal UI and Editorial Experience (EX) was not so nice compared to other solutions. Spoiler alert: what if we could combine the strengths of two worlds? The content modelling capabilities of Drupal with the delightful Editorial Experience (EX) of the WordPress Gutenberg editor? If you haven't tried the Gutenberg editor yet, I highly recommend clicking here and taking a 2-minute break to form your own opinions of its features. It's also one of the most expressive and sustainable tools for developers to meet project goals, but what about content editors? While it might not be a good fit anymore for simple projects, it's still hard to beat if we compare its capabilities to similar SaaS editorial solutions.

Drupal gin theme