--- title: "Drupal Dev Days Ghent 2022 Sprints" date: "2022-06-17T14:43:09+00:00" summary: image: type: "article" url: "/acquia-cloud-platform/help/90941-drupal-dev-days-ghent-2022-sprints" id: "c475c6ef-932b-4e69-ba46-237eda4c1770" --- Table of contents will be added _So what was DDD Ghent like?_ Statistics ---------- * [137 issues across all projects](https://www.drupal.org/project/issues/search?issue_tags=ddd2022) * 52 of the 137 (38%) for core, of which 7 already fixed * [19 of the 52 (37% of core, or 14% of total) on CKEditor 5](https://www.drupal.org/project/issues/search/drupal?project_issue_followers=&component%5B%5D=ckeditor5.module&issue_tags_op=%3D&issue_tags=ddd2022), 3 already fixed (all discovered _at_ DDD, 2 of which for upgrade path) * 16 of the 19 discovered at DDD _I'm especially interested in sprinting on the CKEditor 5 module for Drupal core, since that's what I am [currently working on for Acquia](https://wimleers.com/blog/cke5-gcw), because that is one of the biggest must-haves/blockers for Drupal 10. 86% of issues worked on at DDD Ghent was not CKEditor 5, so … I'm hoping others will do blog posts similar to this one! :D_ New contributors ---------------- I worked with _at least_ a dozen people who'd never contributed to CKEditor 5 before. I mentored in various ways: how to do the issue write-up, how to debug, how to find examples, how to write a kernel test, how to use data providers, how to run _and_ write a functional JS test, how to create a contrib-to-core CKE5 button upgrade path, etc. I know that (my colleague and fellow CKEditor 5-in-core contributor) [lauriii](https://www.drupal.org/u/lauriii) mentored [scott\_euser](https://www.drupal.org/u/scott_euser) to help us get external images support, and he helped someone else write a complex CKE5 plugin that the popular `token_filter` module will be able to use for its upgrade path too. Thanks to all of you who contributed to the CKEditor 5 module in Drupal core last week (in alphabetical order): [andreasderijcke](https://www.drupal.org/u/andreasderijcke), [brentg](https://www.drupal.org/u/brentg) [DieterHolvoet](https://www.drupal.org/u/dieterholvoet), [Dom.](https://www.drupal.org/u/Dom.), [Eli-T](https://www.drupal.org/u/eli-t), [ifrik](https://www.drupal.org/u/ifrik), [jcnventura](https://www.drupal.org/u/jcnventura), [joevagyok](https://www.drupal.org/u/joevagyok), [marcvangend](https://www.drupal.org/u/marcvangend), [mpp](https://www.drupal.org/u/mpp) and [seanB](https://www.drupal.org/u/seanb). Better still: several of these people started issues of their own and ended up collaborating on each other's issues! Takeaways --------- The #1 takeaway for Lauri and I was that the upgrade path we had written assumed _valid_ text format + CKEditor 4 configuration, which was _definitely_ a faulty assumption, since just like the text format admin UI had done historically, there was _no validation_ for any of this: the site builder is expected to _know_ valid filter orders and which filters ought not to be enabled while using CKEditor 4. This utter lack of validation and hence guidance is what CKEditor 5 definitely does much better. But … we need to get those sites upgraded to CKEditor 5 too. That was the top critical we found, and it's already fixed: [#3273312](https://www.drupal.org/project/drupal/issues/3273312). Basically, most long-time Drupalists apparently create new text formats and always add `filter_autop` and `filter_url` to them out of habit. The _majority_ of people testing the upgrade path ran into this! But extra special thanks go to [ifrik](https://www.drupal.org/u/ifrik) and [Dom.](https://www.drupal.org/u/Dom.) they worked on CKEditor 5 the _entire week_ and both not only reported but also contributed to lots of issues! The second most frequent hurdle was contrib CKE4 plugins not having any actionability: the user feels stuck. We're improving on that in [#3273325](https://www.drupal.org/project/drupal/issues/3273325). And more importantly, we're starting to see that some modules are obsolete, which means core can (and MUST!) provide an upgrade path for certain contrib modules see [#3274278](https://www.drupal.org/project/drupal/issues/3274278) for the first of that, and we now have a [Drupal handbook page where coordination is now happening](https://www.drupal.org/docs/core-modules-and-themes/core-modules/ckeditor-5-module/upgrade-coordination-for-modules-providing-ckeditor-4-plugins). And despite not feeling well at all, lauriii still attended the magnificent live accessibility testing that we got from [Bram Duvigneau](https://twitter.com/bramduvigneau), where he basically applauded our CKEditor 5 toolbar configuration admin UI. (And found some hurdles in CKEditor 5 itself when using NVDA.) > Live accessibility testing of Drupal 9 [@ckeditor](https://twitter.com/ckeditor?ref_src=twsrc%5Etfw) 5 integration at [@drupaldevdays](https://twitter.com/drupaldevdays?ref_src=twsrc%5Etfw) by [@bramduvigneau](https://twitter.com/bramduvigneau?ref_src=twsrc%5Etfw) with [@wimleers](https://twitter.com/wimleers?ref_src=twsrc%5Etfw) [https://t.co/JRphSVpNcK](https://t.co/JRphSVpNcK) [pic.twitter.com/w9XtsuKMaB](https://t.co/w9XtsuKMaB) > > Gábor Hojtsy (@gaborhojtsy) [April 7, 2022](https://twitter.com/gaborhojtsy/status/1512059083129593858?ref_src=twsrc%5Etfw) So I'd say: the sprints at DDD were a _big success!_ And not just on the technical front: I got to show my hometown to many fellow Drupalists, so I have many beautiful memories to look back to :) > Morning [#Drupalers](https://twitter.com/hashtag/Drupalers?src=hash&ref_src=twsrc%5Etfw). Let's get ready for Day 3 of [#DrupalDevDays](https://twitter.com/hashtag/DrupalDevDays?src=hash&ref_src=twsrc%5Etfw). Hope this group photo helps you energise for today :D > > Today's schedule at [https://t.co/RAa7HfN9t6](https://t.co/RAa7HfN9t6) > > Get Set Go! > > (Many thanks to [@BramDriesen](https://twitter.com/BramDriesen?ref_src=twsrc%5Etfw) and [@Borisson](https://twitter.com/Borisson?ref_src=twsrc%5Etfw) for coordinating and taking this amazing group photo) [pic.twitter.com/rGXMyyrAH5](https://t.co/rGXMyyrAH5) > > Drupal Dev Days (@drupaldevdays) [April 6, 2022](https://twitter.com/drupaldevdays/status/1511595482568658949?ref_src=twsrc%5Etfw)