Celebrating the Launch of Drupal CMS  ## Metadata - Author: [[Pantheon]] - Full Title: Celebrating the Launch of Drupal CMS - Category: #articles - Document Note: --- tags: - #DrupalCMS - #OpenSource - #Recipes Author: Pantheon, Lindsay Catlett, Suzanne Dergacheva, Alex Moreno, Jim Birch, Baddy Sonja Breidert Source: YouTube Livestream Reference: [Celebrating the launch of Drupal CMS](https://www.youtube.com/watch?v=fnbdldIzFmA) date created: 2025-08-22 23:30 --- # Title: Celebrating the Launch of Drupal CMS 1.0.0 — Recipes, Governance, and AI Integration ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) --- ## 📝 Summary: The livestream marked the official launch of **Drupal CMS 1.0.0**, emphasizing the platform’s shift from developer-centric tools to content editor–friendly workflows. The highlight was the introduction of **recipes**, a new way of composing functionality that reduces repetitive tasks and improves collaboration. Community leaders and agency contributors discussed the implications for governance, enterprise adoption, and accessibility. The integration of **AI assistants** within Drupal CMS points toward a future where site builders can use natural language to configure and manage content. This release represents both technical progress and cultural momentum, evidenced by record participation in the launch. --- ## 📖 Main Content: Drupal CMS reframes Drupal as a CMS not only for developers but also for **marketers, content editors, and non-technical teams**. Recipes replace the complexity of distributions and installation profiles, making site-building more modular and composable. Governance remains a pressing issue, as the success of Drupal CMS depends on community-maintained modules and recipes. The integration of **AI recipes** provides a preview of Drupal in the agentic age, where configuration and content creation are conversational. ### 🗒️ Notes - [00:07](https://www.youtube.com/watch?v=fnbdldIzFmA&t=7) Excitement at the **1.0.0 launch**; Pantheon demonstrates seamless upgrades. - [02:41](https://www.youtube.com/watch?v=fnbdldIzFmA&t=161) **Recipes** replace install profiles, enabling unique site compositions and improved collaboration. - [07:40](https://www.youtube.com/watch?v=fnbdldIzFmA&t=460) Marketing lead Suzanne emphasizes clear messaging and brand alignment. - [10:16](https://www.youtube.com/watch?v=fnbdldIzFmA&t=616) Setup designed for **content editors**; dashboard uses familiar language. - [15:47](https://www.youtube.com/watch?v=fnbdldIzFmA&t=947) Recipes reduce repetitive setup; saves **days of dev time**. - [21:53](https://www.youtube.com/watch?v=fnbdldIzFmA&t=1313) **Enterprise benefit**: Predictable deployments via architectural patterns encoded in recipes. - [23:53](https://www.youtube.com/watch?v=fnbdldIzFmA&t=1433) Decision points reduced from **200 → 20** with recipes, saving costs. - [28:33](https://www.youtube.com/watch?v=fnbdldIzFmA&t=1713) Recipes applied once, without long-term dependencies. - [34:53](https://www.youtube.com/watch?v=fnbdldIzFmA&t=2093) Governance and community support required for sustainability. - [36:52](https://www.youtube.com/watch?v=fnbdldIzFmA&t=2212) **700+ participants, 62 global parties** — record community engagement. - [43:41](https://www.youtube.com/watch?v=fnbdldIzFmA&t=2621) Declarative models focus on outcomes, engaging both developers and editors. - [50:28](https://www.youtube.com/watch?v=fnbdldIzFmA&t=3028) **AI recipe demo**: conversational commands create content types and structure. - [57:01](https://www.youtube.com/watch?v=fnbdldIzFmA&t=3421) Clearer documentation and demos needed for AI adoption. --- ## 📖 References: - Pantheon official release notes - Drupal Association governance discussions - Drupal Recipes Initiative issue queue --- ## 🗣️ Paraphrase: 1. Original: *“Recipes cut down repetitive setup tasks, saving days of developer time.”* - Paraphrase: Recipes streamline workflows, reducing configuration to a few clicks and drastically shortening project timelines. 2. Original: *“The AI recipe changes how beginners interact with Drupal, making it a learning and building tool.”* - Paraphrase: With AI integration, Drupal becomes both a guide and a tool, letting users learn while they configure. --- ## 📰 Newsletter: 🎉 **Drupal CMS 1.0.0 Has Landed!** This week, the Drupal community celebrated the launch of **Drupal CMS**, a new packaging aimed at content editors and marketers. The big story? **Recipes**. These pre-built configurations slash setup time, reduce decision fatigue, and save costs. Highlights: - 🚀 Record launch with 700+ participants & 62 global parties. - 🛠️ Recipes cut 200 configuration decisions down to 20. - 🤖 AI recipes introduce natural language content management. - 📈 Governance remains the next frontier: modules need long-term support. Try it on Pantheon or dive into the [Recipes Initiative](https://www.drupal.org/project/recipes) to shape the future. --- ## ✅ Action Items: - Position recipes as a **case study** for WordPress open-source governance (parallels with block patterns). - Advocate for **funded contributor roles** in recipe maintenance. - Integrate **Drupal CMS learnings** into WPCC initiatives on sustainability. - Teach contributor onboarding using recipe models — reducing **cognitive load**. - Frame recipes as an **OSPO-aligned governance pattern** for enterprise. --- ## 🧪 Hypotheses: - Recipes lower the barrier to entry for new contributors. - AI assistants embedded in Drupal CMS increase adoption among non-developers. - Strong governance correlates with recipe sustainability and enterprise trust. ### 📊 Methodology: - Surveys of developers & content editors adopting recipes. - Time-to-deployment measurements pre/post recipe usage. - Governance audits comparing module vs. recipe sustainability. ### ❓ Questions: - How will recipes affect long-term Drupal module maintenance? - Can AI integration help scale contributor education? - What lessons can WordPress borrow from Drupal CMS governance? ### 🔮 Future Research: - Comparative study of Drupal Recipes vs. WordPress Block Patterns. - Longitudinal study of recipe adoption in agencies. - Governance frameworks for recipe sustainability. ### 💡 Implications: - Could redefine how **enterprise OSS adoption** is measured. - Provides a pathway to reduce **volunteer burnout**. - Encourages a shift toward **declarative OSS models**. --- ## 🧠 Learning Styles Assessment: - **Visual**: Limited visuals; recommend diagrams of recipe workflows. - **Aural**: Live stream format aids auditory learners. - **Verbal**: Strong use of analogies (e.g., Lego). - **Kinesthetic**: Recipes themselves are hands-on, but no guided exercises. - **Logical**: Clear explanations of config management evolution. - **Social**: Community launch party supported interpersonal learning. - **Solitary**: Could add reflection prompts for self-paced learners. - **Naturalistic**: Absent; could tie modularity to ecological systems. Readability: Suitable for intermediate technical readers (college-level). --- ## 📊 Accessibility Assessment: - Screen reader compatibility uncertain; live stream lacked transcripts. - No captions in real-time; recorded version needs accurate subtitles. - Strong contrast in slides, but no alt text for visuals. - Improvement: Provide **full transcript, alt text, and keyboard-friendly demos**. --- ## 🌍 DEIB Assessment: - **Cultural Relevance**: Global event but examples sk - Summary: January 15th, 2025 marks the first version of a newly bundled "Drupal CMS." Join Steve Persch and friends for a demonstration of Drupal CMS running on Pantheon and a discussion of this milestone for the Drupal community. - URL: https://youtube.com/live/fnbdldIzFmA?si=FCt0nFdQqxj2O1qq All right, Alex and Lindsay, I havepressed the go live button, but who knowswhen, uh, when people will actuallyuh catch this starting on YouTube.Alex, but before we really start, I know youattended the whole Drupal Zoom today.I only caught a portion of it; what wasthe vibe at the officialDrupal announcement? I only caught a portion; whatwas the vibe? So I'm hearing a bit ofum, me too, Alex. I suspect you might havethe YouTube video open in another tab. Yes, youdo. All right, that's another reasonto start slow. Uh, I’ll share while we waitfor Alex to figure that out. I wasexcited today to see that the instanceof Drupal CMS that I created yesterdayon Pantheon as uh rc1 was the newestuh available version of Drupal CMS. Imade that yesterday, and then likeminutes after 1.0.0 came out, I pressedthe update button in the Pantheondashboard, and it updated. I mean, thatlike that's just what should happen, butgiven the number of new moving pieces inplay, I wasn't sure if it would. It did, and that made me feelgood. Alex, have you figured out where that other noise wascomingfrom? Maybe, maybe not. All right, wellwhile Alex explores that, Lindsay, how are you feeling, having so much with? I’mgoodness, it’s all right. Lindsay, how are you feeling now that we’ve gone fromrelease candidates to1.0.0? I mean, I’m super excited. I’venever seen development occur thisquickly for so many major features inDrupal. You know, I’ve been involved with Drupal fornearly 15 years now, and this isthe first time I’veseen this type of activity, andso that’s super exciting for me to haverenewed interest. But also just collaboration across not just vendors, but developers and all sorts of folks. And so, this isamazing! It’s been impressive to see it allcome together this fast. If anyonewants to try spinning it up onPantheon, I just dropped our releasenote into the chat here. I see alsoScott Bushi, our product manager, is inthe chat. Scott is the personWhom I needed the officialthumbs up before we published thatrelease note. Uh, hey Mark,from the University of Michigan, I see you in thechat as well. Uh, Tara, Chris Reynolds,Aaron, it’s fun to get a goodturnout here in the live stream too. Alex has disappeared, but you know Iexpect he’ll come back. Technicaldifficulties from Alex, who knows. Um,given that we do have a pretty packedagenda with multiple guests, I feellike we should just keep rolling. Alexwill come back; his moment onthe agenda is in the latter half. Uh,so we’ll keep it rolling here. I’mgoing to slow fade the dance pop, andbefore we bring on our guests, I’vegot a video to play here thatshares some of my own thoughts andperspective on what the truesignificance of Drupal CMS is. Alright. Drupal CMS is a new packaging ofDrupal that’s exciting because it’saimed at the marketers who use Drupalrather than the developers who buildwith. Now, the real reason to get excitedabout Drupal CMS is the recipesconstructed instead of thinking of yourSite as a child of an install profile,each site is a unique composition ofapplied functionality. Okay, the technicaldiagrams of recipes are cool, but theirreal power is that they have sparked morecommunity collaboration than we haveseen in years. None of you have mentionedAI. We are racing into the agentic age,and Drupal CMS may be but a footnote. AIDrupal CMS also has new answers to theoldest problems: media, search, content. Work! Yeah, old problems. The future isexperience. Build a single directorycomponents project, the gold standardof no-code website building. Let me knowin the comments what is your favoritepart of DrupalCMS. All right, I did have fun puttingtogether that video partly because Igenuinely think each of those things. Ido not know myself, which ofthose is actually the most exciting part.I could probably talk myself into anyone of those things. Alex, I think youmight be back before I attempt to bringyou onto the live stream. Couldyou give me a thumbs up orsomething inchat? All right, not getting that fromAlex, but we’ll just keep it rolling. If Alex Moreno cannot tell us themost exciting part of CMS, I know someother friends who probably havetheir own thoughts on what is the mostexciting part of Drupal CMS. We've got, uh,Bodhi from Onx Internet, and we haveSuzanne from Evolving Web. Welcome to yetanother Drupal CMSparty! Yeah, great to be here. The party'sgoing! I'm also actually live streamingfrom a party. There's a party happeninghere in the office. We've been here since 5;it's now 8, so I wouldn't even dare to go out there now.Who knows what is happening? We've gotparties inside of otherparties! That is the magic of theCMS. I could probably stretch that intosome metaphor for like recipes inside ofDrupal CMS, but I'll leave it there. For those who haven't met youpreviously, B, could you briefly introduceyourself and what is yourrelationship to Drupal and the newDrupal CMS?Wow, I've been doing Drupal since 2007.Since old back Drupal 4.7, I think. Um,I started my own company together with mytwo best friends, my partner and bestfriend, One X Internet. We are inEurope, and yeah, I've been part of the community now since2013. I have been on the Drupal Association boardsince 2018, where I was at some pointwith Susanne on the board and now withAlex on the board, who is not here—or heis, but he's coming. Alex, we have youback. Can you hear me? Now we can hear you. I was just talking about you, so justleave again? No, okay. And now,recently, with the Drupal CMS, we arethe track leads of the searchAdvent search, so we've been heavilyparticipating in that andbuilding a lot of things.So yeah, well, that's excitingstuff. And Suzanne, how about you? Yeah, I'mSuzanne Dereva. I'm one of theco-founders of Evolving Web, and I havebeen using Drupal as a developer andtrainer since2008. For Drupal CMS, I joined lastsummer as the marketing lead, so I'vebeen really into all the messaging andbranding of this new product aspart of the launch. It's been really exciting seeing it comeinto being from the inside out, andsprinting the last few weeks to updategoal.org and launch the product. There's, uh, there's so much work, uh, thathas gone into this. It's beenvery impressive to see, uh, andyou know we, uh, we kind of rushed intothis live stream here. I don't think Ieven introduced myself properly. Uh, Stevefirst year director of developerrelations at Pantheon. We alsohave Pantheon staff members, uh, here also.Uh, Alex coming and going with thetechnical difficulties. Alex, where, wherein the world are you rightnow? I'm not far from, in a way, not farin Madrid, in Spain and Europe, so it's 8 PMat themoment. Longitude and latitude, you'rein the same time zone, but still,you know, more than a few miles or kilometers apart. And, uh, and LindsayCatlet, how about you? Hi, so I'm on theEast Coast and joining from Pantheon. I'ma principal Solutions Architect onour Professional Services Team. All right,so we have been saying the phraseDrupal CMS over and over and over againhere. Uh, there's a good chance that atleast one person watching this streammight be thinking, "Wait, what are youtalking about? Drupal has been a CMS forlike two decades. What is this?"New Drupal CMS thing, and Suzanne asthe person who has beenmarketing Drupal CMS. Could you get ascreen share going here and give usa brief tour of the Drupal CMS experience? Last week, you mayhave to hit the present button. Therewe go. Last week, we had an internalmeeting at Pantheon and found, oh,yes, many of Pantheon’s own staff membersaren’t quite sure what to think ofthis, but we see a new getstarted page here in Drupal CMS. Awesome! So you can get a trial up and running in manyways. This trial I’m using here is just alink from drupal.org.One of the really exciting thingsabout Drupal CMS is just the setupprocess. It is really designed to walk you throughthe steps to creating your website.So, the first step here, I can actually pickfrom preconfigured content types to addto my site, and any of these can be addedon later. If you want to customizethem, you can, and each oneis associated with arecipe.In the future, we’ll probablysee more options here and some optionsGroup but for now let's just pickLog can go and set up, and it's going tojust ask me a few questions andstart the install process. So I'm going toskip over to a site that I already haveall set up. Here, when you walk throughthose steps and get to your site, thefirst thing you're going to see is thisdashboard. Um, I think the thing I noticedright off the bat here is that the wholeinterface is really designed for acontent editor, and that to me is thebiggest exciting thing about Drupal CMS:it's nolonger a developer-centric tool. Uh, it'shardly even a site builder-centric tool. The language you see here is reallyadapted to content editors and marketers,and things that they're going to befamiliar with. So, a few things Irecommend doing if you're studying PSfor the first time: you can go to theChoose Recommended Add-ons link fromyour dashboard, and that's what's going togive you access to the recipes. I knowwe're going to talk a ton about recipeslater. Um, and I see, um, on that page, I'm goingto see in a second all the recipesthat I can pick from. I see the contenttypes that were offered in that setup. The process also includes things like SEO tools,AI assistant forms, and Google Analytics—justthings that I might typically want.I’ve already gone ahead and installed acouple of these because they take afew seconds to add.Then, going back to the dashboard,I want to revisit this idea of thewhole interface being really designedfor the content editor audience. So Ilook at the navigation over here andsee the word"create,"having content and media at myfingertips.These are really words that contenteditors are familiar with. I don’t seeconfigure, and all the other more customizedoptions are further down. What Isee centered are really my tools forcontent management; and then, if I go in andactually create apage, I’m going to see a ton of stuff that’salready designed for me. Save and preview options are right up top—sticky buttonshere. As I scroll down, if I want toadd media, I actually have options forthe size that I want to use. The medialibrary is set up. I go in and I can pickall these options. Preconfigured, well, we know thatthey're image styles as Drupal folks, butI can just pick the size I want andthese are all going to be responsive outof the box. Yes, so this seems like amuch more approachable experiencethan whathas come out of Drupal core for, well,forever, as long as Drupal has existed.You don’t get this kind of, you know, eventhough Drupal has been a contentmanagement system the whole time. Youdon’t immediately upon the installationof core get this friendly of a contentcreation experience. Yeah, and none ofthese are earth-shattering features. Right? Just that I didn’t have to do anyextra configuration to get these, and theother exciting thing is that anyone whouses Drupal CMS is going to start withthis, so writing documentation or givingpeople training is just going to be somucheasier. Absolutely! I want tobring in a Lego metaphor on theselive streams. I like to docrayons and diagrams, and it’lltake me a second to reconfigure the, thewhat now, what? All right, so I have heretwo, well, two Lego sets that areVehicles come in very different sizes,and Suzanne, as we were watching thatdemo, one thing that stands outis that this is more approachable forcontent editors. However, for someonewho has been in the Drupalworld for a while, they might be asking,"Wait, what is actually different? I've seen WYSIWYG editors before.I've seen image styles before, and Ibring these Lego sets in because Ithink we can use a differentmental model for assembling a Lego set.Both of these Lego sets, big and small,come with an instruction book. For thesimple Lego set, it's a prettysmall instructional book. Myelementary school son and I did this onein a pretty short amount of time. TheDeLorean here from Back to theFuture has a much longer instruction bookwith hundreds of pagesand hundreds of steps. So, as long as Drupalhas existed, it has been possible tobuild simple Drupal sites and highlycomplex Drupal sites; that is not new.What I see as the new part of DrupalCMS is how quickly we can buildthem. Something complex in the Legoworld — when it's literally toys, it'senjoyable to put thepieces together one at a time. But ifyou're in the world of billablehours, the client paying for theclient who may just want the DeLoreandone, they don't see any benefit in theenjoyment the developer getsfrom finally crafting these things. Also,there are some Legosets that are not particularly enjoyableto handcraft. One of my favoriteYouTubers reviews Lego sets and did notenjoy the repetitive construction of theCaptain America shield because it's just the same thing over and over and overagain. I see recipes as kind of a way toconstruct these Captain Americashield segments. If practically everyDrupal site, or a majority of Drupalsites, need blog functionality, we don'tall have to do the fine grainclicking toassemble a sensible blog configuration.We could just take that recipe andgo. Now, I also feel like, wait,we've had modules. What's thedifference between the modules andthe recipes? About it, modules are more like the individual Lego pieces, andthe recipes are more like therelationship or the configuration thatholds the modules together. We'vehad things like installation profiles inDrupal, and an installation profile iskind of like, uh, you get some flexibilitywith the back to the feature set. Iget the option of having this set beslightly different. Like back to thefeature 3, the car looks different, butthat's pretty much it. If you wanted asubstantially different car, it's reallyof no use to do all of these steps first. Just like, it'snot that valuable if you want a highlycomplex Drupal site to start with ahighly complex install profile; you'regoing to rip it all apart. Um, anyway, uh,it's more valuable to assemble it piece by piece until youhave something like recipes. Now, I feellike I might have overstretched my Lego metaphor. Can someonebring us back to the realworld of how we have gotten to apoint of assembling things byrecipe rather than relying solely on theconcept of install profiles. Modules, Lindsay. I know this is a worldand a problem space you've thought about a whole lot.Yeah, so, a lot of this comes down to what weconsider config management in Drupal,and so it's helpful to kind of take astep back and think about howsomething like config management — how youknow that's how we are deployingthese sort of Legos from one environment to another.In Drupal 7, we had something,and all of this tells an interesting story aboutnot just system maturity, but about the maturity of anopen source project. So, in Drupal 7, wekind of wrestled with features,and that's the best word that I canthink to describe features. So, whatthis was, was you know, we were basicallytreating config management like code andhoping nothing broke. There was a lot ofcrossing fingers involved. But this waskind of just the first phase ofthese bundles of capabilities. So, Drupal 8, you know, was a huge evolution in that.It brought native config management.This was a huge step forward; this put configmanagement in YAML files.What we consider now is properdeployment workflows, but this still kindof had its share of challenges aroundthings like partial config imports,dealing with production content, thingslike that. Um, and so for me, thisis definitely, you know, my opinion,is what kind of makes recipestransformative. It's not just betterconfig management, because configmanagement at its heart is aboutmanaging state. So the shiftto recipes means you're not only able tomanage state, but it's definingpatterns. Defining patterns, um,instead of, you know, synchronizing yourfiles between environments, recipeshave created kind of programmable andtestable workflows. That's a huge, hugething — that testable piece for this sort ofsystem behavior. And so it's, um, I guessin, like, you know, CS parlance, it'smoving from, like, imperative to moredeclarative programming for sitebuilding. Um, and I'm a total nerd,and maybe others won't understand that, butthat's a huge step forward. So just kind of aquick example: Say you have asite that needs, um, you know, slightlyDifferent content workflows, and sorather than, you know, in Drupal 8, nine to10, um, you know, we would have maintainedmultiple different configuration variations. Um,what recipes allow us to do is itdefines; it allows us to find a basepattern that sites can then extendpredictably, and that’s a hugedifferentiator as well. And so the resultum, to me, and I deal with, you know, aton of enterprise customers at Pantheon.Um, the result is more reliablesystems, um, and more predictabledeployments, and that’s huge. U, and Ithink, um, and also, like, these arevery, very deep technical constructs. Andyou know, I’ve been dealing with Drupal, Uyou know, as an architect for many years.But what this is enabling us to do isyou can encode these kind of seniorlevel architecture patterns in a waythat the entire team can implementconfidently. Um, if you’re a site builder,and to me that’s huge. Yeah, I, you know, Ithink about detail,like when I was in my previous job andbuilding sites, I had a strongopinion on how views module URLs couldbe constructed, andthat opinion was basically...Earl Miles said at Drupal CampChicago 2009 that I hung out like that. That'sthe right way to do it, but that's nota sustainable or scalable way of distributingopinions or getting, like Earl Milessays. The best way to do something isto put that in a recipe. It's hard to put that into amodule, but it seems like it ispossible to put such things intorecipes. To me, that is what is game-changing in recipes, right? Becauseit's a kind of recommendation. So in thepast, you would go to a Drupal site or acustomer and ask what they want to do,and then you would go to Google or StackOverflow or whatever, and you wouldresearchwhich module is the best one for solvingthat problem. Then, you would applyyour criteria on how many people areusing that module, and then you wouldknow and apply the recommendations thatyou were coming up with and just hope for thebest. Right now, there's an actualrecommendation, and that helps not justin knowing what to do, but also it’s acost-saving thing. Because I don’t knowif people realize, but every time youYou will go into a project where you will have togo through the same repetitive taskof setting everything up correctly withrecipes. You just click a button and youhave everything. You are saving days, andthose days are days that you don’t needto charge to your customer. Yeah, a quickmetric that I calculated for a standardcustomer feature was there were about200 decision points. If you don’t use recipes,there are about 200 standard decision points thatyou need to make as an architect or techlead. That is reduced to about 20by using Drupal recipes, and that ishuge for everyone: for the customer,for the tech lead, for a developmentteam, and for vendors. Yeah, so that’sawesome. As long as we’re talking aboutrecipes, I feel like it’d be nice tohave someone who could speak even moredirectly to the ins and outs of recipes.And look, there’s JimBurch, a late addition to the live stream.Jim, for thosewatching who don’t know youand are unfamiliar with your work,could you briefly introduce yourself andyour relationship to the worldof Drupal CMS?Recipes, and you are muted onyour settings. It looks like maybe— yeah,how about now? Yeah, all right, we can hearyou now. All right, I am an engineeringmanager at Canop Studios. I came toDrupal in a second life; one where Isaw Steve Pers talk at a Drupal camp inChicago, and it blew my mind. But I lovedthe idea of Drupal being a no-codesite builder. I didn’t want to learnall this PHP and stuff, but I did havethe mind of the architect. I knew whatthe client wanted, and I knewhow to do it in Drupal. So when Drestarted talking about starter templatesat DrupalCon Portland in 2022, hehad me hook, line, and sinker. So Idecided to take my contribution time andwork towards this recipesinitiative. So, two years later— a yearand a half later, we were able tosneak recipes into Drupal 10.3 asexperimental code, and I became asubsystem maintainer of Drupal core for recipesand default content, which we also snuckinto Drupal core. That providesthe foundation for what Drupal CMS is.So, a lot of people are going to want to look atthe code in Drupal CMS.There actually isn’t any code in DrupalCMS. What really makes Drupal CMS magicis that it’s Drupal11, and recipes are applied to Drupal 11.So, you know, you can go and installDrupal CMS, which you can apply recipes.They don’t lock you down; you can changewhat the recipe does in the instance.You know, after you apply the recipe, it’syours. The recipe is ephemeral; it’s goneforever, and you have a Drupal 11 sitethat, you know, like Lindsay said before,we’ve taken 50 hours ofdevelopment time and applied it to asite in less than a minute. So, you know,the future is bright. You know, I likeBaddi’s team; they have an amazing suite ofrecipes that they use. We’ve been workingon one at Canopy that saves our clientstons of money. We’re working on whatwe call snack-sized recipes now. Um, youknow, say I want to add a password policyto an existing site, one that meets OASstandards and makes you change yourpassword after 90 days and can’t be oneof the previous 12, and all that annoyingstuff that, you know, people hate. But itteams love. You know, now we can do thatin an instant instead of taking, you know,four hours and having, you know, multiplePeople look at it and review it, and sothe power of recipes really makes thefuture of Drupal modular, and you know,with less code.That concept of applying a recipe, I think, is incrediblypowerful. Just for a one-day demo that doesn’t need to liveinto the future. Modules were ableto do this before, but modules carriedwith them the expectation that you needto be able to upgrade a moduleforever. But for some things, no. Ijust want to apply this configurationand then not carry that as a dependencyor like an inheritance for the whoknows how long life of the site. Iknow we’ve had some mentions of search functionality. I think youand your team have been pretty closeto that search world. Could you speakto that? I’m guessing that the factthat recipes are applied once and thenleft behind probably gives youmore freedom to make more specificdecisions or recommendations than youmight otherwise make if any givenapplier of a recipe was then carrying a connection to that recipeforever. Yeah, totally. I thinkThat, you know, we all had problemswith the distributions; like all of theagencies in Drupal, you know, we wereall struggling with that because, um, itwas hard to maintain these so-calleddistribution profiles. And um, and thenlike, you know, then to install, like weall talked about the example of having aprofile that we created, and then likehaving to add Commerce profile to thatas well was not possible; and so on. So,this is a game changer for us in theagency world. Um, so we have been, um, usingrecipes, and like we talked about, orI think Jim said it earlier, we have morethan 100 recipes already at 1X, wherewe're not just saving a lot of time for our customers, but itis also like our junior developers.They don’t need to know how toconfigure everything; like theconfiguration and everything just comesthere, and then you can turn it off, turnit off, like on and off; and you know, soyou have a lot of flexibility. We seeit immediately; we've seen it now in ourrecent projects, how much, how much fasterthis makes everything; and again, how, howmuch faster we are actually updatingeverything and maintaining it.It's so much easier. So I think, like, youknow we are just at the start. We arejust launched today theDrupal CMS with the first set of recipes.I’m going to say it here: I think we’re going tohave hundreds of recipes coming outthere in the next months, where peoplecan start applying it, which fitsperfectly to the question that is beingasked in the chat. Yes, you know, yeah?Go for it. Yeah, Chris asks here in thechat, and I put it up on the screen heretoo: how are recipes discovered andapplied? Is it drush? Do you do itin the command line? There’s actuallya PHP script inside ofDrupal calledDrupal, which you can execute.There is a drush recipe command, which is awrapper around that PHP script that’sinside ofDrupal. Eventually, youwill be able to apply recipes in ProjectBR.There is some magic in Drupal CMSthat is working now that might notwork on all contrib sites unless Buddyproves me wrong.Wrong, I'm testing it. It's like life.Now when you say it, so it's so likeall of the, you know, technical partis correct, but at the moment, ifyou go into the Drupal CMS and you gointo the product browser, which you findwhen you go to—if you're not a Drupalperson, you go into Extend when you'relogged in; then of course, you see thelist of all the modules, and then you seethe list of recipes. We now have 12recipes that we can then install, andlike we can try it live if we want to.But let's not do that; let's leteveryone here try it out. Yeah, so yeah,definitely, it works great in Drupal CMS.But that's a hard-coded list of recipes that are in Drupal CMS,which brings me toactually what I want to say is that,there is a—so in Drupal, we have thislike we have the modules, we have thethemes, and we have the distributions, andthen we have the general project. Iwas involved in the decoupled menuinitiative back, you know, one or twoyears ago, and that was like we weretrying to do some decoupled stuff, and wedidn't have a place for it on Drupal.orgor in Git.Install, like, you know, React stuff. Sothere was a general project created, andnow actually people are putting recipesin there, and this is what Jim wasreferring to. Yes, we don't have them yetdisplaying automatically, but this issomething that the DA and the Drupalcommunity, the core team, needs to figureout in the next couple of weeks, I think.And if there's anybody here that isinterested, we have open issues in therecipes initiative issue queue we’d lovefor some UX strategists and sometechnical thinkers.You know, because developers will justdevelop. Like, we're going to make a list,and it's going to be a list of recipes,but you know the Drupal Association'slike, you need to slow down; you need toactually put some thought into it. Maybeget some user testing. Um, so yeah, we havethat need in the recipes initiative.So I think the key is, I love what TimDoy T said during the launch party, thatthis is not a landing party; this is alaunch party. The best, there's a lot ofwork to do, but yeah, the recipe isthere. Yeah, and Alex, I know you'rea part of the Drupal Associationboard, and, and, and buddy, you've got, um.Roles and connections are bigger than the technical details ofDrupal CMS. Like, what else needs tohappen for the launch to keep propelling? What metaphoricalrocket fuel does the communityneed to keep moving? I think a lot is neededbecause we are just at the start, andit was amazing howDre came there in Portland and said, "We're going to do it."At that time, there was no team,no leadership team, no advisory council; this was all createdreally quickly. Now we have a structure for that,and we definitely need to have a structure for how the governanceis going to be around Drupal CMS. We havea lot of modules in theconfiguration that need to bemaintained, because they are part of theDrupal CMS; they are part of the recipes.We need to have companies and contributors behind those modules,and we need to make sure that all of them are maintained and theyhave double maintainership.Active, we need to have the companiesto help and basically commit tocertain things in the DA, and maybe Alexcan tell us a little bit more about that.What the DA has actually, because the DAhas been playing a huge role in thisin the last nine months.I want to give a disclaimer because I'm part ofthe board of the Drupal Association, buthere today I'm just a member of Pantheonand an individual, so everything I sayis my own words and mypersonal opinion. I want to give ahuge shout out to the Drupal Associationbecause they've been under a lot of press pressure.People don't realize that it's a tiny team;as the team says, "Tiny But Mighty."When Dre said, "Hey, we are going to do this,"the whole focus of this tiny team had tokind of change, you know, to all thethings that they were like in GitHub orGitLab. They were having all thesepriorities, and suddenly all of that hasto change to accommodate this, so hugeshout out to them.I want to give a few highlights of what was going on.A couple of hours ago at the party, TimLenon was the director of the orchestrafor the launch event. There were morethan 700 people; I think you weresaying nearly seven, right? Yeah, so 700and on top of that, we had streaming fromparties. We had 62 parties, and let’s justsay that each party had 20 people. Wesaw that there were otherparties that had much more. That’s likeprobably we reached out to 1,000 peoplelive in an hour today. So, this is thehighest-attended Drupal event in history.Right, a part of DrupalCon duringCOVID? So, to me this is amazing; thismeans that, you know, we have a hugecommunity, which we already knew.Having this kind of excitement, I have only seen this duringDrupalCons, right? Having all thesepeople, companies, and people from allover the world contributing to theDrupal CMS access. We are on trackto triple the contributions.These are the kind of things that weneed to happen from the DrupalAssociation. The Drupal Associationis tiny; they can’t do a lot, but they canhelp the rest of the people achieve thesuccess.Drupal, and I think it's just youknow, remember, remember, like we are allyou know, some of us are old enoughto remember the Triple 7 and Drupal4.7 Hypes. These were bigthings, and then Drupal 8 came, andthat was so hard for a long time. Youknow, and everything became a little bitlike, and then I think it's sorefreshing to, like, when you look back,you remember these threehighlights that you’ve had in thepast in Drupal, and this is definitelyone of them. I think this is just—thisis so much—this is, like, Chris said inthe chat here on YouTube. He said, like, um,you know, this was very refreshing toinstall Drupal CMS this morning, and Ihave to just agree with that.Chris largely comes from a WordPressbackground. Suzanne, a couple of monthsago, I attended one of your evolveDrupal events, and one of the themesat that event was sort of stacking upDrupalagainst competition like WordPress andother web systems out there. As you're the co-founder of Evolving Web,I imagine it's your responsibility tomake sure that your agency is buildingWebsites with the most effective tools,and sometimes that means not Drupal. Howdoes Drupal CMS change the wayyou as a business owner think aboutwhen and where to use Drupal?Yeah, I think it's exciting for a lot oforganizations we work with who useDrupal, but they're running hundreds ofwebsites in some cases of websites.There are site owners at thoseorganizations who go off and build asite on WordPress, Wix, or whatnot, andwe always want to support those users.But we would love it if they would useDrupal for everything, and I think DrupalCMSis a game changer in a lot of ways. Theseorganizations already haveknowledge, but now I think they will havea lot more momentum about using Drupalfor more and more of their projects.And that's just from today, but theroadmap for Drupal CMS, like theproduct strategy, is a three-year plan.It's about adding experience Builder, adding a lotof the other UX improvements, and creatingmore recipes. This is going to make iteven more of a no-code solution for folks,and I think it's going to be able tocompete really well against some of theOther tools, um, and I think a lot of what we seebeing added to Drupal CMS are thingsthat bring it in line with theexpectations that site and contenteditors have. But Drupal already comeswith Drupal core, so it’salready, in a lot of ways, more accessibleand more secure than the competitors. So,really, you know, head and shoulders abovesome of the others.And I see some potential to, uh, get that nocode benefit while still keepingthe attention of developers who verymuch want to go back. Uh, many minutes, Lindsay, youused the framework of likeimperative versus declarative mentalmodels, uh, as it relates to recipes. Couldyou unpack that a bit more? Because I, Iimagine inside of there is a nuggetof what will keep developersengaged who might not otherwise thinkwho might otherwise opt out of likeOh, I don’t want to work on a no-codesystem; I want to work on a code system.In whatways will theshifts between imperative anddeclarative models, uh, potentiallyKeep developers engaged in thisworld. Oh, apologies, I thought I was muted.Okay, um, yeah, so I think thekey focus between imperativeversus declarative isvery focused on how to doit, I guess. So, very focused on technical requirements, step-by-stepinstructions, things like that, like thisis very similar to how features werearchitected, and Drupal is a declarativeapproach. Think about customeroutcomes; think about what the customerwants. I kind of consider this as what you want.So, if you thinkabout a content type, acomparative approach would be thinkingabout individual technicalarchitects or tech leads going throughlisting individual field typesthat they need in a content type,whereas a declarative, you know,approach would be thinking about going with the recipe-basedapproach. What do most customers needin a standard maybe content type,that's called stories, for example.And so the use case isn't going to fitfor every customer; every singlecustomer use case.Um, fit for most customer use cases. Um,and so to me, that's the bigdifferentiator! Yeah, that's an exciting way of thinking aboutit. To confirm my own understanding,I'll go back to that search example. Lindsay, you mentioned theway too many options that anygiven configurator would have to wadethrough. Configuring a module like search API,as I understand it, your company has been one of the drivingforces behind the search recipe. If Iam building a site and I know I justwant the best sensible starting placefor search, I'm much better off applyingthe community-accepted search recipethat Body and friends have developed than I am byinstalling search API and getting a zillion checkboxes that I have to thinkabout. Yes, so first of all, likeI actually love that example!It's I actually love that examplebecause so Triple Core comes withsearch. So there is already search inDrupal Core, and that's why it was alsocalled advanced search, because, um,and by the way, like in this very shortperiod of time, we managed to do likeCommunity surveys like we checked and we asked thecommunity what they use, and wepresented that in Barcelona. It wasamazing because 90% of the hundredswho answered said they all useC API. It's like, "Wow, okay, if you'realready using C API." And thenwhat else do you use? We use facets, weuse autocomplete—these are all modulesthat people were configuringevery single time. Some of us werealready preconfigured somehow, and so ourdevelopers didn't have to do it allthe time, or the tech leads had to define itevery single time. And I think,like now we've just, you know, the markethas changed. Also, like, yeah, we need tohave it dynamic. And it was done in away that there is even, like, wecreated a long concept with the hope thatyou could even have it as adecoupled search because the search APIalso has a decoupled version ofthat. So the more we do ofthis, the more you just have to click, andthen you can have this configurationthere. This is just a game changer foranybody doing anything. So a note here.Not all of the ideas that we wanted toput in made it into version one,because, and that I think applies toall of us in the track, becausewe all had really ambitious goals,but at some point, we had to ship aversion that worked. So there's, forexample, facets are not in yet, but it’sprobably going to come in very soon now.Um, and again, we had to do a lot of thingsand just a little search iscombining a lot of different things thatneed to beconfigured. Now, when I wasrecently at WordCamp US, which theWordPress community has also, in the last fewyears, gone through a similaroverhaul as their block editor. TheGutenberg block editor came in, and oneof the things I was hearing repeatedlythere was, we now need to be extendingblocks. As blocks came intoexistence in the WordPress world, thereare some core blocks, and theneverybody’s making custom blocks. Iimagine we could see a similar dynamicwith recipes and Drupal; they’re theacceptedrecipes, but then everybody just goes andMakes their own custom recipes. Uh, Jim, isthere a way to take thecommunity-accepted recipe and thenextend it? There is, uh, one of theprinciples of the recipe initiative isthat recipes should becomposable, and individual recipesshould be broken up so they can beapplied separately or builtupon. Um, so the first thing we did toprove recipes worked was to replace—well, we didn’t replace because it wasn’tremoved—but was to copy Drupal’sstandardprofile as recipes. So, a lot of peopledidn’t even know what was in thestandard profile. They’d install it withminimal and they’d be like, “Where’s themedia entities? Where’s image in remotevideo?” Um, now as recipes, you can installthe image media entity, and you neverneed to do that again. Um, you know, inDrupal CMS, there is a media recipethat creates image styles and responsiveimage styles. I think like I have one inour suite of recipes. I’m sure Bad hasone too. Like, I never want to create animage style config again, you know,because you need to create hundreds,right? If you’re doing it right.You don't need to, um, so one of the thingsthat I did initially when we, uh, therecipe started forming in Drupal CMS wasI looked at, uh, Martin's event recipeand like this is, I mean, he's the goldstandard of datetime things in Drupal.His recipe is that, so I scrappedmy event recipe and now I call his eventrecipe and added some fields, somecustomizations that I need to it. Youknow, the same could be done with Baddie'sand her team's, uh, uh, search recipe, likemaybe customize it for Pantheon Solar, um, oranother host. Um, you know, apply it toyour, uh, to your content types. You know,one of the pros, uh,that Artam on BD's team has solved, uh,was, you know, how do you add facets whenyou add the search recipe to contenttypes that exist now or may exist in thefuture? Um, so there are ways to extendrecipes, and we actually encourage it.Um, so you can just do different thingsat different times, different buildingblocks, and you know, encouragereusability andshareability. So again, you don't have tobuild everything. Um, you know, go ahead,Steve, uh, can I get AI to do all of thebuilding for me? I know that’s one.Of the recipes, I feel like it's somewhat coincidental that the timing ofDrupal CMS has happened at the same timeas the whole tech world is lookingat AI revolutionizing who knows how muchof our jobs. So, Alex, I’m going tobring your screen share on becauseone of the recipes that a lot of people are paying attention to isthe AI recipe that puts an agentinside of Drupal. I don’ttotally understand it, butI’ve been super excited since I saw this. I thinkit was in Pittsburgh Drupal last year ortwo years ago when this first happened.I have to say, I was doing this demo last weekin the Friday Forum that we have every weekin the company in front of over a hundred people, and it went terribly bad.I think I found out why: It's because I wasnot wearing my Drupal demo.So everything should be serious now. Coming back to serious things, one ofthe main goals for Starshot was makingDrupal easier for beginners, and I thinkin an intended way we have managedthat with the AI agent. So, if you go to anew...Brand Drupal French stall. If yougo to the specific, for example, the dashboardor any admin page, you will see somethinglike this: Drupal chatbot. So, I was — whatanother thing in favor of the Drupalrecipes is that I was trying to do thisby myself, installing all the modules,configuring, and I lost a few hourswithout achieving anything. I just wentto the recipe and I launched it. Just aline, which I had to find how to do it,but it's relatively easy and it hadeverything configured for me. I justhad to add the API from ChatGPT, right?Then, when I go to the admin or thedashboard in Drupal, I have someonetelling me, "Hey, how can I assist youtoday?" So, I was saying we may have doneDrupal a lot easier for beginners,because this is actually changing theway that you interact with Drupal. Butalso the way you learn Drupal, becausenow you can say, "Hey, Drupal,tell me what you can do for me." Then,you are learning in Drupal, inside Drupalitself what you can do with Drupal. Right?So, Drupal will tell you, "Well, you cancreate or modify content types. You canset up taxonomies, you can addfields." Okay, but hey, I'm new to Drupal.What are you talking about? What is acontent type? Right, well actually, acontent type — you ask Drupal again and itwill tell you everything you need toknow about a content type. Right? To me,this is a game changer, and thisis just about, you know, kind of learning.Why don’t we do something more? Uh, forexample, let’s find what content types dowe have once weunderstand what a content type is. So weare going toask Drupal to give me that. Would youlike to check the content types? Yes,please. You can see we are having a realconversation with the CHB, which isprettyawesome.Yeah, Chris Reynolds is saying in thechat that this is what he needs,so let’s wait a few seconds. Uh, this iswhat was failing last week, actually,because when you install it by default,you will have a 30 seconds timeout, andfor some of these actions, you willactually need a higher timeout. And, well,yeah, that’s what we found inthe demo last week.Um, things that you can do at the momentfor example is, uh, get a list of umThe actions that you can do include getting a list ofcontent types. Get the list ofactually, I'm goingto show another tab. Can I stop, or do youneed to? No, I think I cannot change.Ah, there yougo. There you go. Oh, there we go. Okay, sooh yeah, that’s one of the issuesthat some actions take some time forthem to come back with. Um, and I don’tknow if that’s a problem with it;it doesn’t matter. The thing is that, as Iwas saying, you are completely changingthe way that you are interacting withDrupal because now, for example, you canask, "Hey,create a new content type." I’m going toadd types as well, uh, call it "Alex ContentType," right? This is going to takesome time as well; it will take a fewseconds, I guess. Um, but once we have this,we will go to the back end and we willsee how our content app is there, readyto create new content.One of the things I like most aboutthis tool, and I think with all AI things,it’s kind of experimental, but not onlycan you create structure in Drupal, butyou can also create content. So, you know,if you want to add a field, a taxonomy.You can add a field to a piece of content to classify it, and you could populate it with theterms that are in there. So, like, add acurrency field to my event content typeand populate it with the most popular currencies in the world. You know, it willcreate the structure in Drupal but alsocreate that content foryou. This is, of course, only one of the things that the AI functionality in Drupal can do. We alsohave, like, you know, who is notinstalling today, like generatingautomatically alt text for images. Youknow, um, give me suggestionswhen I'm writing content. Like, all ofthis is already available somehow,and now with the recipes we’re justgoing to have it more in front ofus so we can easily do it. I thinkit's going to be crucial to give outthis information. Now the job is going to startwhere we figure out how we can makesure that people know about this becausein the installer process, you didn’t seeanything called "Do you want to installAI?" You know, you had to, like, find outthat there's a recipe for that, and thenwhat that recipe does. You also have toread about that, so it’s going to beIt's crucial that when people come intoDrupal CMS, they will have reallygood demo content. And then, of course,the documentation on drupal.org needsto be awesome. So, I think all thiswork will start now so we can reallyshow the world what you can do withDrupal because we've been able to dothis for a long time now, but now we'rejust a little bit bringing this out andsaying, "And now anybody can do it."Yeah, uh, and I want to keep an eye onthe clock here; we're just about atthe top of the hour. Uh, Alex, thank youso much for showing us the AIworld. If you're watching thisstream and you're interested in tryingout Drupal CMS, as of today it has aversion 1.0.0, and that's exciting.Some other tabs here, Jim is workingon recipes in Canopy World.There's a whole recipesinitiative if you want to try this outon Pantheon. As of today, of course,Drupal CMS is available as a PantheonUpstream. If you go to our doc site andlook at the release notes, you'll findthat, which will bring you in a fewclicks to the Pantheon dashboard. You mayhave seen this before; you can installCMS freshly upon Pantheon in, you know,whichever region you choose. I did thisjust yesterday, and it worked. I'mexcited to see where we go fromhere. So I'll bring down my screenshare here so I see us in a biggerthank you, Pantheon. Uh, Lindsay and Alexfor joining me here today on thelive stream. And of course, thank you,Bodhi from 1X Internet, Suzanne fromEvolving Web, and Jim from Canopy. Thankyou so much for taking time out of yourother parties to join this party withina party. Uh, thanks so much, and yes, I'llsee you on the internet. Bye-bye,everybody. Yes., Celebrating the Launch of Drupal CMS, Pantheon, 01jhp2vv92628xmfqcdbfcphvw.