 All right, I think we can start. This session is about the possibilities of a layout builder, mainly for site builders and content editors. And we recently added a little part about content staging as well. Who are we? My name is Wesley. I'm an enterprise architect at Dropsolids. It's a company from Belgium. And I am from Belgium as well. And I'm Frédéric Bouters. I'm also an enterprise architect at Dropsolids. And I have a small request before we start, because it's our first time that we present in the United States. Actually, also my first time just in the States to Kour. So if it's OK, we'd like to take a selfie. Just the two of us and you in the background. Thank you so much. OK, how does that feel? You moved after eating? That's good. OK, thank you. We're for Dropsolids. We work for Dropsolids. And Dropsolids is a company based in Europe. It's a fairly young company, eight years old. And we have around 80, I think now almost 100 people that are from multiple countries in Europe. We have partners in multiple countries and multiple continents and are growing fast. We also are going to talk about the layout builder we did some research on it and improvements on it. We created our own install profile. And we're going to show all that. We also do contributions. We have a lot of modules that people at Dropsolids work on, projects that we support. And we also sponsor DrupalCon in Europe mostly, and events like the Dev Days. Dropsolids is a company focuses on the digital experience platform, which means that it's a combination of Drupal with Apache Unomi, a CDP, and Mardic as a marketing automation platform. If you're interested in more on personalization or marketing automation with Drupal, talk to me after the presentation. Dropsolid also does more than personalization. We also do the optimization. For example, SEO. We also do development or design or strategy. And we all try to do that in an open, sustainable way. But we're going to talk about Layout Builder. And if you're going to talk about the future, you can't talk about the future without looking at the past. So yeah, we'll start with some history about content editing. That's mainly search field, paragraph, WordPress style, quick edit. And then finally, where we are at now, that's being a Layout Builder. Maybe this slide will give you some context. So Drupal 1 is all the way in 2001. If I'm correct, yeah. And that's before things like WordPress, but also before things like HTML5 or Composer, or maybe you can edit it. Facebook, as you see, and WordPress. So it's an old project already. But the things that I want to show with this slide, actually, this is a slide that Dries presented at another Drupalcon. But I added the Drupal version on top. Why did I do that? Because it shows you that it's not a new thing where everybody jumps on it. No, it's already a proven thing where all the good stuff has stayed and all the extras got removed. So we're doing the good sauce, not just something that we just invented. OK, structured fields, first one. I'm sure all of you are familiar with structured field because it's still in Drupal, as of now, and then a couple of other CMSs as well. So we have a content type. This one is the event content type. It has a title field, as it has a description field. Maybe some custom fields and for an event a date field would also be quite useful. It's still what we use today, and it's still a very good basic and a very good way of having structured data on your content. But then we improved. We did structure content for quite a while, actually. But then we improved to some more like WordPress style inline editing. Yeah, and this is actually for most editors like the wet dream of content editing. They just want to go wild, inline, edit, everything. But that doesn't fit with Drupal very good because you have things like moderation and multilinguality and you want to reuse structured content inside this rich editing experience. So there's some things that are hard to combine. We have a small demo on how it looks. The Gutenberg, which was one of the popular ways to do inline editing in Drupal. Actually, actually close it. I'm sorry. And it's really nice way to editing. You all know it because Medium also works like that. You can just click on that text and start editing. Editors love this kind of thing. So if we could combine this with structured content editing in Drupal, then we have the best of both worlds. And that's actually where content editors want to go. The problem with this is, as we showed in the presentation, yeah, it's very hard to combine this with structured content. This is all this thing is just editing HTML and saving it into one field, which is not a very structured or sustainable way of doing things. OK, good. So yeah, that's everything Fritig already told us. So things that are hard with this are things like moderation workflow, multilingual stuff, reuse of content is also not very easy. And the actual unstructured type of thing, it can be used. And it is used. We just checked that it has about 3,000 uses on Drupal.org at the moment. But it's mostly used for block style websites. Then we have what we call old school dynamic. And old school dynamic, what we mean by that is basically paragraphs. I'm sure, pretty sure everybody has used paragraphs. Maybe show of hands. Anybody? Great. But then you'll know what we're talking about. Most companies and most Drupal companies have been using paragraphs for quite some time. I think at Dropsolid, we've done this for, I don't know, five years, maybe something like that. And this very long list, which is not readable at all. It doesn't really matter. It's the very long list of paragraph types that we provide in our install profile, or that we did provide to have our clients or content editors who are working at our clients built their pages. Don't think we needed to do a demo of that. Everybody knows it, so you know how it looks. Then there was a new thing, sort of a new thing. It was about around the same time. It was called Quikated, and it allowed for inline editing. And I'm sure all of you already know what Quikated is. It just allowed you to just, in the front end, just click on a piece of content and then do very simple edits on it, like change the text or add some markup to it. But as some of you may know already, this is going to be out of core again, or it's already out of core again. It's going to be out of core in Drupal 10, if I'm correct. Sorry. So then we come to a new style, being Layout Builder. So what's the difference here? So we still have the structure and the metadata. I didn't really mention it before, but on all the other stuff, there was still the structured data fields that we have in the yellow color. But on top of that, instead of using paragraphs, we now have sections. And each section could be something like a header or your content or a footer or whichever you want. And under each section, there is a block. And in a more visual way, that looks like this. So where you would have paragraphs, it would all be just be under each other. And then some people would do sub-paragraphs or embedding paragraphs and other paragraphs to get the same. But this is more what was the point of Layout Builder, to have these sections that could have columns. And you could put one or more. And this also allows you to combine more. So one section is one division. And you could combine any type of block in this section. So as an editor, you can combine all kinds of blocks for that to be able to do that with paragraphs. You need to create a gazillion amount of paragraphs. So this is already how this works. So when you add a section, you can select how many columns you want on it. And then this is a little bit of our preview of our demo. Then you can add some blocks to it as well. That does come with some confusion. Mainly, we used to have just blocks in Drupal. And that was very clear. The blocks were not for content editors. But they were very reusable. But then along the way and along all the Drupal versions, more and more of them became for the content editors. And then now we have inline blocks, which are part of Layout Builder. They are not really reusable. Or that's not how we use them in Layout Builder. And they are just part of the content. So that can be a little bit confusing. But the difference is mainly the context. So if you add a block in your block overview and you add it to your header, then it's on every page. Or if you limit the visibility, then that won't be. And the inline blocks, they are used for Layout Builder. And they are only visible on the page that you added that specific. No worries, we're going to show it. Definitely. Layout Builder Core, that's about how it looks. Yeah, I do have some issues with that. So maybe some of you already tried it out. And I also tried it out. And I didn't find my way in there. So here you see we installed a clean Drupal 9. And if you would ask like a child, I have a boy of nine years old. If I would ask him, can you add an image to this page? It's nearly impossible. So they would find maybe the add block button. And then they would see on the right side. And if you have somewhere a field that's called an image field, they would click it. But it wouldn't work because it's not on a content type. And they would like scratch their head and like, how do I add an image to this thing? And then maybe they would add custom block, like OK, create a custom block. And then they would find there is an image in this HTML thing. But this is not how you want to work with this, right? So out of core, the experience isn't really very great. And this is something that we improved on quite a lot. What they did do very well is they provided the API, the underlying structure for other systems to build upon. And as you see here, there's layout builder in core. They have the system, the API. And there's bootstrap layout builder. There's layout paragraphs, layout components, and our distribution rocket ship. And so there's multiple ways to go interact with these layouts in Drupal core, which I think is a very good idea. It's a bit like Search API or other API modules that are in there. So we're using the layout builder API to make these pages really, really nice. And other modules do this as well. As you see, there was already a session yesterday about layout paragraphs. They are also using it very nicely. But the only thing is they are very dependent on paragraphs only, and they're not really using the layout builder API, which we do in our distribution much more. It's a different way of going at it. There's also layout components, which is a different module to tackle the same problem. There's also bootstrap layout builder by the guys from ImageXMedia, also a very nice module. They are working really hard on it, so certainly check it out as well. And as it goes with standards, how standards proliferate situations, there are three or four competing layout builder implementations. How ridiculous. Let's build our own. So that's what we did. Of course, we didn't just build it. Luckily, we have someone that did some UX research. She's called Ines. She had also a talk in another DrupalCon. And she did some research on, like, she just put someone in a chair, like, try this. She wrote it down. We improved on it. And this way, we improved the experience quite a lot. Our distribution is called Rocketship. So it's called Dropsalt Rocketship. You can check it out. But don't go too fast. Don't do it just yet on your computer. Because in the end, there will be a link. And you can try it out. We have an online version, so you can just log in, create an account, and try some stuff. So you don't need to try it out, or check it out, and stuff. It's really easy. You'll see. OK, and this is the moment. This is the moment. I'll just go to the next slide. I love the enthusiasm. All right, thank you. So yeah, we'll do a little demo. The desk is a little bit low, so I'll do my best. Let me know if I'm not speaking in the mic anymore. So I already forgot something. It says over here, sales pitch. And the reason why it says sales pitch is not because I want to sell something to you guys. It's because this is how a Dropsalt, part of my job is to go to clients, and this is how I sell them RCMS, being Drupal, obviously. So that's really how I'm going to try to do this demo, not to sell it to you guys, but how I would sell it to our clients. And in order to do that, usually I just pick a page on their current website. Most companies already have a current website. So I picked the one on the site of this event, being the plan your trip of DrupalCon. It's right over here, this one. And I'm going to rebuild it. And the goal is to build something like this. This isn't really a demo then, because I already did it. But I'll go back to my revisions, and hopefully everything works. And I can revert to that one. So here, I just added all the content already. I'll show a bit more, but this is just the plain content that I copied from the original website. And just to let you know, this is just a page. If I would make it, I would just. Small intervention. As you see here, he clicked the great page, and you are now editing the structured metadata, which is like the standard edit way of editing content, where there's that structured field. So it's not the layout that we're editing here. When you're done that. Yeah, so I would just start with creating a page. If I want to create that page, then we indeed have the destruction of metadata over here. And I don't know if you can see that there. There in the bottom, it's the edit page. And then we have the. Yeah, so sorry, a small intervention again. What we also did is we install a module that changes the edit link on content types. So it will be structure and metadata. And the edit, the managed content is actually what's in the standard installation layout. So this is a module that we also linked it in the presentation. You can find it later just for the confused people. Structure and metadata is an edit with the structured fields. And managed content is a layout. Sorry. No, it works. So like I showed in the slides, we can add a section. I'll just go for a single column one. After that, we'll add a block. You can see the layout is also quite a bit different here. Maybe you can say something about that. But that's just UI changes. These are all contributed modules, some of which we wrote, some of which already exist. So we can just add some text to it. That's this one. I have a request. The nine-year-old in me would like to add an image as well. So if you could keep that in mind. I'll add an image. So I'll switch to the page I already created. What we did here is just custom block types, which just fields like in paragraphs. But they just build as custom blocks. So we added some extra things like a button here. And then we had a link to it. And then usually, that should be something else. I know it should be on the original page. Like the link to the Hilton. And then we already have that. And then in order to avoid that, I have to create all these contents. Again, that's the reason why I prepared it. So you can see it over here. What I'll do now is just show you how I created that page. Or that same page. But that looks a little bit better. Hopefully a little bit better than the page that we have on the original website. So it's just very easy drag and drop. This thing alone, if you show this to your clients, that you can drag and drop things around. Well, really, especially for clients who have used Drupal before, that will really amaze them. They will be like, oh, it's really visual. Also have made a little change here. And this is just a checkbox. But you can just go from show preview with editability to preview only or to editability only. And that's useful for large images if you want to move them around, especially. Yeah, this shows you the structure of what's all in the page. And this allows you to drag and drop it easily. Because sometimes you want to add full page with things. And it's hard to drag them around. So when you then switch to editability or the structured way, then you can easily drag and drop those around. So if I remember correctly, I then added a single column one. I'll move that over here. This one over here. See, this is where the difficulty becomes. Because my screen is a bit smaller, resolution a bit smaller. So then you can easily switch to the editability one. And then move it over here, which to preview again. So that works easy. Let's add another one, another section. Hey, I can't talk. No worries. Don't forget my image. Oh yeah, I forgot your image. Sorry about that. I'll add an image. I'll remove an image, and then I'll add it again. Because I already prepared it. Yeah, sorry about that. Or no, I'll add a new image. I'll add an image of Portland. Let's do that first. Thank you. So I'll add an image. I have an image of Portland somewhere over here. So obviously it works with Media Library as well. Just a second here. Maybe when you go back, what you see here, when he clicks the Add Block button, there is a list of blocks. And here, as an editor, I see that there are, and these are inline blocks. This is like a dropdown with all the inline block types that we created. You could look at them as like the paragraphs only. These are blocks that are in a section. This is like an important thing to understand. But as you see, there's also custom blocks. You could create your own blocks. And we filter down the amount of blocks that editors can see, because we're logged in as an editor in this site here. But when you log in with higher permissions, you see all the blocks that your system has. And you can also use them in this nice layout. So this allows you to really use the structured content with the drag and drop way inside your pages, which I personally think is mind blowing. Because this is actually the marriage of the structured content and the inline editing, which makes me emotional. So at the request of Friddick, we'll add an image. And I looked for a nice image of Portland, this one over here, actually. What we did is adding some modules to it that allow you to change the layout of your block as well. So here, we have the normal layout, or we can do it stretched. And then we can also manipulate the image format. I think this one might work for this image. This is like the stretched one, where it's hard to drag and drop it. But then you switch to the structure of you so you can easily drag it around, which is editors like this kind of stuff. Also important to note, we're just using some styling. And nothing in Drupal changes. You can just style it how you want, make the images slide in, or do whatever CSS effects that you want. I'm not a big fan of CSS. But if you want to do that, it's combined very nicely. That's just a Drupal way of doing things. Also, it's just blocks. You can do everything to them. What you could do to block before. I did that thing again. Where I accidentally clicked on the back button, and now I lost all my changes. Yeah, that's amazing. But it's all saved. Yeah, that's cool. And I didn't really plan for that, but it is cool. This is also in Drupal Core, by the way. It's not something custom. Quickly check it before you publish it. So now what we did is just add some structure to it. I mean, not really structure. Structure is a bad word here. But add some layout, like edit the columns, then all the columns. So it's just a bit more readable. Obviously, if you want to show this to your client, show them as well that this is responsive, that if you show it on a smaller screen, that it will work. I have a request. Could you change the background in one of these blocks? Because I think the color combinations are a little bit off. Could you do that? Most definitely. Editors tend to ask these kind of things. And what I did now is just change the background. But it's not changing the background. It's, again, one of those layout things that we changed. And it's just added a, from a front end, part of you, it's just adding a CSS class. It's nothing more than adding a CSS class. But that CSS class changed the background to blue. And then it also changed the font color to white. Yes, and just for the more technical people, this is also configurable. So in the back end of the site, there's a settings field where you could create multiple types of settings where you can link them to classes. And then in your styling, you can link those classes to whatever teaming that you want. So just as you see the list here with the predefined background colors, this is for developers. You can do with it what you want. Yeah, and also an important part here is I just changed this one to gray because our header is also gray. And the reason why I did it is because I can change that header over here. And that's what I'll do. I do not want it to be a gray background this one. So it's a bit more clear. But the important part here, I cannot remove it. And that's also something with some extra modules you can do, like lock some of these sections down, then add them to your template and making sure that you have that header on every page that has your title and stuff like that, but you cannot remove it or not as a whichever role you have, but some roles will be able to changes and other ones won't. So here you cannot add an extra block but you can edit this block. Maybe at the easier here. So I can edit this block and it's changed, obviously, but I cannot remove it or move it to somewhere lower. So that's because you're an editor. As an administrator, you can change the structure of the page and change all the blocks in the structure of them. I have another request. Could you create a template or a section that you can then reuse on multiple? Yeah. Things of them. So I've created a structure for one page and I want it to be used on all pages or for an event kind of page and I want to reuse it for all events. Could you do that? Yeah, definitely. And that's also an important part that you can give your content creators much more power because we have this very easy button here, just add to library and then I give it a label, just a random label I did now and then if I want to reuse it, add a section, yeah, clicked on the wrong button. Import from library. So here's my new section that I just created and this just makes a copy. I mean, it's still inline blocks. They're not linked to each other but it allows your content editors to create stuff that they want to reuse by themselves and they don't have to always send an email to support. I want this kind of type and I have to use it on 20 pages and this way works very easy. So now you showed it out to use it in the library and reuse it in another page but how would you do that for a content type? Can you show where the interface is, where they can do that for a content type? Yeah, definitely. If I'm logged in, yeah. Ah, yeah. Let me copy my URL here. Probably locked in my other browser. So as an administrator, if you will go manage the page display, there you will find in the bottom the managed layout of this content type where you can then do the same kind of editing here if you would click on this page. It looks exactly the same as you would edit another page. The only difference is that you will then create an entire layout with images or whatever that will be copied for every new type of content from this content type and the moment an editor starts working on this page and rearranging blocks and changing everything, they create like, how do you, I would call it like a branch or like a separate version. Only thing is from then on it changes and it will not have the changes that happen on the content type sections and so I hope you understand that. And it's a nice way to provision pages or events or with like a basic layout and give them a nice visual feel. Yeah, the important thing to understand here is that what you do as an admin then that gets used as the base, oh sorry about it, as the base template but obviously every time you save something in Layout Builder, you're overwriting that thing. So if you then change the original one then obviously that won't have any effect and shouldn't have any effect on the existing pages only on the new ones. So I think from a demo's perspective I'll just hit save here. It looks much nicer now. Yeah, I'll just say it. Thank you. So it's about almost what I did in the other one. I think that concludes the first demo. Yeah, so maybe also interesting to notice all things that you knew apply as a workflow or anything that applied to notes still applies. Yeah, if you do it on the template, for the template library you can just upload an icon and it's saved like that and for the ones that are default block types I think that's a separate module, not entirely sure. I mean, we worked at this install profile with the entire company so I don't know every detail but definitely it's open source so you can look it up and if you don't find it, try and find me and I'll try and get in contact with the person who did this. Yes, so I have now an existential question because I've seen that you could create multiple types of libraries or sections or divisions on how to manage your content. If you then only have a content type page couldn't you then make any website with only pages? Do we still need content types actually? Yeah, well, we'll do that in another demo. So I want to just claim the term content type-less here. No, it's a joke because I think content types are still important but... We just invented that like an hour ago but it's okay. So what I did here, I have another demo environment here and I just created a team page, very easy team page. So first section with the two column and then this is actually not a four column but a one column which has a content block in it and that block is actually sort of a view type of thing and if you get... It's just entity reference. So I added some entity references here as well. So Fredrick is in here and some other people from our company are in here as well. So what I'll do now, I'll add a new page. So like I said, only one content type. That Nick because he's right here. He's our biggest fan. Was. Yeah, normally I'll write his title here but now I'll just write used to be CTO. And we'll add just an image. This is like from the slide in the very beginning structure fields. And then this will save that one. We have an empty page now, we'll leave it at that. What I can do here is just go back to my managed contents, edit this block at Nick. We'll let Nick for the very last time all the way to the top of the company. He's always, you know, he inspired a lot of this, by the way. Yeah, absolutely. Lots of thanks to him. And yeah, that's basically it. We now have a team page that just exists out of a page. We do not have a content type team member and a content type team and whichever you want. And if you separate for you or something that then the client has some kind of drag and drop stuff and that wants to add multiple teams. You can all do this with this. But it's a view where we want to change the order of the things. Yeah, definitely. So yeah, that's what clients ask. And in this way, especially for these kind of small types of content types, it's probably not needed to have a customer content type. And here as well, you could do stuff with the templates. If I go here and I import from library, I have one here, team member, yeah. And that has some stuff in it. And then your client could get started. So either your client could make this template or you could provide it for them. So they already have that and it will save you building an entire content type specifically for that. Team member, team member content type. So we'll go back to the slides. Content type less. Yeah. So do we still need content types? Yes, we do. Although we were claiming you do not, you still do obviously need content types. But you need to remember that Drupal is evolving and so are our clients and especially what they are expecting. And this way you could allow your clients to do much more with Drupal, much more than they are doing now and much more, have much more flexibility than what they are used to and they do not have to send a change request for every type of change that they want. They could do way more with this. But you do still need content types because yeah, things like events, you're gonna need an extra field to say what the date is, things like that. Do not throw away content types. However, in some specific cases, you could definitely move away from a custom content type and just use the page. Does it work in production? Good question because yeah, that all looks very nice and well, but we tried it in production, or no, we tried it, we did it in production and I asked one of our developers for a fairly big Belgian company which, and he said, yeah, okay, we dumped it on a little bit because if you give the administrator interface to the content editors, it's a little bit overwhelming. There's really much configurability. There's a lot of things that they can configure, but they dumped it down a lot so they only showed them some block types and made it really easy to use. And it was strange because the developer told me yeah, there were no complaints and we really had to ask them if they were like, does it work? And they said yes. And it was like oh, because that's not what we used to know from Drupal where we say like editors, do you like it? And mostly they didn't used to like it a lot so it was really a good experience there. Is there more? Is this for me? Some of them, just interrupt me, that will be fine. So some of the modules we used to build this and this one is called layout builder model and it just basically puts everything in models which as you saw, works quite well. This is the operation link to change that to structure and metadata and manage content kind of stuff. We'll have to go a bit quickly because we only have 10 minutes left. So locking of specific content. I'll show you that one that was with the header so you can really lock down whichever part you want so you can just allow moving or adding new blocks or not or these kind of things. It's really, really powerful if your developers know how to use it, then you can really do crazy things with this. So there's another slide from this, so layout builder lock it's called. This is layout builder restrictions where you can restrict certain layouts to be used by certain roles and force in certain blocks. So this also makes it possible to dumb it down for the editor so that they can have like a nice experience using it. You don't want to overwhelm them too much with everything. Yeah, and actually that's the same thing with the whole library thing. Know your client in that case. Not all clients will be able to manage and will cope with the whole library thing and then just disable it for them and do it yourself and prepare some library types for them or library items for them but don't let them edit, that's also fine. So yeah, another slide from this. Section library, what I was talking about. That's exactly so we tackle that one and these are models from the section library. It's also module that you can just install and try it. It looks like this, you have add this template to library and then you can choose a section from the library so it's not very hard to use. Sorry for the Dutch text here. Indeed, sorry for the Dutch read. Forgot to translate something. Sneaked in there, okay. So one more thing about this. Everything, usual for block pre-processing, everything applies so because it's all blocks you can just do everything you used to know for blocks. I'm not going to go there because there is lots to say about that and you should already be aware of this because blocks aren't very new. But there is something because a section, a block is in a section and a section is linked to a node. If you want to start changing the structure of pages like for a lot of them, you cannot just hook override or create a class. You need to go migrate all those nodes so that this is different than you would do it like with a structured page where you can just change the template so it doesn't work like that. Here you see a loop where we loop over the entities, then we loop over the fields and if it's a type layout section, sorry for that, then you can see that we loop over these items in there if there's a block. So we're looping over component blocks and then you can see if it's type block content then you can start changing things. So you could programmatically change the content in each of these blocks or these sections by looping over them. This is like how you should do it with layout builder and sections. This is a bit different than how you used to work with blocks, for example. And content staging last but not least. One of our developers, Nginx from Ukraine, by the way, created a module which allows to easily export this content. You see it's here, it looks like this. You can export content. This is like content and it exports everything into this kind of field. They're working on making it nicer to use. But with this, you could do manual imports of content. You could package your content into a module. You could update it with an update hook or you could like, drush export content and drush import content or this allows you to let content move through environments, through sites or like, and this is what we're using also in production, by the way. So we're actually using this for them to create content in a staging environment, choose which one, export it and import it into production because they like to set up the sections and the blocks in staging and import it into production and it's ready and verified. Does it work with personalization last? As we do personalization atroposalit, we have our CDP and our rocket automation, a very quick demo there. Yes, it works. That's the answer is short. What you see here is, so I have this page here where there is, it's called the purple rain. You see two blocks here. When you would visit this page as an anonymous user, you would only see one, depending on what kind of page visiting behavior that you have. So if I'm visiting more as a Mother's Day person because I came in through an advertisement link or whatever, I would only see this button. Why is that? Let me show you here on the bottom. You see that this segment selection button allows you to select a specific segment of users to show this content too. So if I update this, I would change the segment then. It would only show this block for a specific kind of content without doing extra things. So it works with personalization as well. Yeah, and if you want to learn how to do personalization, we have another session on Thursday. Not sure what the hour is, but we'll teach you how to do... That for yourself, yeah. Yeah, yeah, that's something. Aha, the moment de gloire. How can you start with this? Well, beginning with this isn't very easy because it's an install profile. It's a combination of modules and there's a theme in there and it's not very easy to start. So you could start with Composer Start Project and then it's very new with the Drupal rocket ship, Drupal rocket ship. But a few slides in the future, you will also see there's a link where you can try it online by just going online. Does it have issues? There are some issues that we needed to work around. There's a hard dependency on the theme, which isn't the bug is a feature, I was told. The nesting of sections is also currently not possible. As we were based in Belgium, there are multiple national languages in Belgium. That's important for us and we worked with asymmetric translations for the moment. We showed you content staging and migrating to change many layouts is something that you need to be wary of because you need to write a migration. We added some core patches, but you can see them on our Drupal page and you can try it out and this is where you get to try it out. So if you want to try it out, this is the moment, take your laptops, navigate to it, take a picture, give it a try. It's on a test server, so we'll see how it ends the traffic, but don't be scared. Just if it's done, it's good. We didn't ask our ops guy to check it. Of course not. Of course not. It was no longer my problem. No, no, it should be fine. So this is just a website. It will lead you to the user registration page. Just create an account and then you can create a page. We didn't use the email validation so you can use any email address that you want. You don't have to give your personal email just to type in something. It will work without email validation. So go there. If you missed the URL and you want to see it later, come to me, talk to me. We're also, I don't think we have much time for questions, so I think also for questions, come to us after the presentation. We're more than happy to have a lot of questions. And with that, please connect to us on LinkedIn or send us a mail or on Drupal.org. We had a great time here, and thank you so much.