Closed (fixed)
Project:
Experience Builder
Component:
Meetings
Priority:
Normal
Category:
Plan
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
28 Jun 2024 at 04:57 UTC
Updated:
26 Jul 2024 at 17:19 UTC
Jump to comment: Most recent
:wave: Hi, and welcome to the weekly meeting of the Experience Builder initiative. :tada:
0️⃣ Who is here today? Comment in the thread to introduce yourself. We’ll keep the meeting open for 24 hours for all time zones.
| larowlan | hey :wave: |
| kimb0 | Kim :wave::skin-tone-2: |
| griffynh | Griff :blob_wave: Aus |
| pavlosdan | Pavlos :blob_wave: Cad |
| acbramley | Adam :the_horns: |
| Christy Clonts | Christy :blob_wave: |
| lauriii | Hello everyone :wave: |
| guptahemant | Hi everyone |
| finnsky | Ivan! :hand: |
| timbozeman | Hiya :wave: |
| Kristen Pol (she/her) | Kristen, one bar of cell reception from near Crater Lake, Oregon :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.
| guptahemant | Hi @lauriii would love to know your thoughts around #3454125: Implement temporary design system for the DrupalCon Barcelona demo#comment-15658577Posting a summary of resources here for a quick reviewDemo link: https://demo.spacedxp.comOfficial links (from Here):Main site: https://spacedxp.comDesign system: http://space-design-system.qed42.netFigma: https://www.figma.com/design/bAnd87KYw7YASCry80QOaY/SPACE-DS-%E2%80%93%C... Access: https://space-drupalconlille.qed42.net |
2️⃣ Subtopic 1: Theme builder
| Purencool | I can't seem to find any documentation on this subject. |
3️⃣ Subtopic 2: Page builder frontend
| Christy Clonts | Just watched the Experience Builder Starshot session, very exciting stuff! Have we thought about having a feature where content editors can save a section or page as a template to easily re-use? As a content editor I have found this module that saves me SO much time on configuring the styles on sections and blocks, giving me a quick starting point to work with. Also this content admin-created "templates" type feature is available on Acquia Site Studio and some other CMS's. |
| pavlosdan | Yeah this would be a great feature to provide starting points for various layouts that could help content authors.... layout recipes? :wink: |
| Christy Clonts | Here's a quick screen recording of how the module works on one of our sites |
| pavlosdan | Another nice feature that both paragraphs and Site Studio have is the ability to re-use components across pages but updating it once updates the component everywhere it is used. |
| Christy Clonts | Yes! Having the option to either make it a global component or a "detached" version where it only updates on that one page would be very cool |
| lauriii | @Christy Clonts Saving section and page templates is part of the roadmap and we are currently even targeting some of that for the Barcelona demo, meaning it should shape up pretty early on :slightly_smiling_face: |
| Kristen Pol (she/her) | I love being able to reuse configured content components between pages and have built that support in design systems before so that great to hear :heart_eyes: |
4️⃣ Subtopic 3: Data model/persistence layer
5️⃣ I’m not sure where to start, but I want to contribute to Experience Builder.
| pavlosdan | Would love to help but have no idea where or what could be a good starting point to get up to speed and where I could be helping. |
| griffynh | Hey, what’s your skillset? What are you interested? That’ll help to point you in the right direction. |
| pavlosdan | backend coding mostly. FE skills could leave a lot to be desired :slightly_smiling_face: |
| griffynh | Here’s the backend meta ticket: [#3450586]Maybe read through that and see if anything takes your fancy?It should give you a good overview of the backend direction and what needs help. |
| pavlosdan | sounds good! thanks @griffynh |
| griffynh | If anyone else is interested, here’s the FE version of that ticket: #3450592: [META] Front-end Kanban issue tracker |
| Sagar Chauhan | Hello, apart from the last meetup recording on Experience builder, do we have any other resources to get started on contributing. I am basically looking forward to FE contribution. |
| griffynh | Hey Sagar, the link above should help give you an overview of the frontend work required for Experience Builder.Shout if there’s anything in there that interests you and then we can go from there. |
| Christy Clonts | I would love to contribute! I am a UX/UI designer that also jumps into to help with content entry quite a bit at my agency, so very familiar with the Drupal CMS. I have filled out the Starshot UX form and joined the UX channel here :slightly_smiling_face: |
6️⃣ Wins - what wins have you had since the last meeting? Share your successes!
| larowlan | I think some of the bigger pieces in terms of API feel like they're starting to form after work in MR 68 |
| kimb0 | Looks great. |
7️⃣ Are any sync meetings required this week?
| lauriii | Lot's of sync meetings happening in person at Dev Days |
| lauriii | I haven't been able to catch up on the AST stuff but would be good to discuss that at some point |
8️⃣ Weekly updates - What have you been working on? What’s up next? Need assistance with anything? Any blockers?
| lauriii | I was on a core committer onsite for Mon - Tue and currently at Dev Days so I'm prioritizing collaboration with folks who are at the event. Yesterday I had a long discussion with catch, alexpott and longwave about #3440578: [PP-2] JSON-based data storage proposal for component-based page building and within that group we agreed that the current path seems like the right choice at the moment. It's something we'd have to revisit once we have a better sense on the UX and have done some user testing on it. |
| larowlan | Ok thanks |
| Kristen Pol (she/her) | Reviewed Lauri’s feedback on the demo samples provided and passed along to the CivicTheme designer. Looks like things are leaning towards using QED42’s internal Space design system for the demo? I’ll still follow up with our designer once I have better internet tomorrow night (edited) |
1️⃣.1️⃣ @larowlan “Supporting other component types (Blocks, layouts) and storage models (legacy LB and PG).”
| larowlan | See https://git.drupalcode.org/project/experience_builder/-/merge_requests/68 |
| larowlan | and this thread https://drupal.slack.com/archives/C072JMEPUS1/p1719292181635789 |
| larowlan | Big description in the MR: |
| larowlan | What this unblocksAdds support for blocks.Decouples from SDCAdds roadmap for theme builder support.Adds roadmap for layout builder and paragraphs legacy support in place.DetailsAdds two new plugin types as follows:Component Source pluginComponent Tree Storage pluginComponent source pluginThis decouples the component config entity and component tree from SDC components. There's a SingleDirectoryComponent implementation that all the existing logic moves to Adds two additional implementations as follows:Blocks - this will support blocks (e.g. views, menus) as well as a bridge to layout builderLayout (via submodule) - this will support layouts for a bridge to layout builderPaves the way for:Theme builder component - we can create a content-entity here (e.g with fields js, css, twig, props, slots) and build components from the DB based on thatParagraphs support - could be in contrib or a sub-moduleComponent tree storage pluginDecouples the component tree loading from the component tree field. There's an implementation for ComponentTreeFieldItem that holds the existing logic Starts to scaffold a layout builder version in a sub-module that in could possible be a BC layer for layout builder (I'll keep going on this). Adds value objects for component tree instead of array PIs Also opens door to:storage of default values (e.g. equivalent to LB defaults).additional view modes in separate fields (something LB can't do)paragraphs support for legacy |
| sime | > Adds support for blocks.Is that in the sense that it adds "better support for entities" or is it "bridges some gaps we have supporting blocks because blocks are a bit weird, historic reasons" (edited) |
| sime | Oh it's block plugins not block content isn't it |
| sime | Actually you can ignore me, I'm just parsing. |
| larowlan | yeah we know we need to support menus, views in XB - block plugins |
| lauriii | Thanks for working on this @larowlan! :clap: Wim is out at the moment but he'll be back in a week but reviews from others could be helpful in the meanwhile |
| larowlan | No worries, I knew he was off |
| larowlan | Will try and get LB and theme builder support done by end of next week when he's back, to demonstrate how it might work |
1️⃣2️⃣ At what point do we start using core quality gates for MRs. There's been a few things merged that I wasn't sure about.
| acbramley | Interested in this too, seen some very WIP looking code that has been merged already, while MRs from other people are being churned :thinking_face: |
| lauriii | At the moment, I think we should apply code quality gates only against changes that are being made against core (e.g. SDC improvements). On the contrib module, we want to remain pragmatic to enable fast progress. If there are things that could be improved, we should open additional issues where we can work on those improvements. |
| lauriii | @acbramley Are there specific issues that are being held up by feedback? I'd be happy to try to unblock |
| acbramley | I agree with the fast progress bit, the part I'm struggling with is - Where is the line of having enough community engagement/review on things that this isn't just being built by a select few people? What happens when it needs to be merged into core? When do the larger, more strict reviews happen? It just makes me a bit uneasy at the moment |
| lauriii | Reviews are welcome at any point – it's mainly that in order to make fast progress, the team is not blocking progress on that. We know that we want to get some of the foundations from XB to core eventually but there's no need to merge Experience Builder as a whole to core. It can be shipped within Starshot and Project Browser. At the moment, we should prioritize feedback related to UX and architecture to make sure we get those aspects right. We accept MRs for other types of improvements :slightly_smiling_face: |
| lauriii | If there are any issues that in your opinion need more scrutiny, calling that out could be helpful |
| acbramley | Hmm I didn't realise the plan was to leave this in contrib... That's certainly not the impression I got from anything thus far. The hard thing with reviews are getting in before they're merged I think lol... Timezones make that tricky and also being time poor. |
| lauriii | Hmm I didn't realise the plan was to leave this in contrib... That's certainly not the impression I got from anything thus far.Parts of XB might be moved to core eventually but there might be parts that never move to core. The current expectation from me is that we will have a stable release within contrib and when we have validated the solution, we could consider moving it to core. |
| lauriii | > The hard thing with reviews are getting in before they're merged I think lol... Timezones make that tricky and also being time poor.It's okay to open small issues (potentially even with MRs) to improve things after the fact :slightly_smiling_face: |
Participants:
guptahemant, Purencool, Christy Clonts, pavlosdan, lauriii, Kristen Pol, griffynh, Sagar Chauhan, larowlan, kim.pepper, sime, acbramley
Comments
Comment #12
griffynh commentedComment #14
griffynh commentedComment #15
wim leers