 Okay I think we will start. We are happy today to be with you and share our experience with Drupal. We will be fast because I know all of you want to see in which city Drupalcon will happen next year. So today we will share our experience on paragraph layout paragraph and paragraph sets modules. We are in-crew our user experience with those modules and you will have a quick demo about it. My name is Pierre-Ike Peadkade. I'm working with Drupal since 2009. I know in Drupal since version 6 and we see a lot of evolving on it. I will let my colleagues introduce himself. Hi everyone, I'm Xavier Tarnizian, I'm a front-end developer at OVH Cloud for six years now. So some words about OVH Cloud. OVH Cloud is a cloud solution provider so all of you know Amazon, Microsoft but we are I think a major cloud solution in Europe. We have many data centers and of course our main solution are dedicated server, public cloud, private cloud and some tools like VMware and more. So what is Drupal history at OVH Cloud? So before 2018 we were building all the pages manually based on XC70. Just imagine the burden on it. Then we moved to Drupal in 2018 and we enjoy like features like translations, entity reference, media library, you know all of it. And one year later all our public websites were built on Drupal. Our corporate website, event website and sub-branding like Kim Sufi, So You Start, Echo, how we are working. All of you are using FieldUI to build their contents. So this is one of our product page. Like you see there is a lot of fields and there are some advantages about it. Like the developers know how to handle it. You can do for meters on fields, you can do preposets, it's easy to integrate and you can manage specific features by it. But the drawbacks is after five years each time we receive a request from our product owner we ended up with 67 content types. So when you arrive on our Drupal you don't know which template you should use to build a page. And just imagine for developers also to maintain all those content types. So what was our needs? We wanted something really to use. We wanted something with a lot of customization, something that all our employees without knowledge about Drupal can use. Of course we have a design system, we wanted to plug it. And one important point is we wanted our developers to waste less time on integrating content and more time on developing features. Like product features for example. We tried many things in the community like layout builder. We made our help center website on a layout builder. We tried paragraphs for our corporate website. We tried also bricks which is the same thing almost as a paragraph but reusable. And of course they were known Gutenberg. But we decided to keep our knowledge and competencies on paragraph because our employees on our corporate website really like it. The feature was really nice but something was missing. And we tried layout paragraph. So for those who went at Drupalcon in prior last year, Justin from the manager of the module make a really good presentation of the module out of the box. So layout paragraph bring you layout into paragraphs. So you can build some paragraph which are using layout and introduce some paragraph in the layout. You will have the drag and drop features out of the box which is really nice. And the page really looks what it will be seen on the front of this. But like I said, we had 67 content types and we wanted to produce pages really faster. So we did paragraph set. So for those who knows paragraph set is a module that allows you to configure with Fiamma some templates of page by defining which page will have any kind of paragraph type. And you will be able to configure some data, default data inside. We added some previews, some shortcuts like alignments, one click component. For example, if you have a component which doesn't need configuration, you don't want to open a form, edit the component, add in some settings. You just want to insert the component easily and quickly. And of course, some customization by language. We made some custom OVH cloud features. I will say OVH because it's really related to our design system like contrasted features, but it's not the point. So let's see a demo. Bad luck. It doesn't work with the duplicate screen. Let's do it. Okay, so how it works here. The user has two possibilities. You can select an existing full page template or a card can create his own from scratch. Here you have access to a bunch of components such overviews, sliders, testimonials, etc. Some product cards component and some navigations component. Some component can have different style. So for the demo, let's try to create a new. Okay, so for this, let's just add here a new layout section. You have to do it yourself component layout section have two columns. We have some custom style design. For the demo, let's set a blue gradients and save it. The first column, let's add a text component. Let's add a title and a description. You have some custom font size style here. In the second column, we can add a media. This one. We also add some shortcuts to handle the vertical and horizontal alignment. Now our component is ready to save. Let's save it. Okay, so it's quite time consuming to do that. So let's convert it to a paragraph set, set titles, categories. Let's save it. Here we can go to the configurations of the paragraph sets, can change the categories at the preview files. Here you have the complete configurations of the component we've created. All is still fully editable. Save it. Now we just have to go to the paragraph type section, find our overview components, edit it. Here in the behavior sections, we have the paragraph set enable here. So let's find our Drupalcon overviews. Let's save the paragraph set. And now when the user creates his page from scratch in the overview section, you have access to the new Drupalcon overview here and can add it with one click. All is still fully editable. To complete the page, we can, for example, add some product cards component. As I said, the layout is still editable. So can change the layout and add a fifth column instead of trading by our own the second column. We can duplicate this one and drag and drop here. Okay, that's it for the front scratch parts. Let's see how it works with full template page. So here we have a lot of templates strictly different, different theme with different components and different theme. For the demo, let's pick this one. And in one click, all the components have been added to the page. So your user don't have to focus about the design or the structure of the page. You just have to focus on the content. And if you save the page, voila, a full page created within one minute, and the user just have to change the content image and interest. Our solution is not perfect. So I will let you talk about it. So the solution is not perfect. Like you see, when you create a page, you will add sometimes a lot of components. And I will give you an example, a component that we'll see in every design system is a divider component. So sometimes web master wants to add some space between components. So they use a divider. And you can be surprised like sometimes in one section, we for in our case, we discover 20 dividers next to each other's because they wanted the first column to be empty, but still have the space on the screen. So they made some little tricks. And the bad point about it is divider is a paragraph. So you will have 20 paragraphs created in your database. In our case, we have 22 languages in Drupal. We are using content moderation. So when we say 20 paragraph, it will be 20 multiplied by 22 language multiplied by each revision that has. So it's really a mess. But you have way to fix it like you can, of course, limit the paragraph inside a section. So if you don't want to allow some kind of paragraph, it's possible. And the last point is of course, translation. I've been working on Drupal since, like I said, 2009 and translation is always a bit difficult to handle. And when using paragraph, what is difficult is the synchronous paragraph between translation. So if you need, especially localization between languages, like there's a section you don't want to display from Germany, for example, and be displayed in France, you will have to use some tricks. Like in our case, we develop a behavior in paragraph to disable some components on some languages, or we can use some entity reference contents in those parts. But it's a mess. And that's it. So don't forget the contribution day tomorrow. It will be the last day and last opportunities during this week. And thank you for all.