XB week 18: DriesNote deadline

Ben “bnjmnm” Mullins finished the highest-impact loose end: he ensured all single-value field types work correctly.

Major loose ends

Your browser does not support playing videos. You can download it instead.

Drag a component and drop it into truly any location.

Issue #3471169, video by Bálint.

I titled last week’s update drag and drop party because there were so many improvements on that front. But one critical piece was still missing: it was painful to drag components into locations that are difficult to visualize: top and bottom of slots, even more so for adjacent slots. Bálint “balintbrews” Kléri brought one additional improvement:

Goal: make it possible to follow high-level progress by reading ~5 minutes/week. I hope this empowers more people to contribute when their unique skills can best be put to use!

JSX Theme Engine. Ben had gotten the foundations in place in week 10 and then brought basic Redux integration for live updates of the preview in week 11. We knew there were lots of loose ends, but we had no choice but to move on to higher priorities.

Week 18 was September 9–15, 2024.

Lots of usability bugs squashed

Beautiful isn’t it?! I couldn’t say it better than Jesse “jessebaker” Baker in his review: This is such a marked improvement and honestly it’s already better than I dared hope it would be, especially this early. Excellent work.

all posts tagged Experience Builder.

Jesse coordinated the squashing of many usability bugs — not really broken things, but things that should happen to not have a clunky UX:
Who of you have ever been able to chill towards a deadline, and how did you do that? 😀

Back-end improvements

Initial UI that shows the reason why an SDC is not available in XB.
Initial UI that shows the reason why an SDC is not available in XB.”

Issue #3469684, image by me.

For more detail, join the #experience-builder Slack channel. Check out the pinned items at the top!

With DrupalCon Barcelona 2024 only two weeks later, the focus this week is on tying up loose ends. That already started last week, but of the milestone 0.1.0 priorities that product lead Lauri identified, 15 are still left after last week: we need to fix 1.5/day to get to zero.

Unfortunately, during the week, Lauri prioritized several more issues, so we ended this week with … 12 — only 3 fewer than we started with :/ That means we’ll need to land >2/day in the next week to get to zero. Fortunately, most of those twelve are already pretty far along.

Similar Posts