Yeah, is there anyone from Pittsburgh in the room? Native, local? We have no experts. My parents are actually, we'll do a fun fact before we start. My parents are both from Pittsburgh and I've been coming here since I was a little kid, but I've never spent time downtown. But we've always talked about the trams that go up the hill and down the hill across the river and it's beautiful and so that's where this tram comes from, the logo comes from. So if anyone's here and has free time, I recommend it's a good tourist attraction. I can't say I've personally enjoyed it because I haven't done it yet, but I've heard great things. All right, good morning everyone. Welcome to Drupalcon day two. I am very excited to be here. It's great to have you all in the session. I know I'm competing with Dries during the public board meeting, so I appreciate you all being here. It's very hard to compete with him, so I appreciate the time this morning. I have very exciting honor to talk about all of the amazing things that Drupal is and, you know, we'll spend some time together.  I'd love to give you a huge shout out and thank you for all that we've done to contribute to the amazing Drupal community. A quick note about me. I'm Tammy Perlstein.  So I grew up in New England and I've actually never gone skiing or snowboarding, so please don't hate me for that, don't hold it against me. I'm more of a beach person, but I do find that it's a bit of a fun fact. I love to cook as well, so if anyone is a cook in the room, I love to share recipes, learn from each other. The best recipe I have actually I learned from a friend of mine with native Italian parents and I now make the red sauce that he taught me back in college. So always great to share and learn from each other in that front. And I'm also a bit of a newbie to Drupal. I've only been at Aquia for about a year and a half, so still learning, still immersing myself, and I like to think that this community with all of the incredible things that have come out of it, you know, there's always more to learn. So being at my first Drupal con here with you all, I'm very excited to just learn and chat and make some connections that we can carry forward. And I'm always a resource for you at Aquia and otherwise, so if you need anything, you can always reach out to me on LinkedIn and buy an email. So if any of you were at the juice note yesterday, you had the pleasure of hearing him talk about all the innovation and jumping S curves and the fantastic analogies that he used to describe, you know, all the things that Drupal has accomplished as well. And I'll be following on that same theme, talking a lot about innovation today, innovation across the market, innovation in Drupal's history, as well as innovative customers that are doing cool things and putting these innovation practices into driving some business outcomes. And then finishing out with some innovation projects that are going on currently that you can lean into that you can get involved in and contribute to as a community member. So jumping right into things will take a look at the market as a whole and all the innovation that's come out over the last couple of years. And now I won't be going back to the time of the dinosaurs because that would be far too much to even try to cover in a session this morning. But we'll start off with another monumental year, which is 2001. Can anyone guess why I've picked 2001? Anyone have a guess? Good guess, a little farther back. It was actually the first year that Drupal was released to the public. So very interesting, very monumental. The world was changed, you know, maybe not as big as dinosaurs, but I think that it's pretty cool. And we'll make it all the way from 2001 to 2023 today, and then we'll look a little bit forward as to what is coming out in the next couple of years and even, you know, in the next couple of weeks. And what's really interesting is looking at 2001, you may think, wow, so long ago, so much has changed. And what's been really incredible about Drupal and actually pushed a lot of its longevity forward is that it's focused on a singular problem. And that problem is that individuals want to interact with the web and they want to deliver really great web experiences. You know, while that problem existed 22 years ago and it exists today, while having enhancements added to it as well, that problem will still exist in 22 years from now. And as we're expanding across digital channels and embracing new channels, that focus has really at the center of Drupal really provided an opportunity to build a foundation upon for future innovation. And while it's not just that focus on a problem that's supported Drupal success, it's also this commitment and dedication to innovation and moving at the speed of the market. So not being laggards or saying, you know, not looking forward, how do we look to what is new? How do we identify what that S curve is as Strice was talking about and jump on the bandwagon soon. And that commitment and dedication has really proven Drupal's longevity. So we'll take a look at 22 years. Looking back at 2001, while this is a very overwhelming slide, it's meant to be. And while this doesn't even capture all the innovation across 22 years, I feel like this is a good call out with some landmarks that we can attach ourselves to that provide some clarity around what we've seen over this time. So like I said, 2001, Drupal was released to the public 2003 safari and WordPress are launched. 2006, jQuery is available. 2007, the first iPhone came out. I know I was pining I begged for the first iPhone. All cool kids had it. 2008, the first Android phone is available as well. So following right on the tails of Apple. GitHub is launched and responsive design is taking off. So big year 2008. 2010, AngularJS is open sourced. From 2010 to 2013, we have bootstrap 1.0 to 3.0. And then from 2011 to 2015, we have Spratcore becoming EmberJS, and then EmberJS 1.0 to 2.0. In 2012, Composer is released humongous milestone. And in 23, React is open sourced. Moving into 2015, we have another big innovation here. We have GraphQL, JSON API releases, and the Apple Watch, which many of us have become super reliant on it. I know I'm addicted to checking my steps, making sure I hit my milestones and competing with all my friends. In 2019, PHP 8 is released. And in 2020, we have chat, GBT and AI changing the world, along with Drupal 9, also changing the world. 2022, we have Drupal 10. And in 2023, we have Modic being re-released as an open source platform back into the community. So like I said, this is really just a snapshot of what I meant to depict over the course of time how much has truly changed, going from not having cell phones to having a internet, a web in your pocket, something that you can use everything for. I remember my math teachers, it's not a strength of mine saying, you know, you really need to focus on math because you're never going to have a calculator in your pocket. And I laugh because we do. So it's good to take a moment to pause and reflect on how much innovation really has taken place. But like I said, don't hold me. I may have missed some innovative moments in your history that you think are really pivotal to your organizations or what you've used Drupal for previously. But it's important to note that there is an expansion of these channels, right? Drupal was founded on the web platform mentality, the framework, and we've really expanded across all of these channels across Amazon, Alexa's, the IoT, digital signage, kiosk. I mean, it changes by the moment. So it's good to reflect on where we've come and where we're going. All this to say that innovation really is happening at a staggering rate, and we're at a pivotal time in history. So now that we've looked at the market and how it's progressed, it's even more impressive to remember Drupal's commitment. And what I mentioned at the beginning of the session, which is the problem that Drupal is focusing on and delivering those web experiences, which are expanding across digital experiences, and that commitment to innovate at the rate of market. And the remassive advancements within Drupal itself over the last 22 years. So let's take a trip down memory lane. This is one of my favorite pictures of Dries in his dorm room, some brair on his head, young, sprightly, very excited. And as I said, 2001, Drupal was released to the public, the world would really never be the same. And initially, Dries built the software as a means for communicating with his friends. As you can see the picture here, chatting, hanging out, just a means to connect. And one year later, Drupal released to the world to let others extend the platform, contribute to the platform and leverage it for a multitude of uses. And with that, the Drupal open source community was born. And with one line of code written at a time, Drupal has become what it is today and really started to grow. So fast forward to 2007. This might be a little bit of a biased moment in history for me. But Drupal really hit the main stage when MTV came knocking on Dries's door asking for support to launch their new Drupal site. And huge MTV fan personally, I was watching all the music videos growing up. So pretty cool fact about Drupal. But what this opportunity provided was actually a light bulb for Dries to say, Hmm, I think there's an opportunity for an enterprise to come in and leverage Drupal to expand and grow and provide a web experience for a multitude of customers, a wide breadth of customers and a diverse amount of customers. And Acquia was born. And Acquia became what Red Hat did for Linux, which is that it provides an opportunity to extend the power of Drupal and contribute that power back in to the community. And Acquia remains the number one corporate community, the corporate contributor to Drupal today. In January 2011, Drupal 7 was released, which was a revolutionary release for Drupal, the biggest release up until this point. And it was really revolutionary release for two reasons, because of the size and the diversity of the community that was growing at an exponential rate, and also through the strong formation and coordination across usability, accessibility, and the design teams, Drupal 7 was able to address a lot of the accessibility limitations that Drupal had had previously. This opened up Drupal to a wider audience and really pushed for that open web platform perspective, which we bring true and we talk about all the time today. So there's really, like I said, was revolutionary for those two reasons, and really opens up the opportunity for a more diverse audience to start to use Drupal. But also in 2011, in July, Drupal con assumed the formal name of the Drupal Association and began acting as a legal body to support Drupal.org. So since 2011, we all have seen what the Drupal Association has been able to accomplish by growing alongside the Drupal project. And the goal really of the Drupal Association is to make Drupal the biggest and most popular, most adopted CMS on the market. And they're doing that by aligning to the community needs and the project needs. And while the DA initially focused on incredible events, Drupal con events, like this one that we're at today, they're really hitting their stride in terms of what they're able to give back to the community, focusing on contributions and leveling up Drupal.org, focusing on community cultivation grants, as well as global training days to really expand the breadth of Drupal users and the way that Drupal users are using it today. So I just want to say a big thank you to anyone who is a member of the DA or has, you know, we all contribute and we all experience the breadth of what they deliver to Drupal. So huge shout out to all they've accomplished and what they've been able to help to do support the community. And in November 2015, Drupal 8 is released. So this is the biggest update since, you know, the time of when it started. And this really put forth Drupal as a head of the market as a competitive open source CMS that everybody should be looking to to deliver really innovative innovative experiences. And it was ahead of the curve in terms of decoupled websites specifically with built in Rust API for all content, a system to query data from Drupal, a big pipe implementation and improved content editing with WYSIWYG and preview. This really changed the game for how users were leveraging a CMS. However, the decoupling revealed that there was a need to investigate better ways to deliver data on the client side. So as pages and applications became more component driven, the complexity of the queries performed and the demand on those queries increased. So Sebastian Seamson proposed using Facebook's GraphQL to solve this challenge. And luckily for Sebastian, he was right. Because as we know, GraphQL as a query language for APIs makes this quite easy. It's able to evolve APIs over time, limit the number of round trips, and enables powerful developer tools to expedite your workflows and make remove friction make things more seamless. And today, GraphQL is an actively maintained and highly popular module. But by 7 2017, the CMS market was pretty busy. There were a couple key players. So it was hard to differentiate and stay ahead of the competition. However, unlike other CMSs, Drupal took the approach of being API first, not API only, which really set them apart from the competition. And an API first approach, as we're all familiar with, doesn't limit you to a coupled approach. And it also doesn't limit you to an API only approach. So it really enables you to leverage the best of both worlds. And it doesn't limit you to only headless CMS that we have on the market today. And it doesn't limit you to some of those monolithic players that have been in the market for a long time. This was a major turning point for Drupal, as it can now be leveraged to support multiple architectures within your own organization or cross organizations for a diverse set of needs and diverse use cases. So understanding your project, your requirements, who are your users, Drupal can really meet all of your needs. And on January 7th in 2019, all the work from the previous three years on JSON API culminated in a JSON API 2.0 stable release. And the 2.0 release marked the start of the modules moved to Drupal Core. And after countless review, countless improvements, the module was finally committed to core. So humongous accomplishment. It was a major milestone towards making Drupal API first. And it was no small accomplishment. Huge thanks to Wim, Gabe, and Matteo. It was a lot of work from the beginning to the end. It took 28 months, 450 commits, 32 releases, and more than 5,500 test runs. And this is just yet another example of Drupal's commitment and dedication to delivering innovation that's game changing, that's actually going to be applicable to your real life projects and giving back to the community so that other community members can leverage that innovation as well. And finally, in 2022, Drupal 10 was released, humongous excitement. And this is the newest major version of Drupal available today with some key innovative features. First, the Claro admin theme. It's a modernized backend with really fresh and updated look. And it actually replicates the power that Drupal holds. The previous themes did not necessarily depict or invite new Drupal users to leverage the power that Drupal has. So by updating the backend theme, this really invites new users to see and leverage the power of Drupal. The second is a sleek and modern Olivero default front end theme. And as I'm sure we're familiar, this is a beautiful theme right out of the box named after Rachel Olivero, a very committed Drupal community member to accessibility. And it features many accessibility enhancements for Drupal 10 that work for everyone. CK Editor 5 is a refined content editor experience. And our starter kit theme generator for Drupal 10 as well. So as we know, Drupal themes are not usually built from scratch. They're built on top of a basic theme. And with Starter Kit in Drupal 10, you can create a fork from a compatible theme and work on your copy from there. Which ever version you copied from is automatically retained. And then you are then responsible and accountable to review and apply those changes further enhancing stability. And lastly, Symphony 6.2 and PHP 8.1, these upgrades improve the Drupal experience by enhancing support, boosting site performance, and a more modern UX for developers who, for UX developers and also non-technical users. So further expanding that audience again. So as we look to today, 2023, there's some pretty incredible accomplishments that I just walked through. And while I know that not everybody may have all of the experience in Drupal, there's so much room to grow. And I wanted to call out a couple of stats here that I found really powerful. The first is that one in 10 sites today run on Drupal.  The second is that we have over 50,000 contributed modules increasing the extensibility of Drupal every single day. So thanks to our agencies, our partners, our community members that are constantly innovating and contributing back to the community so that others can leverage the same power and apply in different practices as well. And the last is the diverse and inclusive community that Drupal has you know grown and fostered through many years promoting open web and accessibility for all. This is a major, major accomplishment to have a community that is you know so interactive and engaged that we have events like DrupalCon all across the world. It's a testament to the dedication that each of the Drupal users and members feel and the loyalty that we have to Drupal.  It's astonishing what we've accomplished in just 22 years so I'm excited to see no pressure what happens in the next 22. So it's a lot. We've covered a lot of ground, there's a lot going on, I get it, but I wanted to just mention and reiterate the points that I mentioned before which is the focus on the problem needing to manage content, manage experiences across the web and those new expanding digital channels and the dedication to the rate of change in the market. Like I said I can't imagine Dries in his brightly college dorm thinking about all that has been accomplished but it really is an incredible accomplishment. And while we've covered some really innovative moments I think it's even cooler to talk about customers that are using this in practice and doing and delivering some really incredible experiences today. So I wanted to see if there are any New Yorkers. I know there's no native Pittsburghians but any New Yorkers in the room. Anyone who's been to kind of, okay, anyone who's been to New York, visited New York, taken the MTA. Yes, we have a couple more people. Yes, we don't necessarily want to live there but we love to visit. Great to immerse ourselves for three days. I can't do more than three days, it's like Vegas. So if any of you have been to New York and you've experienced the MTA you know that it is central to the city. It is the lifeblood of the city if you will. As much as people want to walk 40 blocks is not manageable. So the MTA set out to improve its customer experience and to create a cohesive user journey across all their touch points and channels which you might think for the MTA they're not super innovative. They might not be doing that cool of stuff. You're very wrong. They were actually looking to provide every commuter with a unique experience across their platforms as they're looking to leverage MTA in every single facet of their daily life. Whether it's getting themselves to work, getting to you know hang out with friends, getting to see family. I mean it's really like I said the lifeblood. So by leveraging decoupled Drupal and aqueous solutions the MTA can use digital signs across all of their locations powered by centrally managed content in Drupal to deliver a well rounded customer experience. And to supply the digital signage they really need to focus on delivering content, collecting content from third party and external sources and then pushing that content out in real time. And a great example of this is what they were able to do with their countdown clocks. So in order to do this they had to collect data from Drupal as well as other external services and collect that data and then in real time push it out but they also needed to attach Bluetooth beacons to the trains themselves in order to ensure the accuracy of the arrival and departure times. So a pretty robust and complex project. But like I said Drupal really acts as that gatekeeper of all of the content and data being able to pull in APIs and push out data and all that content in that real time which is you know when you're looking for a train and it says seven minutes and it's actually 15 that can do real your entire day. So as if this wasn't already a complex project the MTA wanted to layer in a layer of automation. So with Drupal content modeling the MTA was able to automate the distribution and management of transit messages tailored for each of their platforms. I want to pause because that is pretty epic. If you think about how many platforms, how many signs, how many countdown clocks are in New York and you're able to deliver personalized data and content to that specific platform that is a humongous speed. So very complex very challenging but they were able to do it. They also built their front end experience using ReactJS. So by adopting an approach that they call progressively decoupled Drupal the MTA was able to build a reactive application within a Drupal theme. So the data displayed in the front end can still be informed by the Drupal content model while maintaining the flexibility of a decoupled solution. Like I said they just really made this as complex as they possibly could but they drove some really impactful results. So with Drupal the MTA was able to streamline their content management across our digital signs all of their stations to ensure an efficient and effective content update process. With Drupal as their single CMS any user within their organization can go in and make those content updates. There's no relying on the development team to push out content updates in real time. That would cause friction that would delay the real-time nature of their countdown clocks and messaging. But most importantly by infusing the power of digital signage into their station countdown clocks the MTA is making their customers their priority. So the customers build loyalty with their organization and know that they can rely for trusted information. Transit information news I mean all the things that come with travel especially in such a high volume and high stress environment. So they're really putting their passengers at the forefront of what they do and looking at what their passengers need from them. So they're really setting the precedent for how an organization whether in transportation or in e-commerce or in Gov can take a perspective of how do I put my customer or my constituent or my passenger at the forefront of how I build experiences. And it's really a great example of how we can modernize an industry that you may not think might be the most innovative or the most cool or doing something that's unique and different. Pack 12 is another customer that I love to talk about. If you're familiar or unfamiliar they are a collegiate athletic conference and they really wanted to connect their applications to provide an incredible customer fan if you will experience across their digital landscape. And they had an array of apps but they really wanted to be the central source of truth. So for any games any playoffs whether it's you know baseball or football or basketball you name it they wanted to be the hub for where you got information. But their challenge was that they had a ton of applications across iOS, Apple TV, Viya, Android and they had just rebuilt their entire website pack12.com. And applications present content that's super dynamic. It can be team schedules, video content, information from their social platforms. So it's really highly dynamic it's changing all the time and changing almost in real time for games that say go into overtime. That impacts the team schedule. And connecting all these apps was really a big challenge they were looking to overcome. But it was really to deliver a accurate experience for their fans so that their fans knew they could rely on the information they were receiving from pack 12. So pack 12 leveraged headless Drupal in order to connect to and power its array of fan-facing applications. Leveraging the power of APIs. And Drupal really acts as that central nervous system so powering everything that is externally facing for that fan experience. Orchestrating various microservices and the flow of key data. As well as powering and inputting more of that content to make it more engaging. So the team was able to recreate a large number of custom APIs for their events, for their videos that were on demand, as well as their content utilizing REST endpoints to query GraphQL as we mentioned before. And migrated and converted existing React components to improve their existing architecture and provide blocks for use in layout builder. What they delivered was truly astonishing. They were able to launch 3000 plus landing pages for all of their pack 12 conference events in just five months. That is a very large number of sites in a very short period of time for an organization like pack 12. They were also able to migrate all of their existing video and can now host all their pre-game live and post-game video on their site. Which led to in just the first year doubling the number of hours that people viewed video content on their site. So when we look back at what their challenge and what their goals were, pack 12 wanted to be that central hub for their fans. They wanted to be that central source. And with Drupal in a decoupled fashion they were able to achieve that goal. They were able to double the content at the time that they were consuming content on their site for their fans. But that's just one metric that they used to measure that engagement. So as we're looking to leverage Drupal in a more innovative fashion, the theme that we're seeing run through here is putting your customer first. And really understanding what they're looking for, how they want to consume the content, and how Drupal can help your organizations or yourself to push out that content in a really dynamic way. So this is one of my favorite brands, and it's not my favorite brand because I'm a motorcycle enthusiast by any means, but I think they're doing something really cool and disruptive in the market.  Yes, I have one on the back. So are you familiar with Livewire at all? You are. Pretty cool, right? Yeah, they're awesome. They're actually an electric motorcycle brand. So when you think about motorcycles you don't typically think about being electric, but this is again another example of a company that's disrupting the market. And so I love to talk about this brand and what they were able to deliver with Drupal. So Livewire really wanted to deliver a media-rich, engaging experience on their site that captured the vision of their brand. And if you've ever looked at their website before for the person in the back who's familiar, they have a pretty cool website that does actually do what they set out to do. But they were challenged because their previous site was built with a ton of custom code, making it incredibly challenging for their content editors and content authors to make updates to content. There were a lot of bottlenecks. There was a heavy reliance on the developer team and that just created friction across their organization. So by shifting to a headless implementation, Livewire was able to integrate Drupal into two different versions of their site. And there were two really big impacts that came out of this. They were able to increase their overall site performance. So you're not seeing a lag time and load. You're really making sure that you're not seeing a bounce rate, that your people that are coming to your site are going to stay on your site. And you're also boosting that customer experience and satisfaction as a secondary win and benefit from that. So the teams were able to leverage Drupal's API first strategy and framework to take a content as a service approach, seamlessly integrating the powerful Drupal CMS into their existing front end web application. Like I said, if you've gone to the website, feel free to pull out your phones once we had out of the session. Just take a look at their site, scroll through. Super engaging. They were able to reach their goal that they had set out to embrace their brand and make sure that they were conveying their brand across their digital landscape. But they were also allowed to break down or they were also able to break down those silos. And when we think about the content editor, the content creator, it's super important that they have the access that they need to optimize content. When they know content is performing, they want to repurpose and reuse that content. So how do we put the power back in their hands to enable them to drive really meaningful impacts that impact that customer journey? So hugely innovative in their own industry, but innovative in how they use Drupal in terms of leveraging a headless decoupled solution, but breaking down those silos and removing friction internally so that developers had time to do the things that they want to do, which is focus on innovation, focus on cool projects, focus on testing new technology and figuring out how they can work that into their own ecosystem. And the results here at Livewire drove pretty impactful as well. They had a one month implementation, fantastic on time, wonderful. We love to see that. And they were also able to launch five global sites in just one month as well. And then my favorite stat from them is that they actually launched a pre-order page for one of their new bikes that they were releasing into market. That bike sold out in minutes. So we're seeing real business impact from leveraging headless Drupal, from being able to give the power back to the content editors and allow your developers to really do what they're meant to do. And lastly, we'll talk about Leica geo systems. They're the leading manufacturer of precision laser technology for measurements in a wide array of architecture and construction projects. So Leica's challenge was that their e-commerce store was active in multiple countries and needed to be translated into multiple languages. So when you think about what that looks like, it's a multi-site initiative, managing multiple sites with all the complexities that come along with that. But what's really challenging for Leica was that their product content and pricing changed dramatically across those sites in terms of currencies and in terms of sales, etc. So it was a very dynamic site with very dynamic content. And the challenge was really to make that content and product management easier for the Leica team and support the opportunity to expand into new markets, expand into new areas of the world, and be able to support the teams to be able to do so easily. There are specific requirements where that they would need to support 10 countries with a regional, a global regional perspective as well, six different languages, and they had and leveraged tons of third-party integrations, which is something that we hear all the time, and it's something that, you know, Drupal is very strong at. So I moved to Drupal in combination with some smart choices in terms of module support and customization, simplified many aspects of what the Leica team was looking to achieve. They focused in on configuration management, one database to rule them all, one commerce install for multiple stores, one page in multiple countries with multiple languages, which was humongous for a team efficiency, and they were able to future-proof and achieve longevity with Drupal. And what they were able to achieve was that they were able to, leveraging the built-in commerce functionality, deliver highly customized and fantastic experiences for the Leica geo-system teams. It was imperative that their commerce was their commerce back-end be able to be accessible by their marketing front-end, and the third-party services that they had chosen to work with were all accessible within the Drupal ecosystem, making that extensibility very simple with minimal custom code needed. And finally, for a global brand looking to expand into new markets, they were able to leverage the state-of-the-art translation system in Drupal that is provided out of the box. So when you think about somebody who has a multi-site challenge with a global reach, that multi-site and multi-lingual benefit Drupal provides is really impactful. So a couple of different customers doing a couple of different things and innovating in industries that we may not hear or think of very often, but I think this is a really great opportunity to see the impact of the innovation that Drupal drives across a wide set of verticals and a wide set of projects and driving some really impactful value to business and to team members across marketers and content creators as well as developers. So to summarize, we've taken a look back through time, we've taken a look at the market, we've taken a look at Drupal and innovative moments, and we've taken a look at some customers. But let's talk about what's upcoming, what is exciting, what's new, what can you get involved in, and how do you get involved because that's the best next step for you. So I know we've all heard and probably played around with ChatGBT by OpenAI, and I know that I oftentimes will try to play with ChatGBT and I'm told, you know, I'm not able to access, it's too high performance, so I have to come back later, but anytime I can get my hands on it and play around with it, it's super cool. And I like to say ChatGBT really is the new kid on the playground that everybody wants to play with, and so it's just in super high demand. But Dries mentioned this in the Dries note yesterday, if you were able to join, showed a demo of what ChatGBT is able to deliver, but I think this is a really good opportunity to highlight what is going on in terms of innovation with AI for Drupal. So there's a lot of discussion around what this means for, you know, not just Drupal, but for the CMS market, for the world as a whole, but Valeer specifically jumped right in with some foundational features that they felt would enhance ChatGBT specifically for Drupal. So OpenAI provides a handful of services to integrate with the API, and specifically they focus on generating text, generating images, analyzing text, and running moderation, scoring on that text, and then fine tuning the models. But Valeer was able to focus on five key features and really drill down into what those five key features should be for the first iteration of this module. And the features, I'll go through a little bit one by one, what it is and why it's impactful. So the first is Prompt Text Generation Explorer. So what it is, if anyone has interacted with ChatGBT, anytime you type into the little box at the bottom, you're prompting ChatGBT to talk with you. It's how us humans talk to AI. So why does that matter? It actually provides an opportunity for someone to leverage and prompt ChatGBT right in your workflow, no more switching back and forth between the platform and your Drupal site. The second is Content Generation. What this is specifically, I've included a short video for you so you can get hands on view. It actually allows you to generate content for any content type that has a title and body field and generate images for detected image fields. Why does this matter? Well, actually generating random content is super helpful for people like myself who oftentimes get writer's block. So if I'm able to just drop in a quick prompt and say, I need some bullet points on how to make lunch today. It's going to start to spur that creativity. It's going to start to give you a starting point where you can really get into the flow, get into your creativity and deliver meaningful content without having to waste all that time getting over your writer's block. So the third is CK Editor integration. What it is, it's a button in the CK Editor that lets you ask OpenAI or chat GBT a question and retrieve text back. Why does this matter? Well, it can be used for content editing when you want to have a quick one liner or introduction. If you're looking for a quick snippet for a header, it's really great for that use. And it also helps with writing and getting those prompts flowing and really helping you to fine tune that content rather than starting from scratch. The fourth is log analysis. What is it? It's a log viewer in Drupal that uses OpenAI to explain, if you will, the error that you're seeing. So for somebody who, like myself, is not a technical user, so to speak, it helps me do some troubleshooting around what the error might be so I can work to overcome that error. This proof of concept, like I said, is really geared to those non-technical users. So a great way to expand Drupal users into that non-technical site builder marketer persona. And last, text embeddings. So when content is published, it's analyzed by OpenAI and has a series of vector data returned. Essentially, the embeddings feature measures the relatedness of strings. Why does this matter? Well, these calculations will actually help to augment other parts of the system and they can be used as a means for bolstering search and relevancy in addition to using alongside popular modules like Search API. So again, this is really about simplifying that content creation process and driving more meaningful and seamless experiences. So the leader is welcoming anyone in the community to join and develop features alongside their team.  You can download and view the integration module on the project page on Drupal.org. And if you're using OpenAI and you have some really innovative ideas about how you can put it into practice, the leader wants to know. So I'd say, reach out to them, have a chat. They want to make it happen. They want to bring people's ideas to life. So a great opportunity to get into the AI space and work on something that five, 10 years from now may really have changed the world and you would have been at the forefront of that innovation. Drupal10.1.0 release. Dries talked about this a little bit yesterday. I just want to touch on it following his presentation and just acknowledge that this is a humongously feature-rich minor version upgrade with, again, a focus on innovating the product as a whole and providing that foundation for us to build upon. So a handful of features in the release are single directory components, menus exposed as linksets for decoupled Drupal sites, streamlined content modeling experience, increased flexibility for block and page management, automated accessibility testing at a decor and a number of others. And this is just a small subset of what's being released in 10.1.0. So it's a get in there, understand what's being released, get onto Drupal.org and learn, but it's coming soon. So we do have a beta available today as of May 15th and betas are a great opportunity for the technical minded, the developers in the room to get their hands on technology before it is released to the public. So if you have experience with bug testing and even fixing those bugs, Drupal wants you to get involved and really put your hands on the products so that we can find and enhance everything before everything goes live. So it's a learn all you can about 10.1.0. There's a lot going on, a lot of innovation and development and jump in before next couple of weeks as it's released. And then Project Browser which I talk about internally all of the time, it's one of my favorite things to talk about right now. And for those who are unfamiliar, Project Browser really gives you the ability to browse, filter and install modules that you need for your projects. And I love this quote from Drees that he says, the Project Browser makes it easy for site builders to find and install modules. And you'll note here that he calls out the site builder. And we've talked about the site builder, Drees announced this persona back in Portland, DrupalCon 2022. We did a little bit more of a deep dive this year, but this persona is super interesting to me because they are technically minded, but they're not a developer. They do have, you know, ability to work in the command line, but they aren't necessarily comfortable doing that and they would prefer to work in the UI. So this is definitely an evolving persona and to have Drupal innovation and development that's focusing on that persona specifically is really fantastic. So one of the first things a new user in Drupal will do is they'll go to discover modules and they will sometimes get lost, sometimes have to leave the site and do some research and they may not necessarily be comfortable identifying what it means around bugs within a module or have the wherewithal to understand how that could impact the site that they're building and that may actually deter them from using Drupal. So having the ability to leverage project browser to easily discover and then install those modules in a safe way will help grow the Drupal community and expand to more of those ambitious site builders, those marketers, those content authors and break out into new verticals or even align to more projects. And so I think this is a very exciting project and project browser is something that I would definitely want to get involved in. The team is currently looking to fill additional roles within the project specifically around developers, site builders and documentors. The initiative leads appointed by Drees are Chris Wells and Leslie Ginn, Glenn, if you want to reach out to them directly to have some chats. And it's also available in the project browser channel on Drupal Slack. Their meetings are every Tuesday and Wednesday, so very engaging. They want everyone to get involved, everyone to contribute. And I like to say that the more diverse perspectives you can get into the room when Drupal is focusing on an innovation like this, the better off we're going to make the delivery of that solution moving forward. So I'd say check it out more info on the project browser page on Drupal.org but another great opportunity to get involved in. Now we've covered a lot. We have a couple minutes left so if anyone does have any questions I'd love to open up the floor but I just want to thank you all for joining, sitting with me, learning. I want to learn from you all so if you have any recipes for me, if you have any innovative projects that you're working on I'll be here, I'll be at our Aquia Expo booth for the rest of the time but thank you all I'm very excited to continue to be a part of this community and I appreciate the opportunities to be with you all today. Any questions? Feel free to raise your hand if we're a little shy or quiet. I know I'm most of the session before lunch so I don't blame you if you want to run and beat the line. Yeah. So I can tell I'm hearing a lot about the OHC I really appreciate it's a theme that means a lot to me and I identify the Mozilla Foundation and Firefox with that open web space. Have you seen any evidence that like the Drupal Association Aquia may be considering like partnering with Mozilla Foundation? So just to repeat the question for those who may not have heard or are watching the recording the question is open web has been a big topic of conversation at DrupalCon how and we associate with Mozilla and Firefox in this realm specifically so have we seen any developments or commitments from Drupal or Aquia to plan commitments to this initiative as well. That's a great question I think it's a super top of mind especially here with everybody meeting in person finally again and having the ability to lean on the incredible accessibility enhancements that Drupal has put out previously and also as we look to implement that strategy moving forward as well I would say in terms of commitments I have not personally seen anything in writing but I think it's definitely open for discussion and if you have opinions and feedback I'd love to learn from you and hear what your perspectives would be so I can bring that back to our team I know at our core at Aquia you know accessibility as a part of the Drupal community is part of our DNA and something that we are highly focused on in terms of just making sure that everybody has access to the web and everybody has the ability to do so in a way that feels safe and comfortable for them so while I haven't seen official commitments if you have any your recommendations I'd love to learn and hear from you and bring that back to our team thank you no problem any other questions I don't know I know he's asking questions but my question is related to the progressive decoupling method I find that speaks much more towards the solutions that I'm like towards the problems I'm finding at my company in the financial industry maintenance is like the ridiculous amount of responsibility to meet all these requirements and the fact is we have a large developer base that works in Node.js React JavaScript apps and we even have the design system that is basically tailored towards that and they are constantly trying to use our Drupal solutions because we also fully support Drupal on all our public-facing websites trying to use our Drupal solutions and then use fully decoupled and then having all these maintenance headaches because they're managing their own maintenance on all their servers how do I like I don't know how do I sell them on this progressively decoupling idea you don't need to launch nine servers you know to run your React app you can still just use our single pipeline of Drupal get a full you know React app experience but I'm just struggling with making that kind of like sale to them and they only just keep adding to our you know maintenance responsibilities so is there any advice you can have on because I see that as our solution but I can't convey to the people making these decisions how to choose it yeah that's a great question that is also a very deep question and I do want to be cognizant of the time we are one minute over so I'd love to chat with you one to one we can dive into more of your specific use case I couldn't possibly try to reiterate that question live to the group but if anybody wants to join that conversation happy to have that as a one-off as well but thank you all I appreciate it enjoy lunch and feel free to find me later on today tomorrow to have a quick chat


लास पार्ट अप दिवल्पिंग देरीटेलर स्थाटेजी इस दे प्राइस अजिस्मिंट्स तो रीटेलर को अप कोस at any point of time, किसी भी दिनके अंदर, किसी भी मान्त के अंदर, किसी भी वीख के अंदर, they have to make some price adjustments. ताके जो उसने स्थाटेजी बनाई है, वो वो सक्स्स्स्स को इंश्वर कर सके लिए, that can be on the basis of, अगर तो देमान नक्रीस होगी है, अगर तो कोस्ट नक्रीस होगी है, किसी भी जीस को तेकल करने के लिए, to have to make some price adjustments. ताक प्रीष अजिस्मिंट्स can be in the form of mark up, can be in the form of markdowns or it can be price corrections so accordingly retailer ko action lena hain price adjustment karne hain taake jo usne strategy banai hain, uski success ko insure kar suke toh humare paas adaptive mechanism retail ke andar follow kiya jata hain which is ke retailer has to adapt quickly to the changes jo ke environment ke andar, jo ke competition ke andar, jo ke store ke andar kisi na kisi tari ke se ho rahin hain toh usme markdown kiya jata hain additional markup laga diya jata hain ya employee discount ko concept hain markdown ke cases ke andar for example agar aap ke paas kui seasonality product hain aur achanak weather ke andar change hain which was not expected to quickly you can go for markdown for example you can immediately go for let's say 30% discount aur 50% discount aur 75% discount to clear your stock because agar aap weight karenge toh ultimately you will lose margins you will keep stocks, you will have lot of inventory you have cash flow problems so wo tamam tara ke issues aapko face karne parenge jo ke achar retailer expect nahin karta ke wo apne paas ye in cheezon ke saath in stocks ke saath aage forward chale pear additional markups hain for example agar kui asi product hain jis ke wo par there are prices which are increased in the market aur aap uske wo par abhi tak you are maintaining the old prices so again you can immediately do what you can do you can make additional markup on these prices aur again jab aap ye karthe hain ultimately you can earn more margins out of it jis tari ke saath markdown ke andar you are losing margins is case ke andar you have reacted to a situation then you have additional markups third is employee discount normally retailers have some discount policies for their employees which is 5%, 8%, 7%, 6% of the shelf prices so again agar kui employee apne store se product ko buy karna chaata hain toh either the employee has this discount facility into his employment card built it into the system aur you need to use the specific firm to adjust the price so employee discount has been also considered jo ke one of the price adjustments hain wo employee karta hain apne monthly grocery ke li apne li kuchis buy karne ke li apne family ke li kuch buy karne ke li apne relatives ke li kuch buy karne ke li toh amare paas ek ispanha ka price change authorization form normally har retailer ka apne standard format hain lekin uske andar components hain jo parts hain wo pohaad clearly specify ke jaate hain specify hote hain sab se pehle for example agar baat kar tha hoon toh ye define hota hain ke jo price change hain markdown agar karna hain toh uska kya code hoga ta ke system accordingly react kar sakhe agar us markdown ko apne cancel karna toh kya code hoga agar apne kui markup laga hain toh kya code hoga agar apne us markup ko cancel karna hain toh kya code hoga agar apne kisi employee ko discount dena hain toh kya hoga agar jo change aap karne jaah hain wo permanent hain toh usko specify karenge as form ke upar agar wo change temporary hain toh specify karenge agar temporary hain toh kis date se kis date tak hain agar kisi customer ke liye hain toh kis vakt se kis vakt ke liye hain kis specific customer ke liye hain wo tamam baat hain are normally mentioned on this type of price change authorization form this price change authorization form is normally signed by the price change controller jo ke har store ke inder exist karta hain and counter signed by the duty manager or the floor manager or the division manager or the department manager jo ke 4 app principle ko follow karta hain insure karta hain ke yes this change is been specified noted and implemented as per the knowledge of the management then agar am baat karthe hain markdowns ke hain hain hain hain hain so there are some markdowns on the basis of timing also for example early markdowns policy for example late markdown policy for example staggered markdown policy for example automatic markdown policy for example store-wide clearance toh agar sabse pehle maa quickly ek share karta hain regarding the early markdown policy toh kuch detailers hain hain jo ke especially seasonality ke hain hain hain hain ke rather for waiting the seasons to end let's take this early markdown to finish the stock before the season ends and the worst planning is that after the season has end now you are selling the product toh first jo markdown on the basis of time hain wo early markdown hain late markdown ye hai once you have reacted to a season now you are expecting that competition has done it and now you are doing it now you are doing it so it is as per competition has changed ya seasonality ke upar ko impact hain hain hain ya quick supplier ke toh kuch impact hain hain hain hain toh ultimately late down mark policy ke hain aap changes ko karthe hain then staggered markdown policy hain it is almost like the automatic markdown policy jistana se niche agla point specified hain isthara ke cases ke hain so you find into the system that after some time because it is on the basis of time and after at a x particular level of stock this much discount will be implemented for example agar kisi stock ko store mein 6 months se zyada ho gaye hain toh ultimately jaisa hi usko 6 months honge us stock ke upar 30% discount automatically agar aisa hain toh of course it is built into the system uske le kisi ka immediate approval nahin chahiye agar usse zyada den honge toh zyada discount ho gaye objective ye hai ke stock ko automatically on the basis of time and on the basis of this stock quantity liquidate ki hain hain hain hain and then hain hain hain hain hain hain store white clearance ka ye wo concept hain jab aap poore store mein clearance laga hain it is normally a kind of gala which you celebrate it is a kind of some day which you celebrate or poore store ke hain dar you make all this clearance for example everything and anything available into the store is less say on flat 50% so iss case ke hain dar normally ye jo company outlets hain jo branded outlets hain normally they do this jo consumer goods wale products hain uske wo po normally it been observed less ke is tar hain ki policy ko adopt kia gaya wo iss tar ki policy ko follow kia gaya wo to retailer ke saamne ye wo markdowns hain jo ke wo iss na kisi tarike se kar rahe hota hain iss tarike se amare paase quick example hain jo ke promoting markdowns ke wales hain jo ke normally you will observe in the retail stores also ke mid summer sale hain 50 dollar plus ke upar hain free delivery bhi hain and so and so so whatsoever it is you have the markdowns and now you can promote these markdowns to your customers to last step of retailer price strategy was the development cycle was the price adjustments wo markdown ke shakal methi wo markup ke shakal methi ya wo employee discount ke shakal methi hain aur aap ko ye help keringi sabajne ke le ke now and how a retailer can develop its price strategy and how overall it impacts its overall business