 Welcome, everyone. Good morning, good afternoon, good evening, wherever you are. Thanks for joining this webinar by Alchudo and Acquia, unlocking the potential of Adeless Drupal. Let me start with the agenda. Today, we will have a short intro on Alchudo and Acquia, and then we will talk about the market trends. We go deep drive on what is Adeless CMS and how Drupal can function as an Adeless CMS, and how Drupal and XJS can bring two powers, like from the DXP leader, Drupal, plus the front-end technology in XJS, like how they can work together. We do have a short demo of how XJS and Drupal can align and how you can still manage all the Drupal back-end experience and also vis-a-vis editor, everything, along with taking the advantage of all the Adeless CMS features. And also, we have a few Adeless success stories with Drupal and Acquia was able to accomplish. But I will start with the speaker intro. Tammy, you want to start? Absolutely. Hi, I'm Tammy Perlstein. I'm a Principal Product Marketing Manager at Acquia. I've been at Acquia for a little over a year, but joined with a wealth of experience across the digital experience as an industry. So excited to have this conversation with Alchudo today and we have a good one for you guys. Thanks, Tammy. I will go next. I'm Satish, currently working as a Senior Vice President Delivery Technology and Delivery in Alchudo. I have 25 plus years of experience in delivering scalable IT solutions. Been in this content and commerce area for almost 15 years now, currently supporting my customers with achieving the digital and cloud transformation. I'm based in Phoenix, Arizona. I can be reached at the email id given satish.balakrishnan at alchudo.co. The next speaker is Karthik. Karthik, you want to go next? Hi, this is Karthik. So I have about 14 plus years of experience working with Drupal and other CMS. I have a lot of domain experience with marketing, e-commerce, education, health, sports, and telecom domain. So really a good experience with customizing Drupal Drupal as a solution and also implementing third party services in Drupal, CMS, and developing the API. And also I contributed patches and modules to the Drupal community. So you can reach out to me at Karthik.com or at alchudo.co. A brief intro about Alchudo. Alchudo, we are a global digital marketing and technology agency. We focused on one thing and one thing alone that is create a personalized customer experience to our customers. And the way we do that one is like with an integrated tech stack that is focused on delivering omnichannel, cross-channel personalized experience using the single view of customer. The key mark tech that we assemble is CMS, marketing automation, CDP, analytics, CRM. These are the three tools come together so we will be able to achieve the single view of customer. And also we do have a very unique innovative way to bring the customer insights to the process. So our DXP experience, like we've been in this DXP world for over 20 years now. Implemented like 2000 plus projects, worked with 500 plus customers. We are like 400 plus trained certified DXP team members across like various platforms. We are very well known in the market for our IPs and accelerators that we created over this years. From service-wise, we do end-to-end solutioning starting from advisory services, implementation, managed services, migrations and updates. We build like custom solutions for the version upgrade like particularly for Drupal and other major CMS. Like we do have a like upgrade accelerators which helps to migrate this version upgrades much faster and seamless. We do have like something called one-way framework which we primarily used for multi-site implementation, single reusable code base used to build like multi-site, multi-tenant, multi-language websites. And also like we have a lot of experience on the marketing cloud, including campaign management, personalized CDP and dam implementations. About our experience on the Drupal and Acquia, like we've been working with Drupal for more than 10 years now. Three plus years partnership with Acquia have like 10 plus awards across worldwide awards we have received in this DXP. And also like we have like 20 plus integrated solutions which we build, which accelerate the development, IPs and accelerators. And also like we have like 80 plus Drupal SMEs in the team. With that I will give it to Tami to talk about like Acquia. Thank you. A little background on Acquia. So Acquia was born out of the Drupal open-source movement. We were founded back in 2007 by Dries Baitard, the founder of the Drupal project. And the goal was really to support the growing Drupal project and movement and community and help increase the adoption of the composable solution. And Acquia bet that the open-source and cloud movement would win in the long run in the long-term and in the digital experience space specifically. And from the very beginning, our platform has been cloud-based. Now today we're a proven leader in the digital experience space as assessed by Gartner, Forester and more. We have over 4,000 customers across a variety of verticals. You can see just a few here on the right of your screen. And those organizations bet their business and the experiences they provide to their customers on Acquia and on Drupal. And Acquia is the open and composable DXP built with the foundation of Drupal. So built with the open-source CMS to provide you ultimate flexibility and an API-first perspective. We're looking to integrate across your existing systems and services as well as expand you across the Acquia DXP solutions. And our solutions are also composable. So as you grow, as your challenges and your goals adapt, you can swap out different services or expand your services as you really change your organization. Your teams can also assemble and reassemble the different components to craft your digital experiences at scale, making it really modular, really composable and really flexible. And we're built for resilience with that in mind to meet the ever-changing digital landscape with security and performance at the forefront. So Acquia and Altudo, like we both, both the agency have a common goal to help the businesses succeed in the digital world. Acquia being a open-source leader in the DXP platform and Altudo being focusing heavily on the creating a personalized solution, combining both Acquia and Altudo campaign like will result in a better ROI for all your digital investments. We talked about it like why it's time to think and act on edless, right? Like these are all some of the recent studies for example, the worldwide website software forecast, like recently mentioned that the CMS solutions like a headless CMS solutions were like in 2021, it was like 5% but we are seeing a compounded growth of 27.5% across the year after year. And in 2026, like over like $1.6 billion solutions will be built using the headless content management solutions. Same thing like we hear from the faster predicts by 2024 the next year actually like the 75% of enterprise will have adapted a headless CMS, CMS solutions. And one of the recent studies says like a 83% of e-commerce companies will start using the headless CMS for their digital commerce strategy. And from markets and markets predicts that AI in the headless CMS market will grow from like 130 million in 2022, 1.32 billion in 2025 which is like a 58.2% growth year on year. So this is the primary reason, right? Like the various studies, various market trend shows like a headless CMS is being widely adopted. It's not something new, it's been already adopted and it's gonna grow, explode in the upcoming year. So this is the best time for all the marketers and the IT team members like to start thinking about headless and migrate the solution to the headless. So before we go deeper on the headless on the group side, let's talk about like what is like headless CMS and what are all the different variations is today? When we talk about the traditional CMS, CMS, a user create and edit their content through their vis-a-vis editors or an HTML editor. The CMS then displays the content according to the front end layer, front end delivery layer built within the CMS. So the front end delivery layer is coupled within the CMS. That's the only major difference between the headless and traditional CMS. The front end layer is coupled within the CMS itself. So if we remove the headless CMS pretty much like the headless or decoupled CMS will form, in a headless CMS, there is no default front end templates. So the CMS exposes all the content in an API layer and as the developers will create like a front end agnostic solutions, they can utilize this raw data and build the solution which fits for whatever the channel they wanna present the content like whether it's a web or it is in the mobile or in the digital watches or any devices they should be able to use the API content and they can create their own front end templates in their any technologies which they wanna build. Decoupled CMS is very similar to headless but it also provides an additional feature of retaining the front end template but it's decoupled like it's not directly pulled from the database rather it uses the same API layer. So it provides both headless and also features of headless and also the coupled CMS experience also like it provides both in the decoupled CMS. So we can talk a little more on the headless Drupal. Drupal has built like it started as a coupled solution like where the front end sits inside the CMS but in the recent versions like the application layer like API layer has been created. So Drupal supports both decoupled and headless CMS. So what is the, what are all the uses, right? Like headless Drupal is a way to build the website and web application not just the website, like we can use this data content and then build, utilize them in your e-commerce solution, web portal, wherever you want you should be able to build. This provides like the decoupled option. It's no longer like it's not required for us to do the, create the front end using PHP rather we can use any of the recent frameworks like Next.js, React or any of the tools by utilizing the APIs provided by the Drupal. So yeah, like so Drupal, headless Drupal is the ideal for creating a custom front end, building mobile apps and integrating with your any third party services. Why do we need like a headless Drupal, right? Like deciding like the foremost advantage of using an headless Drupal will be the website performance. When we talk about performance like a performance it's not just like it's primarily very important for the customer experience perspective but also right like right now with the recent Google algorithm changes, websites with the better performance gets better page rank. So it became a must for to get the better performance headless Drupal, a decoupled architecture will provide a much better performance than a coupled CMS. So that's the primary importance of moving into a headless Drupal. And also right now it's not just website like to provide a, like create content once and use it across multiple channels it's became a common norm. So headless Drupal will provide that facility as well that feature as well. And as a developer like you get like more control now like all the modern technologies like you don't need to be stuck with PHP or any backend solution. The developers have the wide options right now it's not just the front end technology they can utilize any modern technologies to build that modern technology which they already know they can utilize them and build the solutions. So the availability of developers and et cetera will be much easier now. And also like building this since when you build on your own solution like there is no restriction platform level restrictions are not there. So it will be provides us to build a more engaging responsive and seamless user experience on our website or web application. So the scale, scalability like since the feature of like moving the content delivery away from the backend system will provide us opportunity to scale the website like we can utilize any of the edge computing or wherever we should be able to deploy and scale as our business grows like we have the option to scale. And also the from the security perspective and also maintenance and everything easier right now with the headless proposal. There are like a lot of common misconception about using headless traditionally we get like headless headless is only for developers. So as I mentioned like a headless definitely provides a wide variety of options for the developers but also like with the performance and all other advantages we discussed before it provides like for marketers, non-technical content creators and for everyone headless will provide like improving your page performance and experience and everything like so. So headless provides it's not just for the developers but it's for marketers, non-technical users content authors, everybody take benefits from this headless headless. And also be like a headless is best suited for a single page application. Yes, like a headless definitely can be used in the single page application but with the we can take advantage of all the modern technologies and solutions like we should be able to build a traditional website mobile apps or any other front end applications by consuming this APIs. And there is another misconception like a headless means sacrificing Drupal features. So that's not true as well. In the upcoming we will be showing a demo where even like we will not lose any backend features that Drupal provide but also like a page level editing features also can be enabled when we deploy a headless Drupal. And Drupal is not SEO friendly. This is exactly opposite of what in from the reality. The websites built using the front end technology decoupled websites are always have better SEOs and also like because of as I mentioned before like because of the recent Google algorithm changes. This provides like the SEO has been drastically increased. We have seen customer migrating to the headless CMS have achieved like 90 plus light of score and which improved overall like increase their organic traffic and everything. And Drupal is less secure. This one also is not the right thing. Like Drupal can be more secure than traditional CMS by going with the headless like because we are separating the backend and front end. So which will help us to reduce the security like attack and improve security. And there is another misconception saying like a Drupal is only for the large organization. Definitely like large organizations can take advantage like because of the enterprise wide solution like a large organization can take advantages. But also we have seen like a lot of small businesses nonprofits and the individual bloggers also taking advantage of headless Drupal and building a solutions like which can really omnichannel cross channel solutions they were able to build. Headless Drupal is difficult to set up. It could be a case like several years ago but with the launch of like a starter kit and also like the API layers like very customized API layers which has evolved in the recent version of Drupal. It provides like a easy to set up and easy to manage. Headless Drupal is expensive. That's another misconception like because you can utilize like since we're gonna use the front end development frameworks it'll be easy to deploy even we can deploy them in the Edge Cloud and there's no need for a web server also like with the recent improvement in the Edge Cloud. Drupal requires like extensive coding knowledge. Again, like this one also a big misconception like the headless Drupal will allow us like anyone who knows like how to consume and use an API will be able to start developing their front end using any of the languages they know whether it's a Next.js, whether it's a React or it's a C sharp, whatever language they know if they know how to consume an API and how to display it's like we don't need any additional knowledge or anything like we can the team developers can use their existing knowledge and they should be able to build a headless Drupal solution. And the last one is like a headless Drupal is not user friendly. Again, like it's like the front end experience now with the performance and also like using the latest React.js and type of front end framework. We can improve the customer experience drastically. We can showcase like in our demo we will show like how we easy to filter filter a huge volume of search results and everything. Yaakartik you wanna talk about Drupal architecture? Thank you Satish. So I want to touch base on the different architectures available for us to solution or implement the Drupal application in a way like we want to have this data exposed to multiple channels and multiple organizations. So this can be easily achieved by following any of the architectures which best fits your requirements. So basically we have a traditional or monolithic architecture where we are using Drupal as a CMS. So it holds all the content and we have the front end templates available to render the data. The unified architecture where you have powerful tools and features of content management and user management will be using in the traditional Drupal templating. And next is like we have decoupled architecture. So Drupal is used solely as a content management system and the front end is built completely separately using a technology or a platform design whichever platform you are comfortable or best suit for your needs. So you can approach that solution. So this way it provides a greatest degree of flexibility but requires more development effort as I mentioned like since we are separating the layers like front end and back end we might need some expertise developing the front end frameworks using view or next year or react. And we need the coordination between the both teams to make it a better outcome. And next is the hybrid architecture or progressively decoupling. So this is the best shoot for organizations where they wanted to have or utilize the Drupal front end templates as well as exposing the data through the API. So some parts of the website or application are built using traditional Drupal templating and rendering techniques while other parts are built using some front end frameworks like I mentioned makeshares or view whichever we can. So this approach provides a balance between the flexibility and Drupal's out-of-work features. So we are not losing any kind of editing experience or any kind of user management or content management experience. So that is what it is about like the Drupal architectures which we can take up. And coming to the next, it is the key components of Headless Drupal when we are implementing any headless application. So we have, and coming to Drupal like we have these components like Drupal CMS we have the API or the web services we have different end frameworks. So authentication part is also the major component here and the content delivery and also the decoupled architectures of going over like Drupal CMS as we are well versed with Drupal and other CMS. So it has a powerful content creation and management capabilities including content types, fields, taxonomies and views. So and the API coming to the API component the Drupal provides an API that allows other systems to access and manipulate Drupal content. It is both like consuming the data and also we can update the data from the front end framework. And the next component is the front end framework. So which separates the Drupal front end component and we can use any framework like React, Angular or View is used to build the user interface for the Drupal headless application. So it communicates with the Drupal API to retrieve and display the content. So that's the main role of this component and authentication and user management basically handled by Drupal which provides user accounts, roles, permissions so we can still use the capabilities of Drupal authentication and users can log into the headless Drupal application using the same Drupal credentials which we have which we provide from the back end. And going over the content delivery Drupal provides a variety of options for delivering content to the front end including the RESTful web services, JS and GraphQL. The front end framework can choose best delivery method based on its requirements. So whatever is best choice for you like we can pick up the content delivery method. And also as I mentioned this all comes under the decoupled architecture where we are separating the front end layer and back end and we are using these services in between to transfer the data, talk between the front end and back end components. So the key considerations to move to headless Drupal so everyone has a question like why we should move to headless Drupal and what are the reasons behind moving to headless and what benefits we'll be getting out of it. So I'm going to just walk over the key considerations which you have to make while making the decision. So the content strategy is the main component here which you have to consider. So headless Drupal separates back end content management from the presentation layer. This means that you will not have a solid content strategy in place to ensure that your content is structured organized and optimized for delivery to different channels and devices. So you should have more focus on how you are structuring your content. And coming to the next consideration is that development expertise. So headless Drupal requires quite different skills like as I mentioned, like we need to have a Drupal back end development experience, side building experience. And also you'll need developers to develop different end frameworks which can be next year, so a few years and this should be well versed with implementing the API and also follow the microservices architecture and best possible standards to create the API. And next comes the integration requirements with headless Drupal, we need a lot. We need to integrate in the third party systems to deliver content to different channels and devices. As I mentioned, if you want to create a system for only channel experience like we need to deliver to different channels and the responses may vary depending upon what channel we are targeting. So this means you'll need to carefully evaluate your integration requirements, select tools, which will help you seamlessly connect between Drupal and other systems. And security considerations with headless Drupal, you are exposing your Drupal API to the internet which can create a security risk. You'll need to ensure that you have robust security measures in place to protect against the potential vulnerabilities. So we have, yeah, we have the secure communication and we have to follow the best coding practices. So we have to make sure like access and security protection are in place and we are also making regular updates to the Drupal core and contributed modules so that we are not giving any chance of leaking our vulnerabilities. So I'm going to talk about Drupal solution which we developed at all today. So like we developed an application using Drupal and we selected Next.js as a framework because it is getting more popular and it has a lot of capabilities and our front-end team also created a component library which we can reuse and kind of a framework which we can enhance the time to market for anyone who is going to opt for it. Yeah, we have implemented the solution using RESTful web services and JSON API modules which comes out of works with Drupal we configured the REST resources for content, file uploads, the web forms. So yeah, we structured them in a fashion like we want to expose the data to the different channels. So we are using JSON, like there are a lot of authentication methods available out of works with Drupal. We implemented this using JSON web token authentication and the RESTful APIs are authenticated with disability tokens. And also we have few customization implemented in our Drupal application to make sure like the responses API responses are to facilitate the required formatting and the structure based on the channel which is trying to utilize it. So we also implemented that as part of this solution. And yeah, we have a next year component library which is the most and which fits the best with the Drupal to consume the data and also like update the data. So it's kind of two-way handshake between the Drupal used as a content repository and the next year's framework. Yeah, thanks, you can take over, thank you so much. Thank you, Karate. So AQUIA also pulled together two starter kits that enable organizations in building headless Drupal applications. The first is AQUIA's headless starter kit and what you achieve with the starter kit is being able to accelerate your new headless Drupal application builds by up to 50%. So I will say this is meant for new headless Drupal projects but it really comes with a boatload of capabilities and features that enable your teams to work faster when building with headless Drupal. I'll touch on a few today. The first is a minimalist configuration for easy setup with access configuration for purely headless development in Drupal. The second is a specific headless developer role for front-end developers to have a dedicated role inside the CMS to access API docs, managing access for front-end applications, connecting right into the CMS. An API dashboard for front-end developers to get access to dedicated dashboards that manage all headless integration aspects within the CMS. Data modeling in headless mode, providing revamped admin navigation, bringing all the data modeling controls under a single menu. So making that navigation really seamless, really easy. Content preview and experience to create preview within the CMS to see the content through the front-end context right from within the headless CMS. So being able to see what that content is going to look like in the headless context but making it very easily previewed. And lastly, headless and hybrid UI modes so the ability to operate in a purely headless mode or in a hybrid mode where Drupal is still used to render a front-end. So that is covering off on the Acquia headless starter kit. But like I said, we do offer another which is the NextJS Starter Kit. So the NextJS Starter Kit gives you pre-built configuration and react components to speed up the creation of your new react-based front-end application. And why we chose NextJS? Well, it's really proven as popularity, maturity and flexibility to support decoupled headless and static architectures. So with the NextJS Starter Kit, you'll be able to achieve accelerated administrative setup with roles, users, consumers, API keys, NextJS site instances and more within a single step. So that single step setup makes it really easy. A starter kit for connecting NextJS with Drupal and the Acquia content model. So that makes that very seamless. And then the third is JSON API wrapper to handle all JSON API queries. And the last is starter react components for rendering the content available in the Headless Starter Kit and a default routing system mapping Drupal content types to react components. So again, making the seamless process of building out your Headless Drupal projects with the Headless Starter Kit for Drupal from Acquia and then also providing that front-end accelerator as well with our NextJS Starter Kit. So this is our application which we developed. So this, we have a carousel, we have two cards of content and we have a contact us block here at the end. So this is the homepage which we developed and all this content is coming from the Drupal GMS which we'll be showing you in the next few minutes. So going over to our professionals, so this is the page where we have lots of tons of data about the professionals which are available in different locations. So we can filter the ad filters and then fine-tune the results based on the applied filter. We can also see like we have few more filters from other locations. We can just select them and see how the results are getting fine-tuned. So this is again like selecting a new location. So you just see like the professionals available in those locations. We have another filter here, area of focus. So this bio professional has some area of focus tag. So we can filter these professionals by choosing the data of tags. We can also search by a keyword either by the name of the professional or let's say I'm going to search for com and we got this professional matching with the name. So snora and on clicking like we are going to the details page for that professional and these are the different sections which we implemented which are there in Drupal, all this content is getting pulled from Drupal using the RESTful API. I can show you the editing experience. So I can click on edit and this gets updated into the text field where we can do the inline editing. For this professional and here I can just scroll down and show you how we are editing the bio of this professional. We need some edits. Yeah, and yeah, this data is updated in real time and I just wanted to show the other section where interest of the particular professional we can just update this by making some changes and then click on save and this gets updated in real time. So as this content is updated I'm just going to go back to our professionals page to show you the changes are now reflecting in the listing as well with this data being pulled from the listing API and all this data which we modify is now available in Drupal. So I'm now going to show you the backend that Drupal CMS implementation. So we configured the RESTful API which comes out of works in Drupal like we configured them. We configured serialization. Yeah, we have token and JSON authentication token modules for providing the JWT authentication and I'm going to show you how we configured the RESTful APIs like we have these resources available, content, web form, our file upload and I can just edit our content and show you we have all these methods and then JWT authentication is what we are using as authentication method and yeah, so we configured everything and I'm just going to showcase one particular content type which is bio, which we just had a look at and here we have different fields added and then we are referencing these fields with paragraphs where we added paragraph types. I'm just going to edit one paragraph type and show you how we structure the fields to hold the content which we are showcasing in the UI. So let's make it on education and we have a lot of fields which are available for that particular paragraph and filtering by a content type we can see the list of bios available and Nora Peters, we just updated from Nora and to something Nora Peters so it is now reflecting back in Drupal. So just trying to edit and show you how we populated the content in the backend which is available in the front end in different sections as I showcased you. Yeah, so this is how we structure the all the categories applicable for this professional. Yeah, so this is a quick demo showcasing the capabilities of headless implementation using next year. So we'll finish off our conversation today with a couple of customer stories of how they were able to achieve success in leveraging headless Drupal. A couple of different industries but some really great stories. So we'll start off with PAC-12 which is the collegiate athletic conference and they would really wanted to provide connected applications to provide the best digital fan experience. I know some I'm a big sports fan March Madness is going on but really they wanted to provide the number one spot for their fans to go to for information. PAC-12 has connected apps on an array of platforms such as iOS, Apple TV, Android, Fire TV and they rebuilt their entire website PAC-12.com. So their applications present content such as team schedules, video info from social platforms so pretty dynamic content to their fans and connecting all of these applications with the most accurate content which as I said is dynamic it changes frequently proved to be pretty challenging for their team. So PAC-12 went out and leveraged headless Drupal to connect to and power their array of fan-facing applications via APIs and Drupal acts as the central nervous system. So really the piece that holds everything together orchestrating various microservices and the flow of key data across all of these apps. Leveraging headless Drupal and Acquia together PAC-12 was able to deliver 3,000 plus landing pages for all annual PAC-12 conference events then they were able to create all these in just five months and they also migrated all their existing video and can now host all pre-game, live game and post-game video on their new site. And in the first year on Acquia's platform PAC-12 networks doubled the number of hours people viewed content on their site. So a really great example of a real life way to leverage headless Drupal to increase customer digital experiences and connect those experiences across an array of applications. Our second example is a company called Livewire. They're an electric motorcycle brand and what they really wanted to do was deliver a rich multimedia digital experience that portrayed what it was like to ride one of their motorcycles. They also wanted to establish a single source of truth for their digital assets. And their previous site was designed completely from custom code which made their content updates very, very challenging with a heavy reliance on their developer team. And by shifting to a headless implementation with Drupal it lets Livewire integrate Drupal, their CMS and all the content that lives in Drupal into two different versions on their website. So overall they're able to improve their site performance but they're also able to boost their customer experience and satisfaction. And their team leveraged Drupal's rich API support to take a content as a service approach. So they were seamlessly integrating Drupal, their powerful CMS into their existing front-end application. And the new site effectively captures their brand, the experience of their brand and allows their communication specialists to seamlessly update media and all of the related content. So removing all of those barriers that they initially had by building with custom code. The results, they were able to implement in just one month. They launched five global sites in one month as well and they launched a pre-order page for one of their bikes, which sold out in minutes. So again, another great example of leveraging headless Drupal, accessing those rich APIs and delivering rich content that connects with customers and really drives incredible customer experiences. And our last customer success story is KCTS9, which is the Netflix of PBS and they're powered by Drupal of course, but they chose to build their experience with headless Drupal. Their site was really tightly integrated with a variety of PBS's APIs with station level curation, personalization and original content. And they built the site to serve APIs for future projects such as Roku and Apple TV and a number of apps. So again, another example of leveraging headless Drupal to use those rich APIs to serve content not just on current channels but looking towards those free to channels, what are you looking to expand into and how are you planning on serving all of your content to those new channels? And what KCTS9 was able to deliver by leveraging headless Drupal. So by taking that decoupled approach, they were able to create a streaming application that is three times stickier than their default PBS app based on videos played per visit. So they were able to increase their customer engagement threefold just by leveraging headless in a Drupal context. So great, another example, another great example of how a customer of ours leveraging headless Drupal was able to again impact that customer experience, really drive impactful engagement, gain revenue, gain loyalty, leveraging headless Drupal and really seeing some strong success. Thank you everyone. Have a good rest of your day or night.