This is a follow-up to my DrupalCon Pittsburgh talk. It does not provide an overview of the status nor the progress, but instead it’s hands-on, with 2 live demos to help attendees: use Config Inspector to find which config is still missing validation constraints, add it, and observe it catching invalid data — by adding 3 lines of YAML! update existing config forms to use validation constraints, including tweaking the validation error message — by adding 6 lines of YAML and copy/pasting 5 lines of PHP! Each in less than 5 minutes, including the explanation! In other words: everybody ..read more

Drupal 8 shipped with many exciting new concepts, including “configuration”, “configuration and content entities”, “validation constraints” and “API-First”. The missing link between these has always been the inability to modify configuration through Drupal’s REST or JSON:API. Because only content entities have validation constraints. This has been the #1 blocker to the Drupal (JS) Admin UI initiative: validation of configuration unfortunately (but understandably) still is hardcoded in the PHP-based form logic. But … in the background, the foundation was laid during the Drupal 8 cycle ..read more

On behalf of Acquia I’m currently working on Drupal’s next big leap: Automatic Updates & Project Browser — both are “strategic initiatives”. In November, I started helping out the team led by Ted Bowman that’s been working on it non-stop for well over 1.5 years (!): see d.o/project/automatic_updates. It’s an enormous undertaking, with many entirely new challenges — as this post will show. For a sense of scale: more people of Acquia’s “DAT” Drupal Acceleration Team have been working on this project than the entire original DAT/OCTO team back in 2012! The foundation for both w ..read more

Drupal 8 shipped with many exciting new concepts, including “configuration”, “configuration and content entities”, “validation constraints” and “API-First”. The missing link between these has always been the inability to modify configuration through Drupal’s REST or JSON:API. Because only content entities have validation constraints. This has been the #1 blocker to the Drupal (JS) Admin UI initiative: validation of configuration unfortunately (but understandably) still is hardcoded in the PHP-based form logic. But … in the background, the foundation was laid during the Drupal 8 cycle ..read more

On behalf of Acquia I’m currently working on Drupal’s next big leap: Automatic Updates & Project Browser — both are “strategic initiatives”. In November, I started helping out the team led by Ted Bowman that’s been working on it non-stop for well over 1.5 years (!): see d.o/project/automatic_updates. It’s an enormous undertaking, with many entirely new challenges — as this post will show. For a sense of scale: more people of Acquia’s “DAT” Drupal Acceleration Team have been working on this project than the entire original DAT/OCTO team back in 2012! The foundation for both w ..read more

So what was DDD Ghent like? Statistics 137 issues across all projects 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, 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, 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 ..read more

Together with zrpnr, gabesullice, lauriii, bnjmnm, yashrode and hooromoo in Acquia’s Drupal Acceleration Team, I’ve been working on getting Drupal on CKEditor 5, because CKEditor 4 is reaching the end of its long and productive life. zrpnr got it started in January 2021. We’ve been meeting with Reinmar 1 from the CKEditor 5 team to ensure a smooth automatic upgrade path from CKEditor 4: all functionality should be even better! Less than 10 months later, on November 11, 2021, CKEditor 5 was committed to Drupal 9.3! But … it’s not yet stable. It’s an experimental module. We have a road ..read more

For the past two years I’ve been working on something less visible but no less important. Since DrupalCon Amsterdam 2019 (an actual in-person conference — sounds surreal in 2021, doesn’t it?!) I’ve been working on Acquia Migrate Accelerate, or “AMA” for short. In a few days, another DrupalCon Europe is starting … so perfect timing for a recap! :D Why? Drupal 8 comes with an awesome migration system built in, originating in the Migrate Drupal 7 module. It standardized many migration best practices. But it still required a huge time investment to learn it. Of course, there’s the ..read more

Mateu, Gabe and I agreed to sunset the API-first initiative, about which I’ve written a lot in 2016–2019. We’ve all spent countless hours on it — Gabe and I were able to work on it mostly full time, Mateu contributed an incredible amount of his free time to get the API-first initiative and the JSON:API module ecosystem in particular to where it is today. I learned a lot from these two lovely people, and we also had lots of laughs! API-first Drupal with multiple consumers @DrupalConNA :D pic.twitter.com/GhgY8O5SSa — Gábor Hojtsy (@gaborhojtsy) April 11, 2018 Mateu wrote a great ..read more

On 7 January, 2020, the Drupal module JSON:API 1.x was officially marked unsupported. This date was chosen because it is exactly 1 year after the release of JSON:API 2.0, the version of JSON:API that was eventually committed to core. Since then, the JSON:API maintainers have been urging users to upgrade to the 2.x branch and then to switch to the Drupal core version. We understand that there are still users remaining on the 1.x branch. We will maintain security coverage of the 8.x-1.x branch for 90 days. That is, on 6 April, 2020, all support for JSON:API, not in Drupal core, will end. Pl ..read more