Laravel Worldwide Meetup - Statamic: The Laravel native CMS and Content Platform

Heat. Heat. N. Hey, hey, hey. Let me follow you. Hello world. We are live. Welcome to this March 2026 edition of the Laravel Worldwide Meetup. My name is Dan Sapelsa. one of your co-hosts along with Margaret Tvaris here. We're thrilled to once again bring you an awesome presentation from someone from the Laravel community. Speaking of my co-host, Margot, how are you doing today? I'm doing pretty good, Dan. How about yourself? Doing great. Yeah, we're uh we're slowly but surely heading into spring here in Canada. The weather's getting a little nicer and uh lots of fun stuff on the horizon in the Laravel community as well. So, looking forward to all of that. So, yeah, lots to be uh to be uh looking forward to for sure. Um, and with that, we do have a bit of community stuff, I think, to touch on before we bring in today's speaker. So, uh, what have we got here, Margot? Thanks, Dan. So, Laravel News is one of the best ways to stay connected to what's happening in the Laravel community. Um, so they do a great job covering releases, tutorials, and everything going on each week. So, you can sign up for their weekly email newsletter at laralnews.com. And you could also check out their Laravel News podcast run by Jake Bennett and Michael Dinda. So, thanks to Eric Barnes and their team for running this great resource. If you haven't heard the Larville podcast, this is a great podcast run by Matt Staler. Uh, and congrats on being the newest board member at the PHP Foundation. So, we'll shout out there. Um, in their latest episodes, Matt's organized a great series of getting to know the Laravel team. So, be sure to check it out at laravelpodcast.com. Also, if you are looking to hire or you're looking to post a job or for all your Laravel job needs, you can check out larajob.com. Um, and one other thing that we want to do on in the community is highlight some companies that are looking for some laral developers. So if you want to check out American Kennel Club, All Calls.io, Felix, Site View Software, and Vivid Impact after the meetup today, you can find some more details about these job descriptions um and below in the description of the YouTube video. Uh, if you haven't heard about Larcast, it's one of the best ways to learn Laravel. So, a huge thanks to Jeffrey Wei for building such an amazing resource for the community and you can check it out at larcast.com. And a quick shout out to the Laravel community. If you're looking for more events that are just like this, the Lar World meetup, um there's a lot of other events that are happening around the world. So, definitely check out the community. It's a great way to stay connected and find meetups near you. And if you have an event or a meetup that you want to share, you can register your event there, too. Also, there are some really cool ways that Laravel is spotlighting the community like Laravel stories and artisan of the day. So, if you've built something you're proud of, please head on over to laravel.com/stories, answer some of Taylor's questions, and share your story with the community. We also want to say a big thanks to Vehicle for their support in hosting this meetup. So, they also have a great team of developers. And so, if you have a layer of a problem, be sure to hit them up at govehicle.com or check out their website, vehicle.com. And we're also doing a giveaway. A big shout out and thanks to our Jet Brains sponsor. They're going to be giving out a couple of one-year subscriptions, one-year subscription codes to any Jet Brains IDE. Winners will receive an email if you scan that QR code. And watch out for that email. We're going to be announcing our winner on April 7th. And those are all of our community announcements. I'm going to pass off to Dan to announce our speaker for this month. All right. Thank you, Margot. Um, our speaker this month is Joshua Bloom. He's a developer at Statamic. There's a good chance if uh you're watching this stream that you're familiar with static already. But if you're not, Statamic is an awesome uh CMS or Laravel powered content management system. Uh if you're already familiar with Laravel and developing with Laravel and you need need a CMS, Statam is a be a great tool to reach for. And uh recently within the last few months, we've had the release of Statamic version 6, which as you can understand comes with some some upgrades, um some improvements, some new looks from what I've seen. And uh Josh is going to join us today and uh and kind of share some of that stuff. So, without further ado, let's bring him in. There he is. Josh, how are you doing Hey there. Uh, yeah, thanks for having me. Um, I'm doing pretty good. Pretty excited uh to yeah, show you Statamic. Um, and um, yeah, everything we introduced with, uh, with version 6. Um, which is kind of a yeah, major thing for us. Um, and yeah, also like if people on the stream like have never um heard of Statamic before or have never actually used it before, um, just give like yeah, an overview and and an introduction about like what Statamic is and um, yeah, why it's a great CMS for maybe your like next project or already your existing project. Awesome. That sounds great. Yeah, I think that would we'd all benefit from some of that. So, without further ado, let's uh, you want to share your screen? I think you have some slides and some stuff you want to show off there and then uh Margot and I will step backstage and we'll we'll hand it off to you. Good luck, Josh. All right. Thank you very much. Just let me enable my screen share. All right, here it is. I see it. Should be there. All right, we'll talk shortly. We'll be backstage. Uh the stage is yours, Josh. Talk soon. Awesome. Thank you. Um All right. Yeah. Um welcome everyone. Um I'm going to give you a yeah overview about Statamic. Um which yeah is like a Laravel native CMS and not only a CMS but like content platform um that can do like um many things way more than um yeah in big like air quotes just a CMS. Um and yeah I'm Josh. Um just a really quick introduction about uh myself. Um I discovered Statam um all the way back in 2014. Um while it was um not even um on Laravel yet, but still um built um on Slim PHP. Um I started using Laravel um in 2018. Um actually Statamix switched to um Laravel in 2017. Um so I um only really started using Laravel as a framework like a year later. Um and like just about myself. I'm really into triathlon and like all the like uh three discip disciplines. Um, and I'm currently preparing for Challenge Roth, which is, um, if you've never heard of it or if you're not into triathlon, um, it's an iron distance like triathlon. Um, so yeah, uh, currently is kind of like my, uh, second job to prepare and train for it. Um and yeah, Statamic is a CMS built on top of Laravel, but um you can also like see it as again in big air quotes just another package um in the like big and uh really great like Laravel ecosystem. Um, and one of its greatest strength, especially for I guess most of you like in the audience now, which are like Laravel developers, um, it can be installed into any existing like project or Laravel app you have at pretty much any point. um whether you're just um creating a new application or have created it like last week or if um you have an application that's been like running for a decade um if um yeah you're looking for a CMS um you can just install it into your existing app as well. um kind of a little like um yeah background about Statam. Um in 2012 um version one got released um which was not on Laravel yet um because Laravel wasn't really a thing back then. It was just like I think in 2012 or 2013 uh was the first stable release. Um and in 2017 we switched to Laravel uh with version two of Statamic. Um it was a Laravel app in itself. So not like a package that you could just install into any other app. Um but like um a closed like application in itself. And that changed um with Statamic 3 which we introduced in 2020. Um and it was like a yeah major architectural like overhaul and shift um static becoming like a composer package. Um and between 2021 and 2025 like a lot of stuff happened. Um we released um yeah 3.1 3.2 2 which wasn't like semantic versioning um back then and also like v4 v5 um where we switched to semantic versioning and had a major release like every year and now in 2026 um we release data 6 which is um yeah a big step for us um because it is um yeah kind of a big thing with a redesign and um a lot of features that um we ship with it and yeah why why trust data make um as a CMS as a product um it's battle tested since 2012 so for over a decade um it's uh been power powering a lot of apps and and sites um actually tens of thousands of sites are in the in the wild from small like simple um brochure sites to really large scale enterprises is that serve like millions um or even billions of um page views and and visitors. Um and there is an active add-on ecosystem as well. Um everyone can create an add-on and even sell them through our marketplace. And we have an amazing community. I think the Laravel community itself is pretty amazing and welcoming and kind of unique compared to like a lot of other communities. And um there is a big overlap between like the Laravel and the Statamic um community of course. And so yeah, shout out to everyone like on our discord server and just like um all the amazing people like contributing to static um yeah writing blog post doing like screencasts just yeah all the community members big thank you um what we're covering in in this um little like uh meetup talk um why you shouldn't build your own CMS maybe again maybe you've tried it in the past um and the general concepts of Statamic um like collections and entries. Talking about that in a couple minutes um what's new in Statamic 6 since it's a like a major release for us. Um and also do a demo um since most people here are Laravel devs. Um, we're going to, um, install Statam into an existing Laravel application. Um, so you can just start a static site from scratch. Um, which is nothing more than a composer create project pretty much similar to just a vanilla Laravel app. Um, but it also includes the Laravel CMS package. Um and yeah with the point um building your own CMS um from a developer perspective it could also be fun like um just something you do I don't know like in the evenings or like on the weekend but if you're a freelancer for example or an agency um or you're a company like that um has a product um going and at some point you're like, "Yeah, we want to release or like publish blog posts or um do our marketing site." Um yeah, then you're like, "Okay, should we build it ourselves?" Because a lot of the time it just starts with we need a simple blog or we just need like a handful of landing pages, simple marketing pages. Um but then all of a sudden after that yeah first couple of um landing pages or like a couple of blog posts it's like oh yeah but we really want like a rich text editor that's like featurerich and offers like a lot of like neat little things and then you're like okay we have maybe like a handful of landing pages and we want to reuse the components we have on them um to like quickly like ship like more like landing pages. So then you're like, "Okay, like a page builder would be nice." Um maybe you need an admin panel as well. Um and you don't have that already. Um and then you've built a CMS like you have a rich text editor, a page builder. Um but then like maybe you grow as a company or um your your website just grows um and then you need uh need like multiple localizations, languages or different um brands even like serving um yeah for different countries, multiple brands for example. Then you need forms. you want um to have maybe a simple contact form, but later you want to have like um call to actions, newsletter signups. Um maybe you run giveaways. Um so yeah, you you want forms. Um do you want to build that yourself again? Um, then you maybe need image resizing and general like asset management for PDFs um or like um when someone signs up to your newsletter, you um offer them maybe like a handbook or something um on whatever like SEO like optimizations on uh or like how to use claude more uh efficiently and you want to collect for example their email, you need a form. um you want to um have um yeah assets like PDFs for example they can download then uh you need asset management as well. you want to improve your website performance, then you need image optimization or image resizing. Um, user roles and permissions. Um, maybe you as um the developer um are an administrator um but depending on how many people there are, you want like granular like control over their permissions. Can they edit the like overall like main landing page for example? Or are they only allowed to write blog posts um and not even like publish them but just like create them um and um someone else to review it and publish it? Um SEO optimization or now like AI crawler optimization as well. Um do you want to build all of that yourself? Um, and maybe at some point you're like, "Oh, now we have a mobile app as well." So, you have to build an API for it or like API endpoints um to serve your content to your Yeah, maybe iOS and Android app. Um, and do you want to do all of that Um, because there is like a hidden text to it um for something um custom you build. um the maintenance like you own it forever. You have to maintain it like down the road like um small little things or even like bigger things like refactors like tech debt like all of it. Um security vulnerabilities you need to patch them like yourself. You um have to keep an eye on it. And um now with AI like um security vulnerabilities now uh like with the one with Axios for example um are becoming like um even more important and um yeah do you want to like do all of that yourself and onboarding developers as well or like even users that use um your CMS in the end like marketing people for example you have to onboard everyone on if there is um a like well-known product um or like a CMS that's already been there for over a decade um in this case Statamic which uses um all of Laravel's conventions. It just feels familiar to the developer um that might join your team for example. Um so yeah it's just like um one or like a couple of things you don't really have to think about. Um if your developer like a new hire joins and uses data make maybe he he or like she they used it before um they just feel right at home. So like the onboarding um takes less time. So instead of building everything uh yourself, Statamic like kind of solves all of this because it's already built and it's been going like for over a decade. Um, and one of the things that um, I like about static or like even when I discovered it like over a decade ago um, was its flat file approach which means that the content is in markdown and YAML files by default. Um, Statamix supports the database as well. Um, I'm going to talk about that in a bit. Um but by default um everything is in markdown and YAML files. Um and why this matters or why this is great is your content lives in your git repo as well. Um and this serves as a built-in backup solution actually like a pretty powerful backup solution because a lot of like built-in backup services they keep like the most recent backup or like a daily, a weekly and a monthly backup for example. But with your git history, you have like kind of a backup for like every small little change you've done. And you can even see like who did it because Statamic not only integrates with git from a like developers perspective but also from the control panel. So when marketing people for example or content people um edit content from your production like side from uh within the control panel um it gets uh committed and pushed to your repo. Um and yeah there is no database needed for simple sites. Um and yeah by default it's um flat file. um when you create a project or even like with our new wizard, it ask asks you whether you want to use the database, but you can change it like down the road at any point. Um which is great because um you don't have to maintain a database. Um and it's also like a potential security vector as well with uh things like um SQL injection. So just one thing uh you don't have to worry about. Um, like I mentioned, there is Git on the authoring site as well. Um, and yeah, what's amazing is, and that's kind of like one of the things that, um, Jack, one of the or like the founder or co-founder creator of Statam, um, um, his pain point was, um, environments like, um, being like mirrors, for example. Um you might know this to have your production environment like kind of like locally you would do like a um a database dump um import it locally or write um uh factories and ceders to have like fake content for example to work with. But when um everything is in git, the content as well, your local and prov uh production environments are the same. Um and vice versa. Um if you don't like this, it doesn't have to be like that, but it's actually like a great experience um as a developer to have the actual like production um content locally available. So you can build or design the site um with actual like um content. Um and like I said there is full database support when needed. Um at any point you can just switch to our eloquent driver. It um supports importing from flat files and even the other way around. Um, so when you think, um, okay, um, I started this site with a database, but it's just like I don't know, I don't know, like I don't really need it. Um, it just adds complexity. Um, you can even, um, export from, um, the database back into flat files. Um, and there is also the amazing um, runway add-on by Duncan. Um, it started as a kind of like community add-on, but Duncan um joined the core team um and runways um a an add-on that allows you to um manage um all of the existing eloquent models and everything you already have in the database inside of um Statam and the control panel. So if you have an application for example that's been running for like multiple years and you have a lot of content in the database already you can um use runway to view um edit create everything um you have in the database from within statamic and the control panel um and yeah the control panel is kind of like um statammix heart and um yeah it's actually um a UI that um users and devs as well actually enjoy using. Um it doesn't get in your way and it's um yeah just beautiful and easy to use. Has a great um UI and UX and uh since V6 um it's on Vue3. We upgraded from Vue 2. Um switched to using inertia. Um, it's been built with Tailwind CSS for quite a couple of years now and it's fully extendable and customizable as well. You can theme it. Um, you can change so many things. Um, it even supports white labeling. Um, and yeah, now a little bit about the um general like uh concepts of Statam in terms of of content. Um so there are um collections you can like um think about it like yeah database tables um could be as simple as uh pages or like blog posts for example but it could also be something like um products for example if you think more um in terms of a yeah like business application in terms of like a um Laravel app um then there are like entries that are like single pieces of content um in a collection. Um and um then there are blue uh blueprints which are the schema. It defines which um fields are available in an entry. Um and you can see here that um there is an example um which would be a YAML file for the posts um collection. And just to keep it really simple, um there is um a handle of title and the field it uses is um of type text. It's required um and um it is just really like simple text field. Next is the bot field. I'm going to show it to you later. Um, but is a um really soph sophisticated and um featurerich um field type that builds on top of um tip tab and pros mirror. Um it's yeah really like a rich text editor on steroids and um offers a lot of um features. Um and oops um then there are uh assets as well. for example, um if you want to set a hero image um or yeah, just whatever like assets is kind of agnostic. Um main use cases images for example, but could be PDFs and everything as well. So this is just like a really simple um blueprint of um what a blog post for example could look like. You have a title, you have a bot field and an assets field for like a hero or like um the article or post image for example. Um Statam offers um more than 40 builtin field types um and you can build your own ones. You're not limited to the um field types that Statamic ships with. And um since um Statamix 6 um there is also a new UI component library we've built um that you can just reuse and um yeah build your own field types with um if yeah you need to build your own one but for like 99% of uh sites and apps uh the built-in ones cover everything everything you need. Um I just highlighted the Bart and replicator um field types here because they are like somewhat special in a way because um both um especially in combination uh really powerful um when you want to um build something like a page builder experience for example. So like I said, bot is a um rich text editor with a lot of features that is um extendable as well. And the replicator field type um like the name suggests um lets you like replicate um uh content blocks. So, um if you combine these two, you can build um really um powerful page builder experiences um for your site. And when it comes to the front end, um Statam ships with its own templating engine. Um it dates back to like version one. Um and it also has first class um blade support. Um, Antlers is kind of um even though it's um very featurerich, it's in some ways simpler than blade because um it kind of is like um the controller logic is in the template itself. Um so with blade you would usually have your um regular like model view controller appro approach and the logic for the view sits in the controller. Um with antlers you would usually like skip this uh controller approach and have the logic in um in the template. Um blade support is like first class. Um our documentation as well um always shows an antlas and a blade snippet. Um and it's your choice. Um if you have existing blade views in your existing application, you can just continue to use them and um use everything that Statamic offers inside of your existing views as well. Um we offer like a lot of facads for example that you can um use um from inside your existing controllers um to yeah have the data available um in your view and you can even mix them if you like with partials for example um or like components um yeah if you have existing um blade views but want to um create certain things in endless for example you can even mix it or if that's um Yeah, if you don't just uh if you don't really like um the approach of um having blade for example or you use a JavaScript framework um like next for example um Statamic um also offers a built-in REST and GraphQL API. Um and it's super easy to use. You don't have to even though you can you don't have to um write endpoints yourself. you essentially just switch an enviable to true um either the rest uh the rest or the GraphQL API or even both and it's kind of like um autogenerating. So like from from your like content schema and everything it just generates endpoints for you even though you're not limited to them. If you want to change certain certain things um you can do so. Um and yeah, Statamix 6 um which we uh released um in January um so like um about 2 months ago um introduced a lot of features. Um this is even like a shortened list with kind of like the important things. So, it's a completely redesigned control panel, a UI compon uh component library that's really handy for developers creating add-ons or custom field types for example. Um, we introduced control panel theming. Um, and yeah, also upgraded from view 2 to view 3 um to Tailwind CSS4, moved to inertia. Um, then we also introduced a command pallet which is pretty cool. I'm going to show it to you um in a couple moments. Um it's just like um for example like raycast uh or Alfred kind of like the command command space or like command K thing that you can um yeah run commands from or like navigate an application from. We also introduced elevated sessions um native and built-in two-factor authentication. Um pass keys are supported as well. Um, so you can see like if you would build all of this yourself when you build your own CMS, um, it's quite a lot of like features and things to add that Statam just like um has built in. Um, regarding AI, um, we also have Laravel uh, boost guidelines that are static specific. Um, there is also a Statamic MCP server add-on available. Um and um yeah, live preview for example um supports hot reloading and the rest API uh there should be a line break. Um now supports um authentication as well. Um this is just like a like about like 50% of uh the features that um are new in Statam X6. Um yeah, it's just scratching the surface. Um and the ecosystem um is uh pretty amazing for Statam as well. Um on static.com/marketplace um there are both add-ons available which are um also uh just composer packages as well. So add-ons you just composer require them. Um and starter kits are available as as well that um are similar to the um starter kits that Laravel offers even though there are also um paid ones that offer um um components to you for example with beautifully built UI and um yeah in terms of add-ons um there are a lot of like um categories and like um for example our SEO pro add-on is it's a first party add-on um Yeah, helps you um with SEO optimization, but there are also add-ons, for example, for AI, like I mentioned, the Statam um MCP server, but also e-commerce um like a Shopify add-on, for example, um or cargo, which is a pretty um pretty amazing um e-commerce add-on um that's uh created by Duncan, our team member. Um and Statamic um is a paid product even though we also offer a free version. Um but we think like that our um pro version like offers a lot of features um that uh yeah are well worth it because if you like compare like the list of features to building it yourself like um the return on investment or like the break even is reached uh pretty quickly. Um, like I said, there is also the free version. So, if you're just building your personal site, for example, your portfolio, a blog, for example, um, you should be good most of the time um, just using the free version. And Sedamic Pro is also free to try locally on and on test environments like your um, staging or like dev server for example. And their license is only required um, at launch or like um, once you launch into production. Um yeah um now it's time for a little demo. Um like I uh mentioned earlier um since I guess most of you are Laravel developers um we are going to um install statamic into a yeah fresh but like existing Laravel app. um create a collection um edit the blueprint um add entries um via the control panel and um yeah um and also peek uh at the flat files in the repo to see like how the markdown files and yl files are like um yeah getting added to the repo when you edit things from within the control panel. Um, all right. Just let me um get everything on the screen. All right. I hope I'm not blending anyone with my light mode, but I'm a light mode guy. Um, and this is a um a fresh Laravel app I just created earlier. Um, and we have docs available for how to install statamic into existing um existing Laravel apps. Um, because um it does a couple things differently. For example, if you have an existing Laravel application going, um you usually already have um existing users in the database. So, Statamic is just going to use those. Um and it's super easy to install Statamic into an existing application. Um you essentially just do a couple changes to your composer JSON. um then you're going to um require statamic um and run the O migrations. That's pretty much all there is to it. And um yeah, we're going to do that now. And um just uh yeah, hit the CP route then and start using the control panel. Um, so I'm just going to uh copy those uh commands real quick, add them to my um composer file uh post auto dump. All right, now we should be good to go. Um let's copy the command to install it. Uh right application. Yeah, should be the right application. Uh yes, allow it. All right, that should be kind of it. Let's run the migrations real quick. All right. And if we open that now in our browser, you can see that this is like the uh regular Statam uh sorry Laravel um uh welcome page. But if we hit the um CP route now, we should get the um statamic um login uh login page. Um so let's create a user real quick. We can do that from the command line. Uh please make user um just user example example.com uh Joshua password super user in this case. Yes. Uh whoops. Um I run the migrations artist make the user again. So that is the case when you install it into a fresh application. Okay, user created successfully. I forgot to run the migrations. Um so let's log in nav item support collection of the okay script uh class definition. What? Let's have a look. Okay, I wasn't expecting this. Let's have a look at the lock file real quick. story log level. SQL table uses. Okay, if anyone has a quicker idea than I have. Hey Josh, I did notice that in the chat Jack said just static new a fresh site real quick. What do you think about that? Um I mean yeah instead of like uh because I did this early and it was working fine. Demo gods don't take a day off, right? So it's all good. But yeah, give that a go. kind of why we everyone loves a live debug too. So you got to make new. So like um okay um switching gear or like uh just doing it differently. Um you probably uh all know the Laravel installer um which is just a um composer package that you usually install globally um and it gives you the Laravel new command. Um we have a similar package um it's called the statamix CLI and um you also composer um require it usually globally um and it gives you the statamic new command um so let's do that real quick um when you do startup new um it asks you like uh with Laravel prompts like what is your um site called and just gives you the um entire like wizard to create your application um so in this case let's do the Laravel our worldwide meetup but this uh is already taken by the other app. So let's do the dash start. Um would you like to install a stat starter kit? Um let's do it in this case. Um you can um find starter kits on uh on um our marketplace. Um and um there are like a lot of ones available like free and paid as well. Um, and let's do um the peak one for example. Um, which is a really popular one. Um, like I said earlier, by default it's flat files, but you could also, if you want, use the database. Um, do you want to enable statamic pro? Yeah, let's do that. Um, do you plan to generate a static site? In this case, we don't, but we could uh create a super user. Yes. Um, initialize Git repository. Yes. um not a new git repo uh on GitHub. Um I've already start the repo, so let's skip that for now. And it essentially does the same as uh when you run Laravel new um but it um creates a new static project. Um let's just wait for a couple of seconds. So the um statamic site or like app is generated. Okay. Oh, this is an issue with my local machine actually. I think because of the um starter kit. Um so let's skip the starter kit. Wow. Laravel meetup. Um let's just call it test. Um blank site in this case flat file static pro no static uh static site create super user yes um git repo yes um nope already done that. Okay now we're good to go. Let's do the user as at example.acample.com. Uh name is Joshua. Password is a super secure password. Okay, now we're good to go. Um CD there test directory. What did I call it again? Oh, I forgot the video. Okay, let's open it. Other browser. Okay, this is the uh statamic welcome page similar to um the Laravel one we just saw earlier. And when we hit the CP route, we see the um the login. And let's log in real quick. Okay, now it's working. I haven't set up a license uh locally now. So, let's uh snooze this for now. And now you can see the um redesigned um static control panel um that we introduced with uh with V6. Um this is like um the dashboard that's also customizable. Right now it just says like um it just shows the um getting started widget, but this is also customizable. For example, you can just build your own widgets and yeah, have a completely custom dashboard. There could be user stats on here like um things like um jumping quickly to certain collections or like blog posts for example. Um you can just yeah build everything and customize and extend everything um to to your liking essentially. Um then uh let's go to collections. There is uh now a simple um pages collection for example um that we just saw when we um yeah opened the page um at the root um and it just shows like um the homepage. Um this is like a super simple um blueprint here with a title um a simple content field um you can set the author um and choose a template for example. Um, now I just have to like kind of like um improvise a little bit because I prepared um a couple things with the um with the Laravel app. Um but uh still like the concept is is kind of the same. So um let's um jump into collections and um we have the pages collection which would be like um yeah just to um build your site with pages, landing pages, marketing pages, um content pages or like contact pages. Um this is usually like kind of um in yeah most sites. Um but let's say for example um you want to have something like a um products collection. So let's just go ahead and create a um a products collection. Um let's say you do do e-commerce and you sell things online. So um yeah, we just created that collection really easily. And um now let's configure like the content schema um with the blueprint. Um you have like I said um more than 40 40 field types available um and it could be like simple things like a title for example which is just a a text field um but also um have um yeah more complex ones. For example, uh like I mentioned earlier, the bot field type is um a really featurerich um text editor um that you can also um build um kind of like page builder experiences with. Um so yet let's um use that one for example. And here you can see in the blueprint builder um that you have like a lot of options available and um depending on the kind of field type you have you have more or less options available. Um so the bot field type for example offers a lot of stuff in terms of um um yeah um rich text editing. Um so for example you can have headlines, you can have um lists like you can have something like quotes in there like or even um tables for example inline images um and yeah you can um depending on the collection for example um configure it for like each collection like some collections might um have um tables or inline images like enabled but others might not have uh that enabled. Um so let's um let's uh use a um a bot field um to hit cont. Oh uh content already exists. Um let's do uh um product or like let's do description. Um all right let's um reorder it to be like more at the top and also for example an asset because um every product product for example has um a um image for example let's call it just a product product image um and um by default it uses the um local file system but um of course through fly system um you can um connect to like your S3 buckets um or any other like um file system you have configured um or some like um external like um image image provider for example. Um let's just apply and save also put that to the top. Um click save and let's go to the product collections for example. um create an entry. And here you can see that we um have the product image and the uh description um available uh to us that we just um just created in the blueprint. Um so for example um that's something I had set up in the other demo um to do uh kind of like um mock content um for us and like uh kind of like have like um yeah a couple dozen entries um available then in instead of just like uh whipping it up or like creating them manually now. Um, so if you have like product one for example, you can just like um create all of your products um have a um an an image for example um could be an existing one or you could just like um upload one um and um in your description like then have for example um a headline um like uh amazing product uh product you really need um and um like um have everything in there for your marketing people um to um oops um to um yeah create um products for example um that you can sync um with Shopify as well. for example, if you use that um we have a um Shopify add-on on on our marketplace and the UI and UX um and we also call it um AX like the authoring experience is really great with Statam because it's just like really intuitive um for like most people to use. Um so that kind of like combines um both the DX for developers in terms of um yeah building um apps and sites with something you're familiar with. Um so if you are familiar with Laravel and have used it for a couple of years um Statamic um yeah will just feel kind of like natural to use because it just um uses all the or sticks to Laravel conventions. Um and for your users or your end users um it's just a great UI um that's really intuitive and easy to use. Um so onboarding new people for example is really easy as well. Um and um yeah um kind of uh bummed about the demo now like uh because I have something different planned for it. Um, so, um, I'm just thinking like, um, even like if someone in the chat, like whether it's like Jack, um, or like someone else in the in the chat, um, has requests or like ideas like um, what to show um, and give an overview um, of um, feel free to suggest something. Um, we could go over forms, for example. um taxonomies um which easily let you like um categorize things for example, could be blog posts, could be um could be um products for example. Um yeah, forms um are really um nice and we have um a couple of um neat things coming for forms in the future um regarding form building and really like um big overhaul for forms. Um and um yeah um just looking at the chat I just opened it. Forms would be nice to see. Um I haven't set up a form in this application. Um so let's just create one from scratch. It could be like a um contact form for example to keep it really simple. Um so yeah just create the form and um we have um security um or like um spam prevention um built in to a certain extent with a honeypot field for example. But there are also add-ons available um to use um captures or recaptures like Google and uh Cloudflare for example. And um yeah when you create a form um you can then um edit its blueprint to have um certain fields in it. for example. So, um if you want to let's say create a contact form that's like really simple um you want to have um for example an email field in it um then you want to have a uh name field in it for um should be a text field obviously with the um um with the name handle for example. Um, and then you want people um to be able to um send you a message through the contact form. Um, so then you use a uh text area field for example and um that's like super easy to um set up a in this case really simple um form. just hit save and um then you can um in this case we don't have any submissions right now. Um but you can um use those fields as well from the um on the front end of your site um whether it's antlers or blade or even if you use a JavaScript front end for example um you can submit everything through Ajax um through the API as well. Um, and yeah, then you can view submissions from from the control panel. Um, and even have logic in there. For example, we offer a lot of like built-in events um, for example, that are native Laravel um, events. Um, and one of them could be a um, form form submitted event for example. Um, and if you use something like HubSpot or a CRM or something like Mailchimp, for example, um you could sign up people to your newsletter um list or um send stuff to your CRM. Um that's all possible as as well. Um so um yeah um forms are like um can be really simple like I just uh uh showed with a simple contact form uh that just collects an email, a name and a message. Um but it could be also more complex with an image upload for example. Um or like uh sending stuff to um third party services or APIs as well. Um, so that's kind of like a thing that's um I feel like is a thing that Statamic um overall does. It can be really simple if you just need a simple CMS. It covers that, but um it goes all the way um to like serving uh large enterprises and um having like really complex um sites and apps and everything that falls in between. Um and um yeah, Statam is just really flexible when it comes to that. um from flat file to database. Um from one user to tens of thousands or like hundreds of thousands of users um it just like uh can kind of like adapt to all your needs. Um and uh your projects uh needs um so um yeah. Is there anything else? I mean like we can do like a Q&A. Um Josh, there was there was some chatter that there was a suggestion here. I'll put on the screen from looks like Antonio. And we saw that weird issue when you first tried to fire up the demo with serializable classes, which to be honest, as an experienced Laravel user, I hadn't seen before, but it looks like it's maybe something related to Laravel 13 specifically. And what people are saying in the chat is you go to the config cache file. Uh I think there's maybe a serializable classes option in there and you want to set that to true I believe is what chat's saying. So you could try that. Um just one hopefully that fixes things and if not there was also a couple suggestions from uh from Jack as to maybe things you might want to touch on as well. But uh yeah source uh crowdsource uh debugging for the win here hopefully. One sec. I'm going to try it. Yeah, give it a try here. Let's see what happens. one sec. Let me try again. No, not that one. What we have here still? Oh, somebody says it might need a artisan cache clear perhaps. Oh, I I did that. I did the the I have as an alias. Uh I did the optimize clear. It should like clear everything. uh PP autism. Oh, wrong size. Nope. That's all right. Um if you have any uh last uh or ideas there um if not there was yeah this message from Jack here uh mentioned uh in addition to forms you maybe showing page builder or asset editing or any of those sound interesting. Oh yeah. Um sure. All right. All right. just real quick um kind of like the almost the Q&A or like just showing like certain things that might be like uh interesting to the community or like the viewers. Um just the last slide of uh just the last slide of mine. Um if you want to give static a try um visit the the documentation um at static.dev dev. Um we have um videos and screencasts at um or like on our YouTube channel and make sure to join our amazing Discord server. Um it's a really amazing community. It's really welcoming. Um and yeah, if you just get started with Statamic um for the first time, then um yeah, it's just a great resource. Um so yeah. Um all right. um assets for example um are pretty neat. We also introduced um some um a feature like image um cropping um or like native image cropping um recently. Um so um this is like your um asset browser which is empty um right now. But for example, let me um look for a image that I can use. Um like this one for example. Um it's from the Laracon EU after dark party. Um so it's just like super easy. Um drag drag and drop. Um and um you can just like easily upload stuff. Um and you can also like um yeah edit image uh images for example. Um like with this picture for example um you can crop and set a um focal point for example. Um set the um the alt text for example. Um and yeah if you want to do the focal point um you can do that um yeah right from within the browser um which is pretty neat and handy. Um and um something we recently introduced um natively is um support for for cropping images um which is also um pretty neat um to do um from within your um CMS. And when you edit it, for example, um yeah, you can save it as a copy um or replace the um original. In this case, let's replace the original. And something that's also pretty cool um with Statamic are those two features, replace and re-upload. Um in this case, it's an image, but it could also be a PDF, for example. When there is like, let's say, an updated version, for example, um because you made a typo in the PDF, you can um replace it. Um, so it um swaps out the file um while um references to that asset for example on your site still keep working. So um yeah, this is a um pretty cool feature as well. Um and it's yeah just pretty neat uh pretty neat um to have. Um just thinking um whether there is more that I can show with um with like assets or like um images. Um obviously you can create folders as well. Um and um yeah just thinking whether there is more to show with assets. Um I don't think there is right now. um any suggestions from from from the chat or like requests even like if you want to see something specific. I did see I think a couple mentions to page builder Josh. Oh yeah. Um, if you want to set up a like really sophisticated page builder, um, it like takes a couple like minutes, like let's say like a couple minutes. Um, but if we want to just do a, um, really simple one, um, we can do that. So, we already have the pages collection here, which is, yeah, super simple right now and doesn't have kind of like the um, page builder um, yet. But what we can do is um edit the blueprint for it. And um like I mentioned um when I uh went uh over the slides is um the replicator field type and also the bot field type as well. Um and with it you can um yeah build um from simple to really complex um page builders. Um so let's uh just do that real quick. Um so um with the page builders you can um do the replicator one. Um let's just call it um replicator for now. Keep it really simple. And um the replicator field type in itself is um really simple um that you or it lets you um add blocks to it. Um and blocks can also be sets. I didn't go over the um idea of um sets or like field sets as of yet. So field sets essentially are um yeah kind of like um sets or like um they summarize or like let you put multiple things into um one field set that can be reused and can have like a lot of like um fields or like partials in it for example and you can use those um together with um with the replicator field type as well. Um so let's create a field set for example um let's call it um blog post create a field set and then um let's put a lot of like um a lot of uh fields into it. Uh let's do a um simple uh text um text uh field for example um apply let's do an asset one for example let's call it um hero image um and also put a bot field um into it. Um for the bot field let's call it um main content. Um you can have uh instructions as well for example um and markdown for um formatting is supported as well. So let's say your marketing people or content people um you want to like instruct them like what should be in there, what should uh they be aware of. um could be for example um they should keep it to a certain number of characters for example for SEO purposes like such things could be in there for example um we um want a couple of uh buttons for the bot field we don't want an H1 for example um because there probably is an H1 on the page already um but we want like an H2 and H3 and um I guess Yeah, block quote. Um, I think that should be it. Let's enable the reading time for example and the word count as well. Um, and the asset container is set. Um, so let's apply and save. Um, blog post heading, main content. Okay. Um, and then you can see that we have the blog post um, field set in here. Well, so when we um added the um page blueprint, we have um the replicator field and we have just created a um a set. So uh we can oops uh link a field set. We can link the um blog post field we have just created um to it. And when we go to the pages collection uh sorry and create a new entry we have the replicator field. And you can see that all of the um that all of the um fields we have just added to the um to the field set are now in here. And now you can imagine that when you have a lot of content blocks um built um you can just mix and match them, reorder them. So like in this case we only have like one or we just created one field set um that um we only have that one available of course um and we can collap uh collect collapse them and also reorder them um and um disable certain ones for example. Um, so the content is like still there when we save it, but it's not um rendered or like shown on the front page for uh on the front end for example. So let's imagine you have something like a sale that's like limited for a um certain like time. Let's say you have a like Easter is uh coming up. You have a Easter sale. Um, then it could be, for example, a banner or like some kind of um of content block in your page that says like, "Hey, we have an Easter sale going on." But like after a couple of days, Easter is over. You just disable it again. Um, and um, most sites have, let's say, a handful up to like dozens or like hundreds of um, content blocks um, available. And um when you build a page builder then for example you can um yeah just um choose between different like um calls to action like CTAs or like hero sections um newsletter signups um contact forms even um or like um yeah whatever um your like project or site like uh requires. Even if you have something hardcoded right now. So for example, let's say you have um everything in in blade views hardcoded. The content really is like in the views. Um then you can um kind of like make those blade views that you already have dynamic um and reuse like the view logic but have the content in there be dynamic um and coming from from Statamic. And you can edit everything in inside of the control panel instead of um yeah um editing the views themselves and um changing the content like in there. Um yeah, I'm just looking at the chat. I'm sorry. I'm not looking at the chat. It's all good. Josh, we're keeping an eye on things here. There was I think one more comment here. uh maybe just as like maybe something people want to see and then we could probably do just a little bit of kind of Q&A to wind down after that. But the comment here it looks like from David was is there is there anything that you can demo that's new in Statam version six compared to version five. So for an experienced Statam user what are what's maybe something you want to highlight in terms of new features? Yeah, that was the idea with the other um with the other app as well. But um I mean like the biggest change is of course the redesign. Um but something that I u mentioned um on the slides as well. So you can see up here um where there is like this uh little search input and it also says um command K. So this is the um new command pallet um we've introduced with Statamx6. Um and it's um aware of roles and permissions. Um you can navigate with it. Um you can extend it even um it allows you to add things to it like for example run custom actions or commands. Um so that's one of the new features. It's like similar to um to um yeah imagine raycast or like spotlight on on Mac OS for example. Um and it yeah it's kind of similar um to it. For example, we are um now on the um on or like looking at a publish form of an entry and um let's give it a title real quick. Um I don't know like um blog post one because I'm just going to give I'm just going to giving it a title because it's required um because when I hit the command K you can save and publish it from right here for example. Um, so when I hit uh save and publish, it's yeah, save and uh saved and published. Um, and you can also, um, since it's now like saved and published, like it's context aware, so other, um, options or like actions show up like deleting it, duplicating it. But you can also like quickly jump into the blueprint builder for um, this specific um, collection, which is the pages collection, and yeah, edit the blueprint. Um, and yeah, you can navigate um with it. Let's, for example, if you wanted to go to um to assets, you can um do that as well. Um, and this is, for example, one of the um uh features we introduced with Statamic um Statam 6. Another new feature is um native uh or like exactly this is a new feature um it's called elevated sessions um so that for like um kind of like um higher level actions for example like looking at a user because I was about to um enable two-factor authentication um it asks you to reauthenticate by um by uh re-entering your password. Um so this is also a new feature um the elevated sessions but also two-factor authentication is now um built in as well as pass keys. Um so yeah two-factor authentication um is now baked right into Statamic. Um and it even works with um flat file. Um so yeah for example with uh your phone or like if you have one password installed you can um scan the code and um yeah enable two factor um command pallet. Then one of the things um that you don't see um right now really um because it's kind of like under the hood is that we upgraded from view 2 to view 3. So everything you see here is now built with Vue3 and we also switched from VX to Pina. Um and one thing um that's also um brand new and the entire control panel is built with it are our new um UI components and we have an entire UI component library um that you can uh see at UI.statamic.dev. Um it's fully documented um using using storybook um and yeah we built the entire control panel with it but you can also use it as a developer when building add-ons um or custom field types for example. So um yeah we have a range of components available um for example um yeah like like let's have a look at what's a nice um thing to uh to look at um I don't know like if you build a custom field type for example um you have a text a text area and you want to like pass props to it like for example something like um like this is disabled um or you um want to have uh radio buttons for example. Um that's something that um is really kind of like we just build it for you with accessibility in mind as well. So you can like uh you can tap through it. Um, and um, if you build um, if you build something custom like an add-on for example, um, that's something that you can just reuse um, inside um, yeah, inside of your package. You don't have to um, think about design. You don't have to think about the logic um, for your UI. You can um, just um, use our um, pre-built UI components. Still, if you want, you have the freedom to um do something completely custom as well. Um but um yeah, most people don't really need this. So they can um reuse our components. Um so yeah, the command pallet, elevated sessions, two-actor authentication. Um what other things come to mind? I mean something we recently shipped as well is the image cropping feature. Um just thinking about um what else is new or like what I can um what I can show um any other ideas or like requests from the from the chat. There was one more in the chat from Jack says collection calendar mode is Oh yeah. Um so let's do um the products for example. Um I think there should be um yeah publish dates enabled um for it. Um hit save. Go to products and yeah you can see up here is the the calendar icon and um yeah if you have for example could be products um let's say you have a product um that is not yet released. Um when I edited or I configured the collection, you saw that when I en uh enabled publish dates, um it allows you to configure past date behavior uh past date behavior as well as uh future date behavior and future date behavior could um be set to private for example. So when you have a product, you can already create it and have it like scheduled to to be released. could be um the case with a blog post as well. Um but what's really cool about the um new calendar overview is just like instead of having this like yeah really simple um um listing um you can have a really nice um yeah calendar view. Um now like there are not a lot of entries um in this collection but just imagine like there would be like um scheduled things for example things from the past that you just have a really nice overview of everything. Um so uh yeah and you can toggle between uh the week and the month view as well. Um so yeah that's the the new calendar uh calendar view for collections. Awesome. Well, if there's anything else you want to touch on, Josh, but I mean, uh, despite the fact that the demo gods got us, uh, no problem. We were able to see so much. It's weird. We weird because when I did the um like created the the demo last week or like the idea for the demo, it was still because you I think you mentioned it was Laravel um 13 specific. I tested it on Laravel 12. even though we support Laravel 13. So, um yeah, I'm just Well, you know, sometimes even I I turn the computer on the next day and it's it's doing something different than it did the day before. So, who knows? At the same time, nothing was really lost there. We we were able to see a bunch of that stuff. And I think, you know, for for most of the crowd here, the the best suggestion is uh is uh you know, try it out yourself, right? It's uh completely free to use, even even locally with the with the pro version. There's no um restrictions on what you can do. So uh you know encourage everyone to uh to composer require it and uh give it a go. It's super easy like just go to statamic.dev uh have a look at the docs. Um, and it's essentially nothing more than uh composer require statammic. Um, or if you want to use our CLI um just uh composer global require statamic/ CLI um and then you can use the static new command to quickly create new sites and apps um through it with the whole like wizard like do you want to use flat file or database? Do you want to do you want to create a static site? um like um yeah, using our CLI uh just makes it um yeah, a lot easier and nicer to use. I agree. And there was there was some chatter um and I think there was it was it was great. There was a lot of like interaction uh with with the uh with the audience here, but there there was some chatter and people talking about I think at first maybe people less familiar with Static about you know the pricing model and uh you know what you maybe got with the with the core versus versus the pro model. Um and and I think you know Dave uh Dave Hicking here had a really great comment which I think kind of sums it up is like one huge reason in my experience to use Satamic is if you have a site where you need custom functionality and you can just do it in Laravel it would be easy. Static make is easy. I've definitely had that experience with some other CMS's where it's like you feel like you're you're jumping through hoops to do something that seems relatively simple. Um but uh and and in addition to I mean I think some of the examples you showed there Josh of even just something relatively simple of like uh say you're building a CMS for for a company you you know very common user say we have a staff page we want to show staff profiles or we want to we're a construction company we want to show uh profiles of of jobs we've worked on right and even just building out like you were showing there the collections and making being so easy right in the UI to do that I know like in WordPress for instance there would be a combination of a code change I need to make there in addition to probably a paid plug-in install to give me some of those fields that uh that are kind of made available kind of out of the box. So, um you know, right away I can kind of you know, very quickly see some of the some of the value that this brings in terms of like you know, how powerful the the back end of uh of the system is. Yeah, I mean just that you mentioned it like you can just go ahead like and really quickly like um create a staff collection for example configure its blueprint and say like um let's say um yeah the um staff like every staff member has uh I don't know like a uh a name and uh I don't know like a headsh shot for example an image of them just like scaffold everything like configure like um everything maybe like a short bio or something. Um, and all of a sudden you have your entire collection of your staff and can output it uh can output it like on your front end have a nice um yeah overview of all of your staff members. So it's like just super easy um and instead of yeah building everything yourself um it's way nicer to use a well-made um wellmade and well-designed product. And I think too having the um if you're using this at a company, maybe there's other people that or less technical people that you want to give access to be able to edit content. Being able to, you know, in the UI build that collection and, you know, add a staff page themselves, I think is pretty empowering, too, right? Less need for a developer to intervene with things is is nice as well. So I think there was a yeah a really good suggestion here um from somebody that said you know in terms of a suggestion of like how to get going is like you know choose something ambitious and an ambitious site concept and uh and try it on the free version you know and that's I think a really good suggestion sort of like the you're learning uh programming you know don't spend all your time doing tutorials try and build something real and see some of the real problems you run into and also you know maybe uh realize some of the uh the gains you can have you know from reaching for certain tools so I think that's a really good suggestion uh Margot did you have any uh any questions over there? Yeah, I guess um it was really awesome demo. Um and it was cool seeing the cool um features like the command pallet. Like are you using that a lot in your day-to-day? I feel like bringing in a lot of the the feel of searching for things and navigating easier. That was that was cool to see. Um I'd imagine that's something that you you use like all the time. Is that right, Josh? Um like you mean the the command pallet and stuff or like Yeah, just like to quickly navigate. I thought that was a really nice touch. So um for I mean yeah use it like kind of like depends on the perspective. If you're a um developer I guess you use the control panel less than your actual like end user. Um but still like I really enjoy those features um because like I'm really used to for example just the command space to bring up raycast for for example. So, it's really nice um to have something like the command pallet to quickly navigate the uh control panel. Like as a dev, you usually like try to avoid leaving your keyboard um and use shortcuts for everything. Um so that's really nice. um of course but um yeah like like I said earlier like static like um offers um a lot of things for both developers as well as control panel users um which are not like developers or like techsavvy um so uh yeah that's um yeah I just like static is like just batteries included in a way um so for example um when you I don't know like um built something like forms for example as a deaf um just like the form handling the saving up of submissions is just like super nice and for um people in marketing for example it's really nice that they don't have to do anything um by themselves really and just maybe if you set it up that way as a dev they have everything in HubSpot or in their like CRM of choice um without them like having to do anything. They don't need to like export anything somewhere and import it somewhere else. Um if you as a dev for example um hook it up um every like form submission for example just just gets uh sent to their CRM or like um their like mailing list or something on Mailchimp. Um so that's just really nice. It serves like kind of like um yeah both parties or like both audiences in a way. Um there's usually always something that makes deaf work easier. Um and also something that makes um yeah um regular non-deaf people uh lives easier as well. Yeah, that that finding that middle ground that's really uh really tough spot to to be, right? Yeah. Like that's totally my experience too. It's like it can be really easy for developers and like you know a pain for less technical people or you know vice versa, right? So being able to kind of strike that uh that middle ground is a real uh a real tough one and it seems like you know statics done a good job of that. So very cool. Um there was a there was some questions about you know when it comes to like the the visual uh like and probably more so like what you see on the front end right there were some questions about is there concept of theming exist? There's a question here looks like from Bernard any visual site builder in the future like WordPress Gutenberg or Drupal canvas. Um, can you touch on Yeah. What does what does it look like in terms of building what the user would actually see on the front end, Josh? Yeah. Um, we have the live preview um feature as well. So, um, also not in this uh demo uh site here right now. Um, because the live preview obviously depends on the like views you've uh you've built um in your app. Um, then you have like the visual side by side. um yeah editing experience. So when you hit the live preview here for for example and you have a um more complex site. This is like a really simple um really simple um example right here. But you can um yeah just visually like um edit everything um like uh this is your live preview in action um and save it and um yeah then it's um yeah live on the front end um like I showed earlier you can build like page builder experiences with content blocks and everything um there is no like um actual like wizzywig like full um visual page builder as of yet. um like uh for example something um like web flow um offers but um something like web flow has like other limitations um and it's um it doesn't give you the freedom of like um yeah um being in control of the entire code. Um but there is no um yeah visual page builder experience as of yet. Um what you would do is have a page builder um with content blocks and use something like the live preview for example. Um theming um you just mentioned um theming is possible um with the um like in the control panel um when you go to uh preferences you can um uh choose between pre-built themes but also create custom themes. Um this is for the control panel itself. Um and um the control pu uh panel also supports white labeling. Um so if you build something for a client for example or even like internally and you want it uh to be more in line with um with your um corporate identity for example, could be logos, could be like uh colors. Um you can um configure all of that. Um when it comes to theming in the front end um we don't like limit you in any way. Um so that would be something that you um that you build yourself. Um it could be a simple when you speak um of theming as a light light and dark mode. Um but it could be also like entirely like different themes as well. Um but um yeah we don't like give you like any limits when it comes to this. Um, and you're free to to edit the code or like um do the front end however you like. And I would be writing uh Tailwind uh CSS then. Is that is that correct? I'm building up my also not limited. Um like we still uh or like I still know people that um build new sites with Bootstrap still. I mean like Tailwind is kind of like the default and we all love Tailwind. Um, and it um just like uh has a is a joy to use. But you're not limited to that um in any way. If you prefer vanilla CSS and JavaScript um go for it. Um but um yeah, by default um static um ships with Tailwind. Um but if you prefer anything else um just just use it. That's really nice to know, especially too if you have people are looking to maybe migrate an existing site, they uh they don't necessarily have to to move to till at least not right away as well. So, lots of options there. Awesome. Um I don't know. I think I think I'm out of questions. You have anything uh left there, Margot, in terms of questions? No, I think I'm good. Looking through the chat, a lot of the stuff that uh we were kind of asking here has been also been answering the chat, too. And thanks so much, Josh. It was such a great demo and just seeing all the cool things that are happening in Statam 6. So yeah though I thought it was a great presentation and yeah maybe uh one kind of wrap-up question for you Josh is like in in terms of all the the new stuff that uh that came in in Statam version 6 what what feature or thing are you most excited about or we were most looking forward to to that release. Um I would say like really from like just as a developer the view 3 uh upgrade as well or like together with the UI component library. Mhm. Um, when it comes to the control panel like itself, I would say the command pallet um, is really nice because it's just like a pretty cool feature and just like makes like navigating the entire control panel or like running custom actions as well like just really nice. Yeah. Also, CS definitely modernizes things. I think that's the the command pallets a thing you're seeing more and more, right? Not just in desktop applications but in a lot of web applications as well. So, yeah, definitely make gives it that nice modern feel, too. So awesome. Well, uh like uh like we said, thank you so much for joining us today, Josh, and and sharing all of this and like we said, you know, I think the best way to uh to get familiar with Static and then and kind of determine if it's right for you is go ahead and install it and try and build something with it and uh and there's lots of resources out there if you have questions along the way. So, uh any final thoughts for you, Josh, before we uh we let you go today? Um yeah, if you want to give it a try, um it's free to try like you um just said, just uh yeah, create a create a project, dive right in. Um and if you have any questions, um feel free to reach out um to uh to me or join our Discord server. Um it's a super um welcoming uh community. Um and um yeah, that's that's pretty much it. I would just say uh give it a try if you if you haven't um tried Statam before um or if you haven't tried Statam in the last I don't know like two three years or something um just give it a try again because yeah especially with V6 and the major redesign and a lot of new features um it's um yeah even better. It's not your grandfather Statamic as as they say. So, do check it out for for experienced and and new users. Awesome. Well, thank you again, Josh. Uh enjoy the rest of your day and we'll uh we'll talk to you soon. Thanks for sharing. Thanks for having me. Thanks, Josh. All right. And with that, Margot, we've got just a little bit of uh community stuff to wrap up before we send everyone on their way for the rest of their day. So, what do we got here? That's right. So, for our next meet up, you can join us on April 28th. We have a guest speaker, James Acon. So, very excited to have him and join him uh for next month. Um, and if you haven't signed up for our giveaway, our giveaway is now open until April 7th to win one of two Jet Brains IDEs. So, make sure to scan the QR code and we'll announce our winner on April 7th. And to stay connected and involved with what we got going on, please follow us on X if you'd like at Laravel WW meetup where we'll post all the announcements of our future talks and what's going on. It's also a great way to reach us if you have any questions or if you're interested in speaking as well. And then you can also follow us on Blue Sky Laravel WW Meetup. And then for all your Laravel worldwide meetup updates, you can go to the official website at meetup.larabel.com and you could sign up for our email subscription list to get notified for every meetup we got going on moving forward. And we'd love to chat about what talks you're looking forward to next. So make sure um if you're a speaker or anybody or if you are looking forward to a speaker to speak about something in specific, make sure to reach out. We're happy to to take a look and see what people are interested in the community. Um and you could thank you for catching us on YouTube as well. So, uh, we're on the YouTube channel and with all of our previous live streams, you can go and check them out, especially this one afterwards. You can check take a look at all the links that Josh was talking about during his talk. You can find them in the description below after the meetup is over. Um, and we really hope that you enjoyed this meetup and thanks so much for tuning in. Yeah, lots of fresh content on the uh, Laravel YouTube channel uh, daily and weekly, so be sure to check in on that regularly. And uh thank you once again for uh Josh for joining us today and sharing all the new features in Statamic V6. And thank you everyone for tuning in and uh and checking it out. Uh with that, Margot, any uh passing or final thoughts for you before we uh send everyone on their way. I can't wait to try out ZX 6 and see what all the new things that are coming out. So um yeah, really looking forward to it and very happy that Josh was able to join us today and do the live demo. All right, well thank you everyone again for tuning in. Thanks, Josh. And uh enjoy the rest of your day and we'll we'll see you on the next one. Have a great day, everybody.