XB week 19: flickering cliffhanger
Last week ended with 12 remaining issues. Did we make it? :D Major loose ends Like last week, I’m starting with the major loose ends.
Last week ended with 12 remaining issues. Did we make it? :D Major loose ends Like last week, I’m starting with the major loose ends.
With DrupalCon Barcelona 2024 only two weeks later, the focus this week is on tying up loose ends.
We matched last week’s record: again 26 MRs merged! :D
A new record week: 26 MRs merged! :D Too much to cover, so going forward, I will only write about the most notable changes.
Monday August 19, 2024 definitely was a milestone:
How does cta1href sound to you? Gibberish, right? :D
The first prominent leap forward this week was built by Harumi “hooroomoo” Jang: they added the ability to Experience Builder (
The back-end heart of Experience Builder (XB) is its two-property field type.
This week started with undoing the horrors that y’all were subjected to last week: TwoTerribleTextAreasWidget featured prominently.
The Cypress front-end testing infrastructure clean-up landed on Monday, so this week we’ve already been seeing increased velocity!
Experience Builder (XB) allows crafting an experience using components. A tree of components.
Last week was very quiet, July 1–7’s #experience-builder Drupal Slack meeting was
It’s Drupal Dev Days week!
1.5 week prior, Lee “larowlan” + Jesse fixed a bug in the undo/redo functionality and added the fir
We started the week off with a first MVP config entity: the component config entity.
My Monday started with a pleasant surprise that is only possible in cross-timezone collaborations: Ted “tedbow”
Monday was a U.S. holiday, which meant I was able to go full-steam ahead on the sto
Experience Builder (XB) must be able to render single directory components (SDC
Acquia is sponsoring me full-time to operate as the tech lead for Experience Builder — thanks!