:wave: Hello everyone, welcome to the fortnightly (morning) meeting of the Experience Builder initiative.

0️⃣ Who’s here today (edited) 

lauriii I'm here'ish :wave: trying to multitask
penyaskito :wave::skin-tone-4:
larowlan hey
Libbna hello :wave:

1️⃣ Do you have suggested topics you are looking to discuss? Post in this thread, and we’ll open threads for them as appropriate. (edited) 

lauriii AI is probably a new topic we should include on a recurring basis. XB now has an AI component which is a core part of XB.
smustgrave @griffynh want to add that to our list @lauriii sorry didn’t see this in time to add 2.5 so added as 9
lauriii No worries! Thank you!
griffynh Can do, thanks for the heads up.

2️⃣ 1️⃣ Subtopic 1: Theme builder

lauriii The CLI tool for managing code components outside of the code editor is nearing completion[#3525571]

2️⃣  2️⃣ Subtopic 2: Page builder

2️⃣ 3️⃣ Subtopic 3: Data model/persistence layer

smustgrave From previous meetin[#3520449]#beta
smustgrave See ONLY 2 are ope[#3532712]
penyaskito First one is postponed on XB requiring 11.2.x, which won't happen before mid-july-ish, so won't be in beta I guess.Second one was raised yesterday. Not aware of any bugs this could be causing, but better safe than sorry. In any case don't think it will happen before beta neither.
larowlan We landed a major change to how we store entities in auto-save this week, We're now storing entity objects and not the client-side model. This means the system is more reliable w.r.t detecting changes and opens the door to look at using workspaces
catch How does storing entity objects work with incomplete entity data? E.g. if required fields aren't filled out yet.
larowlan Stored normalised in temp store
larowlan Could only use workspaces once they were valid
catch So just completely skipping validation? I guess the choice is between the entity data and client side model because no fapi data to use which would be the autosave contrib module approach.
catch Unvalidated entity data is probably closest to that then.
larowlan It does validation on publish. Fapi validation violations are stored until then
larowlan And entity validation obviously
catch Publish always happens after the entity is reloaded into the form and then from there? Or can it be direct from autosave?
penyaskito is always from auto-save
catch So if you're editing and immediately hit save, it will go UI -> autosave -> entity save. hmm OK.
penyaskito yes. Technically there is no "save", is the publish on the top right that only sends the ids + hashes, and that only interacts with auto-save (temp keystore) (edited)
penyaskito (I think we also send timestamps? not sure anymore)

2️⃣ 4️⃣ Subtopic 4: Layout Builder and Paragraphs

smustgrave Don’t judge I’m about to transition a new client from panels to layout builder with XB in mind so very interested in this
catch https://www.drupal.org/project/experience_builder/issues/3454519 and the child issues are the ones to watch afaik.
larowlan Dan has been chasing HEAD with the LB source plugin. Things moving so fast his working code keeps getting broken. He's juggling it with client work and is close to having an MR

3️⃣ I’m not sure where to start, but I want to contribute to Experience Builder.

smustgrave Here are all the XB issues tagged with ‘Novice’ - https://www.drupal.org/project/issues/search/experience_builder?project_issue_follow[…]Open&priorities%5B%5D=200&issue_tags_op=%3D&issue_tags=Novice

4️⃣ Wins - What wins have you had since the last meeting? Share your successes!

penyaskito Permissions META almost complete[#3516602](edited)

5️⃣ Are any sync meetings required this week?

6️⃣ Weekly updates - What have you been working on? What’s up next? Need assistance with anything? Any blockers?

7️⃣ Review previous meeting minutes

smustgrave Close[#3529698]

8️⃣ Any updates on our next major milestone?

smustgrave Here’s the current 1.0 meta:#3515932: Milestone 1.0.0-beta1: Enable creation of non-throwaway sites
lauriii This is probably the most accurate list of beta blockers https://www.drupal.org/project/issues/search/experience_builder?text=&assigned=&subm[…]=&status%5B%5D=Open&issue_tags_op=%3D&issue_tags=beta+blocker
lauriii beta is targeted for July

9️⃣ From @lauriii AI component of XB

lauriii The AI team is currently focused on two tasks:Allowing AI to generate and refine componentsAllowing AI to generate and refine pagesMeta issue can be found here[#3530701] (edited)
lauriii @timplunkett (he/him) Any updates you'd like to give?
smustgrave My question around the AI, love the idea and the demo on Atlanta was awesome.  But with more AI stuff appearing, some people publishing full modules that has caused a number of threads in various channels.  Is there any concern here? Know it’s a fluid situation because there’s no official governance around AI use
lauriii We're trying to be on the right side of this and build something that we believe is responsible and is going to help our users. XB is particularly well aligned with this because it provides a "sandbox" outside of the production site, allowing the AI to make changes that the user need to review before publishing.
lauriii We're also adding tools that allow us to optimize for higher quality outputs. For example:#3532296: Visual Review and Iteration agent on created components
smustgrave Cool! Not against or trying to rain on the idea just have seen a lot of very recent discussion around the topic
lauriii I believe that the AI generation of modules and libraries is something that will continue to remain polarizing because of the accountability model where the person downloading the module will be accountable for the results that the module provides. The difference between the AI for XB is that the user generating the content, would be accountable for what they have generated. (edited)
smustgrave That’s a very good distinction!

Participants:

lauriii, smustgrave, griffynh, penyaskito, larowlan, catch

Comments

smustgrave created an issue. See original summary.

griffynh credited catch.

griffynh credited larowlan.

griffynh credited lauriii.

griffynh credited penyaskito.

griffynh’s picture

griffynh commented
griffynh’s picture

griffynh commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.