 I don't have any slides prepared. This is more of an informal sort of knowledge transfer, maybe I learned some stuff and I'll show you some stuff. And then definitely I'll just share the screen. Okay, cool. Let's go with this one. Is that visible? We have a Chrome. Yes. Cool, all right, so layout progress, what is it? What do I need it? If you're using, what's the built-in one? There's like a built-in sort of layouts thing. It uses blocks, it uses that side panel. It's ugly, it's terrible to use, it's hard to pick it. Not a great energy experience. It's kind of where layout paragraphs comes in. So I might just quickly whip around it. I've got some paragraph types set up and I've installed layout paragraphs and I've got a content type and on the content type is page manage fields. I have a field content, which is just a empty reference for paragraphs field. So if I go to manage form display underneath content, I'll just select the layout paragraphs and I've got some pretty basic settings here. I just want to show it as default and I want to require the things to put inside a layout. And then on display, I'm going to show content as layout paragraphs builder with the same settings. So it's default and require paragraphs to be displayed. So what does this look like? That, it's not very interesting. Doesn't do anything yet. Add section, can't add anything. So I'm going to go to structure paragraph types and I've got this little section paragraph type that's set up. You can just create whatever you want. Like a paragraph type could be called, you know, content aid. Doesn't have to have anything in it. So there's no fields in the end. Doesn't need any fields. Just under edit, we're going to enable layout paragraphs and we're going to choose one column and two column. You know, if you define layouts the same way you would throughout Drupal. I think you can do it inside your theme and your theme can add extra layouts. But that's that. So content, edit, add section. Now all of a sudden I have stuff to do. So I want a two column layout and I'm presented with a slightly broken layout but we'll ignore that now. Add some content and here's the rest of my paragraph types that sort of show up. Of course it's a live demo, it's nothing weird. So what I'll do is now we've got to that point. I'll get a working version. I'm just going to share a different. And hooray. So this is the exact same thing that's where we left off. I have a layout paragraph inside of this layout paragraph. I have some content types. You can kind of see it starts to really open up how this everything extra events work so I can drag and drop between different section. Put that up there. If I edit the meteor, it opens up in a little light box if it wasn't broken. There it goes. And that's kind of it. So that's layout paragraphs. The name is you to put paragraphs in layouts and you get a nice little editing experience. I mean, I don't want to drain on too much. That's kind of the knowledge transfer. It's worth having a go with. What else can I say? Like you show this to clients and they're kind of like, well, that's exactly what I want. There's a no code, low code sort of thing you can drag and drop, you can get your interfaces done and they don't have to know how Drupal works and they don't need to understand the terminology where a block is and they can just kind of see it on their screen. So when they go to add some content, that's all they see. It's a correct page. That's all they want to see. Keep it simple. All right, we're going to add one thing inside that. One thing I want in text. Sorry to keep you just being slow. And maybe we'll add another section underneath that. And then away you go. Yeah, I'll just leave it at that. Any questions? I don't want to go into a lot of detail about it. It's just sort of like, that's a cool thing. Install it, configure like two things that you can drag and drop your paragraphs around. So it will apply like as a custom module or have you contributed to it? No, this has been around for almost years, almost, just no one really uses it. It's just a slight alternative to layout builder. So instead of having to put blocks everywhere and define everything in blocks, and then you have to install third-party modules to lock down that sidebar. Then another third-party module that can lock down the configuration of it and another third-party module to open up which blocks are allowed to which people and which groups. The whole thing just becomes this giant mess. This is just paragraphs in a page. And the configuration that goes with paragraphs, so you select the bin and you give a layout and you decide what things can go in that bin. That's it. It kind of like, what it does is it adds what I kind of like about it. Is a section is just a paragraph as well. So a section is just inside your list of paragraphs inside that field. A section is a paragraph, it has an ID and the thing below it gets a behavioral setting that says the parent ID is this and the region is this. And that's all it is. So when it displays on screen, it's just rejigging the layout of it going, all right, well here's the layout sections and then find me the things that go in the regions and then, so when you're working with something like GraphQL or just an API, it's actually quite a flat structure and it's really easy to sort of understand and rebuild again in a headless state. What do you mean, do you have a look at it? Thanks for showing us those as I actually didn't know about this. I was wondering, I'm assuming it would work with like nested paragraphs and you had a paragraph. Yeah, so in that I've got an accordion example, I don't know, I'll just share it on screen at that point. This one, sure, let's see if it actually wants to play ball, but go add accordion that inside that I can add text. And then maybe I'll have inside that, yeah, maybe, yeah. So that's an accordion, so that's pretty much your paragraph with paragraphs inside paragraph. I think it starts to get weird when you use layout paragraph inside layout paragraph. I don't think it's designed to do that because then a layout is not a layout, but yeah. It might get pretty messy at that point. It could, yeah, but then when you start getting like inch dimensional paragraphs, things get weird anyway. So you're kind of just gonna have to play it safe usually or just make sure your theming engine or your templates can do the right thing. How does it work with revisions? Any idea? So it is just paragraphs under the hood. So paragraphs is empty reference revisions. So, yeah, it would work from revisions. It might get weird. I mean, the entire layout if we have, if we change and if we save, are we able to revert it to the previous one? If you change your layout in any system and it was mapped to regions, I think you're gonna have a bad time. So I don't know what they're there. I would assume if you were gonna change the regions and like what was in those layouts, you just create a new layer and you would have to make some sort of migration across, but you would have to do that with anything that used layouts. Yeah, if you're talking about just like the dragging and dropping of things, so like from one revision to another, this is here and that's there and that's all around. Then that information is just parent ID and that's coming from the behavioral settings which is almost like a third party settings on the entity. So, should be there, should be revisionable. Okay, let's go get it. Okay, get it. My question might show, I'm sure it shows my naivety in Drupal and it might be similar to what you just asked there, I may about revisions, but if I had like 100 page site, right? And it was constructed however it was constructed and then I started using this layout paragraph for my 100th and first page and 102nd page. Do those two new pages use this new editing experience and the legacy 100 pages, would they use layout builder or whatever the old method was or is it possible to sort of retrofit this experience into a site, I guess is what I'm trying to get at? Yeah, so if you used paragraphs for the original site build, so it was just standard paragraphs and you had the, you had all your components, you had text image, text image, text image, whatever and it was built inside paragraphs, then there's no reason you couldn't just turn on layout paragraphs and not select the check box that I did which is forcing things to be inside a layout and then you could progressively I guess enhance it that way, but if you're talking about like vanilla fields that need to be converted into paragraphs, then no, that wouldn't, you just have a new field that was for paragraphs layouts that you could continue to build underneath it and that's maybe where it differs to the core layout builder where you can turn that on per entity and then you can just start to mix and match where your fields are and mess around with it. So it's probably a design decision you'd wanna make early on if you were going to use paragraphs to build content or fields to build content. But I mean, there's no reason like, I worked on sites in the past where it's like, us girls should set a paragraph field underneath everything you start building components, it's just easier. So yeah, I mean, you can just do that. It's PHP, the world's end, you can do it everyone. Cool, thank you. Yeah, all righty, any more questions for us? Thanks a lot. I have a question for you. Who's gonna do a five minute presentation on CoolStar? Next one, next month. I was just actually chatting with Go-in, Go-in is also on the call, he joined up at Lake and what I was probably telling him to do is that we should probably do something about single directory components. That's the new up and shining thing. It has got a lot of traction specifically in DrupalCon Pittsburgh. Wait, before I do that, let's stop the recording.