 So, this is going to be fast because only 10 minutes I'm going to present you. My Monster website is a crash test multi-site running on beta with almost 500 plugins. So the first thing is why and why it's useful to me and what's in it for you, what could be useful for you as well. So the first thing, it was to have fun. Some years ago I said, okay, that could be fun if I install all the plugins I have access to in one big, huge multi-site and then I use it for all the things I'm going to present you. Different use case, it means that for a given project I may have different needs and I can pick in my list of plugins and install that in a sub-site of the multi-site and check if everything is compatible if there is no conflict and it's easy because all access is there. I test with whenever I have a beta access to a plugin, if I know the developers I have a beta access so I can test this with themes or other plugins for conflict and inform the developers if this is the case because myself I'm not a developer. So it runs on the beta WordPress, means on the nightly builds, I will show you that. So this is the, it was updated this morning, so it's 6.5 alpha with that number. It means with the current beta test of the next version. So I've always, the version that is updated the last night and as you see, 481, actually it's a little bit more, this was an older capture so it's almost 500 now. Of course the first question people ask is do you activate them all at once? No, I don't. Actually I tried something but I will create a sub-site of the multi-site and activate the plugins I need. I test a wide range of things. I have many themes, classic themes, block themes, so the new with the site editor. I have a lot of plugins for different use like forms or tables or whatever. I have many page builders that I tested and this is one of the sub-site I tried to activate all the page builders at the same time. It was not working but it was fun. I also often talk about multilingual plugins because I'm from Switzerland and we have many languages in our country so it's a very common topic to talk about multilingual plugins. And I present that at meet-ups and I tried them all, like all the names you know about multilingual plugins. There is one that is my favorite, this one, is a multisite language switcher. I trust very much that multilingual plugin and its developer, Dennis. And it's very nice because with my use case, I test and I install two or three different sub-site of the multisite and I can export easily to importing a production site. To export from a multisite into a production site, either a standalone or another multisite, I use a plugin called Prime Mover and it's working with a free version for that. It's very easy. I just went, yeah. So with the full list, I can select the plugins for a new project and I can also copy paste block patterns that I made them ready, for example a complex colon or whatever and I can simply copy paste because with Gutenberg it's easy to copy paste and it's ready. I have, for example, forms. I have a contact form in French and when I install that contact form plugin in a new site, only the English demo will be there. So I can simply from this starting site export and get the JSON or CSV file and import in the production site. It also increased the confidence in the plugin reliability and compatibility and I'm also checking for security. On that multisite, I have a plugin called WP Vulnerability. This one lists all the plugins that have been abandoned, so it means not updated since a long time or if there is a known vulnerability. I would not install that on the client side because it would scare them a lot. So there I have a bird's eye view of all the plugins I can use anywhere. I have the list of if there is an issue and I know in advance and I can either find an alternative plugin for the same features or if it's a vulnerability tell the developer but usually they already know. But then I can wait for an update for the production site on my site or my client's site. So yes, I told you about the templates and plugins and some settings that it's easy to export and then re-import in a production site. I told you about the forms but it can be, for example, if you use code snippets, you can have a full list of code snippets there, export and the one you use and import in the production site. AI plugin, local translate for translations, I told you about the forms and everything you can imagine. I have my starting stack and then I export and it's easy to build on the production site. This is important because when I talk about this and I say, oh yeah, there is almost 500 plugins and people say, oh! But relax, it's fun and it helps to prevent issue on the production site actually. It makes things much more relaxed for like. This one I'm going to skip because it's only a 10 minute talk. I was planning to ask someone to try to hack it in one of the entries or whatever but yeah, we have no time. That would be helpful if someone can enter and then I get to know maybe the point of failures and point of entries via an abundant plugin or vulnerability. This slide will be on my website so maybe we can do that anyway. In conclusion, the first thing it was to have fun but then I discovered that it helps also for many use cases. I love to find out the reason when the white screen of death appears, even though I'm not a developer, it's funny for me. It works in diverse situation and I can explore the plugins there and I don't need to deploy every time at development sites and I easily solve things proactively actually. This QR code goes to my personal site contact if you want to follow me, all my social links and the third here is a crash test if you want to have a look at this crash test. Thank you. Grazie.