| griffynh |
Whoops misssed this one! Griff, Aus :wave: |
| larowlan |
lee, Aus :kookaburra: |
| Kristen Pol (she/her) |
Kristen, California :wave: |
| kimb0 |
Kim, AU :wave::skin-tone-2: |
| guptahemant |
Hemant from India |
| DanielVeza |
Daniel :wave: |
| Akhil Bhandari |
:raised_hands: Akhil - Au |
| lendude |
Len, lurking |
| lauriii |
Lauri, Finland! :wave: |
| acbramley |
Kia ora :the_horns: Adam |
| brianperry |
Brian, following along from Chicago. |
| timbozeman |
Tim, California :wave: |
| Bálint Kléri |
Hello, Balint here from the Netherlands! :wave::skin-tone-2: |
| cellardoor |
Hi all - Chris in Seattle(ish) |
| wimleers (he/him) |
:wave: Wim, from Ghent :european_castle: |
| dharizza |
Hi! Dharizza, from Costa Rica :slightly_smiling_face: :wave: |
| penyaskito |
Christian, Andalusia, Spain, catching up, not much to report |
| larowlan |
I would be keen to have a sync call with @Jesse @wimleers (he/him) to talk about AST for #3453690: [META] Real-time preview: supporting back-end infrastructure |
| larowlan |
I think we probably need a sync call with @wimleers (he/him) @catch @gabesullice @effulgentsia myself and @lauriii to get some consensus on #3440578: [PP-2] JSON-based data storage proposal for component-based page building |
| lauriii |
I would be keen to have a sync call with @Jesse @wimleers (he/him) to talk about AST for [#3453690]I know Jesse is out until Tuesday and Wim will be out from Friday next week onwards. Maybe we could set this up between Tue and Thu next week? |
| larowlan |
Sounds good |
| timbozeman |
Can I come to the Real-time preview: supporting back-end infrastructure meeting please?I used HTML comments when making an in browser twig template editor and attributes when making LB+ and an inline editor Edit+. An AST sure sounds like a good idea! |
| lauriii |
@timbozeman it might be really hard to organize it at a time that works for you given that we already have folks joining from Europe and Australia |
| lauriii |
@timbozeman if you share your email in PM, I can add you to the invite |
| timbozeman |
Ah yeah. Timezones. No worries! |
| lauriii |
Invite sent! |
| lauriii |
I'm sure there's going to be notes we can share :slightly_smiling_face: |
| griffynh |
So a few things:I added a What have you been working on thread to clarify what is happening in the initiative?If people find it useful or are working on it regularly, it could be automated and posted daily.I added a Reminder to update the CK thread so that this becomes the main source of truth/where are we up to?Any other suggestions to clarify what’s happening and where people can jump in? |
| larowlan |
there's a slack bot for daily standup we could consider |
| Kristen Pol (she/her) |
I like both of these |
| Kristen Pol (she/her) |
And the thread on how to jump in as new person :heart_eyes: |
| Kristen Pol (she/her) |
Perhaps add blockers? Or is that covered and I missed? |
| Kristen Pol (she/her) |
Pretty standard in a standup |
| Kristen Pol (she/her) |
Could be tacked on“8️⃣ Weekly updates - What have you been working on? What’s up next? Need assistance with anything? Any blockers?” |
| griffynh |
Good thinking, I’ll add that |
| guptahemant |
Also maybe when we setup the standup bot, add a link to contrib kanban for easier track of the progress |
| cellardoor |
@larowlan is this the space we want to discuss the design system? I can take a first take at breaking the figma page apart into atomic components so we know what we'll need to start with |
| Kristen Pol (she/her) |
the official design system or demo? #3454125: Implement temporary design system for the DrupalCon Barcelona demo |
| cellardoor |
https://www.figma.com/design/aADVsc8fdsENnUaKePvVpg/Experience-Builder-D... this apart into the design system components (and atomic structure) so we can know what components we need to implement for the demo |
| cellardoor |
but more specifically the answer there is: yes? I think the demo should have a small design system to power it then we extend that out to have the built-in design system. That way we're not wasting any of the work done for the demo |
| Kristen Pol (she/her) |
please weigh in on that demo issue then if you would as that is a discussion point |
| cellardoor |
Must have missed your comments there - is the plan now for civictheme to be the design system for XB? |
| Kristen Pol (she/her) |
That is one proposal for the demo at least… the other proposal so far is perhaps building from scratch… feel free to chime in on that issue with thoughts :+1: |
| larowlan |
at the moment the component config entity is tightly bundled to an SDC but it feels like we need to support other things - like blocks (views, menus). Making this plugable could also mean a bridge for paragraphs users |
| larowlan |
it feels like there's a concept of a plugin in here, like we have for media-types + media sources |
| lauriii |
Yes, we definitely need to support other types of components too. Blocks and Layouts (besides SDCs) are the two examples I have in mind we'd probably support from the get go. |
| lauriii |
@larowlan Would you like to file an issue for this? |
| lauriii |
Just saw that @Pierre (pdureau) was coming to a similar conclusion in #3454173: Media Library integration (includes introducing a new main content renderer/`_wrapper_format`)#comment-15637780 :slightly_smiling_face: |
| wimleers (he/him) |
Yes, we’ll need all that. We needed to start somewhere though, hence currently 1:1 tied to SDCs. |
| wimleers (he/him) |
This seems like a naming challenge, @lauriii? What would be the umbrella term for:SDCsblockslayouts… more things still? |
| Pierre (pdureau) |
What would be the umbrella term?Renderables? |
| wimleers (he/him) |
"Developer-created components": mark which SDCs should be exposed in XB was but a tiny stepping stone, and the next step is Allow specifying default props values when opting an SDC in for XB, to ensure that when a user drags an SDC onto the canvas, it’s guaranteed to be visible (example values in SDCs are optional) and we’d already know which field type + widget to use. |
| wimleers (he/him) |
Renderables?Keep the ideas coming :nerd_face: |
| wimleers (he/him) |
What would the end-user facing term be? Or perhaps we’d just surface these as what they are to the end user: “components”, “blocks”, etc? |
| Kristen Pol (she/her) |
Thingamajigs |
| lauriii |
@wimleers (he/him) XBC? PBC? :joy: (only half-joking) |
| Kristen Pol (she/her) |
Experiencibles :laughing: |
| larowlan |
Components |
| Kristen Pol (she/her) |
I like that myself as it’s generic enough to cover “all the things”… other than SDCs, are we using any “components” terminology in the codebase currently? Away from computer so hard to check |
| larowlan |
#3454519: [META] Support component types other than SDC, block, and code components |
griffynh, larowlan, smustgrave, Kristen Pol, Bálint Kléri, guptahemant, lauriii, Wim Leers, acbramley, timbozeman, DanielVeza, cellardoor, Pierre (pdureau)
Comments
Comment #11
griffynh commentedComment #14
griffynh commentedComment #16
griffynh commentedComment #17
griffynh commentedComment #18
larowlanComment #19
smustgrave commented