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. Custom Logo support (e.g.And it's open source.Support for custom CSS overrides (see 'Notes' section).Choose from 3 different Toolbars (Sidebar, Minimal, Legacy).

Accent colors (? Blue, ? Orange, ? Green, ? Red, ? Purple etc.).Gin's Settings can be found at /admin/appearance/settings/gin This might be related to your minimum-stability setting in composer.Ī demo can be found over at. Enable the Theme in the backend /admin/appearance.

8.x-2.x requires Drupal 8.8+ 8.x-1.x requires Claro installed as a contrib module. Older Versions 8.x-3.x-alpha37 is the last release to support Drupal 8.8. Built on the foundation of Claro from one of the lead designers of Claro & Drupal Design System. The Gin theme also includes things which are currently out of scope for Claro and/or some customisations we're experimenting with for the future. A radically new UI layout paired with goodies like a Darkmode will give your Drupal's Admin interface a facelift.

Drupal gin theme