51黑料不打烊

Transcript

So hello everyone, and thank you all for joining us today. We are going to go ahead and get started. We鈥檝e got a lot to get to a full agenda, for everyone. So welcome to espressos and experience Manager. Today Casey Bitter and Rajan Kumar are going to be presenting on digital agility with. So we鈥檙e going to be covering both Am assets and sites today. So again a lot to get to. And as you can see we are working in 51黑料不打烊 Connect today, which is a rather new webinar platform for us. So we might have a couple of things or unexpected surprises, but we appreciate your patience and hope that you enjoyed the session. So we have designed our webinars to be interactive, so we do encourage you to ask questions in the questions box throughout the presentation. You type them in there and we鈥檝e set aside the last ten minutes or so for Q&A. And we鈥檙e going to do our best to answer as many of those as we can. So I do want to quickly mention a few housekeeping items before we get started. We are recording this webinar and it can be viewed on demand and shared with other members of your team. So you鈥檙e going to get the recording of this event in an email from us tomorrow afternoon. And, I would like to also point out that at the top of your screen, there鈥檚 a black bar with the icon of a hand on it. You can, drop down there and find different actions that you can utilize throughout the presentation. So if you like what you see, you can like, applaud, laugh or so on. We would love to see your engagement throughout the event. So definitely encourage you to utilize that feature. I do also want to mention that on the next screen there is a handout available for download. Our presenters today put together a bunch of resources for you, so definitely be sure to download that and use it as needed.

And then as we鈥檙e closing out the webinar, we do have a couple of quick survey questions, that we鈥檙e going to be at the bottom of the screen would just take not even like 30s to fill those out. So if you could answer those for us, that would be greatly appreciated. So with that, I would like to introduce myself. My name is Alana Cohen, and I鈥檓 the senior digital event manager here for our Customer Success Strategy team. Here at 51黑料不打烊. I鈥檝e been with it be now for a little over six years, and spent the majority of those years organizing and hosting these events for you guys, our customers. Prior to my time on this team, I spent about two years working with 51黑料不打烊鈥檚 Advertising Cloud customers. And then before coming to 51黑料不打烊, I spent many years at different advertising media agencies around New York, but I am excited to be here now hosting events like this for you guys, our customers. So if you have any questions or comments about today鈥檚 event or any of our customer exclusive events, please do reach out. So I鈥檇 like to hand it over to our presenters to introduce themselves. So, Katie, would you like to go first? Sure. Thanks, Alana. Hi, everyone. You see we鈥檙e here. I am an Am business advisor here at 51黑料不打烊. So mainly just in and product specialist. I鈥檝e worked with Am for over six years now and I originally started over in the solution implementation space. And then I transitioned over to this post implementation strategic role. A few years back. So I鈥檓 excited to talk about digital agility today. And I鈥檒l hand it over to Raja. Thank you guys. Hey. Hi everyone. My name is Jasmine Kumar. I am a technical advisor at 51黑料不打烊. I have more than ten years experience working on end product, and I have been with 51黑料不打烊 more than a year, and I have prior to that. I have work in the development and the implementation space with the different roles as a architect or did consultant. And currently I鈥檓 managing more than 200 customer for solution led customer where I lead the technical consultations. From onboarding implementations and the post implementation journey.

Awesome. Thank you guys. All right. So let鈥檚 go ahead and get right into it.

Right. I鈥檓 actually going to hand it right off to Casey, who鈥檚 going to kick us off.

Awesome. Thanks a lot. So welcome everyone. I鈥檓 sure we鈥檙e all wondering what is digital agility. So I hate to throw another nonsense business term at us all. So let me try to break it down for us first so we can describe digital agility as authoring content quickly, consolidating content from disparate systems, or pulling in content from relevant systems. And finally, we can refer to it as delivering the right content intelligently and quickly to the right audience.

So Am has native features and integrations to be digitally agile. Then we鈥檙e going to talk through these today in terms of a financial services case study that our professional services team, 51黑料不打烊 Customer Solutions or Ax, implemented and talk through some of the latest and greatest authoring methods that AMD has to offer.

So yeah, the agenda today we鈥檙e going to talk through some common challenges that you all may be facing, and then go through some of the best practices that we can apply to your business objectives and alleviate some of those challenges. Like I mentioned, we鈥檒l be going through a case study that was put together by yes, and then also talk through some additional best practices before we get into some of the newer innovations with a, that is universal editor and document based authoring. We鈥檒l have a brief demo of those two new tools and then talk through some innovations before we get into Q&A.

So some of the challenges we hear from customers are listed here. We see slow or generic experiences that do not engage your customers. We hear that content authors cannot create quickly or update experiences quickly, and we hear that there can be long and complex development cycles that limit your business agility. So we want to talk today about how you can implement a with a focus on content reuse, centralizing assets, content permissions, personalization, and template or component governance, and how these can help alleviate your challenges to help accomplish your business objectives.

Katie, do we actually have a poll question that we want to ask everyone? Yes, let鈥檚 I was asking for that. Let鈥檚, Have them call us. Thanks, Alana. Sure thing. So, we want to know from you guys what challenges most impact your business objectives. Content reuse, centralizing asset content permissions, or personalization. So let us know which is the biggest challenge for your business.

And honestly, Casey, it鈥檚 kind of like a mixed bag here. I like to share the results with everyone, so people should be able to see. But it looks like personalization and then centralizing assets are the two big ones here. So yeah. Awesome. All right I鈥檓 going to go ahead and close this poll and get us back over to the side.

Awesome. Well, thank you for that insight.

I just want to, you know, kind of set the scene. So before we start any a, project, what your implementation team is looking for is to understand your customer challenges and objectives. And so during this phase, communication, collaboration and alignment are critical in any implementation. And so the first step is establishing a partnership between you and that implementation team and getting clear alignment on the challenges. So that they can help map the right solution to solve them.

So many customers, including the one that we鈥檙e high level discussing today, start their journey with multiple cmss and places where assets are stored. And for this, customers impacted their ability to achieve the desirable result. And so just before we get into any of the case study, just know that at this phase, we鈥檇 like to build a solution that follows best practices that we鈥檒l talk through today, drives value and delivers future capabilities for your business. And doing so, of course, will maximize the impact of those experiences to drive those measurable outcomes.

So during the discovery phase of this case study, this project has focused heavily on this, these four business objectives and mapped them to our best practices.

The first objective is being the UX alignment with A and componentry. And this customer moved from an existing CMS to Amazon Cloud service. And they had no experience developing front end code for Am. So part of the deliverable was to take what they had designed and co-developed the component library with that front end team.

Next, there was an emphasis on extreme content velocity. The team identified where content was reused not only the same content, but also where the structure of the content was similar or the same.

They use content fragments or experience fragments to create similar experiences. For example, this customer had many article pages, office locations, financial advisor profiles, and article authors that all had similar content and use content fragments or experience fragments that provided similar structure to create these, different pages.

So it鈥檚 important to all of our customers, just like we saw in the pull to deliver personalized experiences. So this team used an art plugin to give end users single landing pages. These pages were personalized by applying the branding for the customers through CSS changes via style systems. And they were also able to see their personal information. They used core components, but enhance those components to bring in relevant information through APIs and variables that were stored in Em.

And finally, the last main objective for this project was that they wanted to make sure they made their the best decisions to increase their customer engagement. So they worked with the customer to leverage all 51黑料不打烊 products that they owned, leveraging 51黑料不打烊 Target to display relevant content, and 51黑料不打烊 Analytics to test and measure engagement of those experiences and make changes based on the data that they had gathered.

So let鈥檚 talk through some of the high level solutions within the asset space. They saw disparate systems, siloed teams, a lack of security groups. And so as the US designed a centralized dance system to house all content and track everything within the dam.

Next, they discovered that most of the 100 components that existed on their previous CMS were actually just variations of the same component, but with slightly different styling. So they were able to consolidate and reduce the component library down to 25 components, and also were able to accommodate multiple use cases with each of these components leveraging those style systems.

And originally, pages were authored separately and from scratch for the use of content fragments, and experience fragments provided them a central place to author everything for a consistent experience across all places. It also pulled in other relevant articles based on the audience data, allowing for end users to find relevant content very easily.

So let鈥檚 talk through more of the specifics of the solution now. The article just gonna, jump in here. I think we have another poll that we want to ask you to. You鈥檙e right. I鈥檓 all good. Okay. This is, I think, the last one. So, Okay, so we want to know which 51黑料不打烊 solutions are you using? I know Casey just went through a couple of them. So. Want to hear from all of you what everyone has here on the call today. So, yes, a majority. This is also multi-select. So if you have more than one solution, please let us know.

But it does seem like a majority of our crowd are Am users, which is awesome and plenty of work for users as well. So good mixed bag. Happy to see people from all different solutions on the call today. Awesome. Cool. All right. I am going to, end this poll. Okay, that鈥檚 back over to my presentation. Go for it. Casey.

Awesome. Yeah. So we鈥檙e actually going to touch on each of those products a little bit in this high level, diagram of the solution that was built out. But, we kind of touched a little bit about how normalizing the number of components helps your teams manage and use them better, and makes that process of creating content more efficient, which ultimately leads to that content velocity that we鈥檙e discussing.

But as you鈥檙e aware, marketers are also responsible for creating content for multiple channels, which means we need a robust content supply chain. So the specific customer use work front and dynamic media to help the supply chain. So I know this is a little small, but first let鈥檚 talk through this bottom left portion of our solution with work front. If you鈥檙e unfamiliar, work Front is an enterprise work management solution used to assign and complete projects, work front end and have a native integration. And after they鈥檙e connected, any marketer can comment on an asset and work front, and then the asset and all of its data can go into the down.

Marketers can kick off any project and work front by linking an asset in the down, and metadata will seamlessly sync between the two systems. So this specific flow made it so that any asset entering the dam had already gone through all the required workflows and work front, meaning that they were all compliant and approved by all of the stakeholders by the time they reached a.

So the next portion of this solution is that now that all the assets are in a, dynamic media can be leveraged. So dynamic media has many different capabilities. And use cases like zooming or 367 set. But in this specific use case, the customer wanted to view the same asset and three different areas on the site. The first being an image on the homepage as a small teaser. The next. If the user were to click on the teaser, they would be taken to a landing page and the image would be used as a hero banner. And lastly, it鈥檚 also use on the details page as a primary asset. So there are three different height with aspect ratios for the same image, and dynamic media will serve them with the right proportions each time, only needing to store that image once in the dam and once just authoring on your site without having to go on and create those different variations.

Next, I want to talk a little bit about 51黑料不打烊 Target. So to serve the right content to the right audience, 51黑料不打烊 Target helps marketers to personalize content for end users. Now, target needs two things they need content and an audience. So of course A comes in for the content piece they created and manage the content in a specifically with experience fragment.

Then, within 51黑料不打烊 Experience platform or app that lives all of their end users data. So they have a 360 profile of this data. And from there they can create and activate segment and target. They created a target activity role and serve the right content to the right audience using logic in that platform.

And finally, this team also had use cases where they needed to move content from one environment to another. A newer capability of Cloud Manager is to use the Content Copy tool to sync content from prod to stage, stage, QA, etc. so this is kind of just a high level of how they use and leverage all these different products to ultimately complete, their business objectives.

Now, earlier we spoke about content supply chain for structured and unstructured content. Let鈥檚 briefly talk about the last portion of the solution with structured content.

We mentioned that this customer had multiple office locations and wanted to keep the office addresses inside of em. And so for that we can treat these addresses as structured data.

They also had multiple financial advisors where information like their first and last name, their bio, their location was all stored in Am.

Now, these advisors were writing articles, and these articles were made into content fragment models. One office location could have many advisors. Advisors can write multiple articles, etc., etc. so all of these one many relationships are all managed and am.

Similar to how you can create a page and am needing a template to create a content fragment, we need a content fragment model. So that鈥檚 what you鈥檙e seeing here.

This customer wanted a structure in and but also in their own systems. So even though most of this project was ahead full solution, this aspect was also used as a headless application. So there was a graphical layer and a to retrieve the data from an in Json format. And then another reason why they chose this content fragment model approach.

So that kind of concludes the overview of the case study, where Arcs implemented and with some best practices to ensure everything was set up to be digitally agile. Now, one of the most common questions I receive as an and business advisor is what are Am best practices and how can we leverage them? So as you can imagine, there are many ways to respond to this question as everyone implement em a bit differently. But I want to encourage you to recall the, all the different ways to accomplish digital agility that we talked through earlier. So that would be authoring content quickly, consolidating content from disparate systems, or accessing and leveraging content from relevant systems, and finally delivering content intelligently.

Using some of the best practices that we left listed out here. You can emphasize content reuse with core component style systems, experience fragments, content fragments, native tools, and new innovations which ultimately lead you to be able to author content quickly and efficiently. We also just encourage you to think about where you can consolidate systems and rely on em for solutions, like a centralized dam with the well thought out folder structure, naming convention and metadata strategy, or even structured content models. Also, consider your entire content supply chain and discern where you can access or leverage content from relevant systems like WordPress. And finally, think about delivering your content intelligently by connecting your CMS with other tools like Dynamic Media, 51黑料不打烊 target, 51黑料不打烊 Analytics app, and testing those experiences along the way.

So now I鈥檓 going to hand it over to Rajan to discuss some more technical best practices to help with your digital agility.

Thank you Casey. So now you have just a great overview of the how the customer key challenges can be overcome with adhering with the business state to best practices. I鈥檓 going to talk about, technical best practices in access governance areas and environment deployment and the last, performance in the security. So okay, so access governance best practices generally for most of the organizations is managing the users and the group is crucial. And controlling them, the access with responsibility within the system. So, there are a few of the best practices while setting up your users and group. You have to follow up. So kind of the ensure you understand the users responsibility. And accordingly, you can create a group with the authority kind of this particular scopes having the access only to do the content auditing. Another group probably might have only do the asset manipulation. So kind of have the proper setup for the roles and the risk groups initial level. And there are, other box group comps, with the am, so kind of, rather than creating a new group from the scratch, probably try to extend out of box a group like, dam users, then we have, contribution some users and then workflow users. So you can leverage those, you, groups. And on top of that, if you have any custom, requirement, then you can modify that. Then another one avoid user based permissions. So generally you ensure you create a group, you add the required permissions and keep adding users to the respective group to ensure the, maintenance perspective. It I鈥檒l always have a group created and apply the ACL permissions rather than just having permissions applied over the, users. And then last one is basically having multiple brand to your system. So having a content, a structure hierarchy, and the asset also in the managing hierarchy, it will help you to provide the access easily. So these are the basic level of the access governance perspectives. But how you gonna manage those. Right. So if you see at the left section, admin console is the central locations to manage users. And they group fully across all that product. And then you can create a group which internally, sync into the M and M, when it gets in we call like I am s group and I am s group should be the member of the a m groups. So. And a m groups will have the required ACL permissions. So I鈥檒l be showcasing in the demo as well. So we鈥檒l talk about how you can just manage the group. So this help you to add your users directly to the admin console. So if you have already set up a groups you know each groups have what falls in the responsibility you keep adding to the admin console. So rather than just, going to the a m and then adding to the respective groups. So having these all best practices centralized, you can get benefit with the easy access management in case if you just want to get added in the future, you know what group it is. You can easily add them. They will get the required access. It also talk about the, the ownership and the responsibility. What group has the what responsibility. And then it reduce the complexity of managing users in group.

All right. With that, I鈥檒l move on to that environment, best practices. So, by with the base, package like, environments are available with the products plus stitch all together and it comes with that, development environment. So productions and the staging environments are available as a pair. So when you spin up, staging environment you get also created the production scene instance as well. Then development instance can be used for any of the testing purpose, and it can be a link to the non production deployment.

Then additional one is the rapid development environment, which is a very crucial for the developer who want to test quickly and rapidly kind of have you want to deploy a code and just wanted to validate, any of the functionality so it can enable that capability. In general, if you want to deploy via Cloud Manager, it has to go through the security and quality code checks, which take some amount of the time to deploy your, code into the your environment. But having a use case where you want to test, small functionality and quickly you want to deploy so you can leverage the, the e and this can, the sole developer can just deploy from the local to, the instance via a command line. So it enables you to, especially in that during the development phase, if you want to, cross test the multiple functionality, it give you the faster way to, enable and enhance your development productivity. The third thing is, additional non product, an environment. So basically especially this comes into the pictures where the use case you have a scenario where you landed up into that long running. And you just take a longer time. So you have a stage and production. So typically stage and production should be always in the sink. You don鈥檛 want to keep, stage and, product is, not in sync. So in that scenario you have the options to add, purchase additional non-production environment where you can just, deploy your code, have the your testing is done properly, and then you deploy to the production instance. Then last thing is talking about on the environment best practices, additional published regions, which is IR, add on capability on the purchase. And it just provide the, lot of capability, kind of, I it help you to reduce the latency and increase the availability. So especially the use case where organizations receive a significant, business critical traffic from the different regions. And, and you want to serve your content from the closer to the, which attack locations. Right? So, distance publishers can help you in that case. And it also help you whenever the any region goes down. So, city and traffic will directly related to the respective region. So this can enable you to kind of, have a, higher availability and reduce latency. And, your visitor will get a better experience.

All right. So we鈥檒l move on to the deployment best practices. So yeah. So probably you must be knowing to deployment, comes, like a non production spike in, in the production pipeline. So non production pipeline basically just validate your code and build and deploy it to the non production environment like a dev. Or you have additional dev environment. With the non production pipelines you will have also a good quality pipelines which handle the builds. And then they run your unit testing and execute the code quality. Give you that idea how your code is kind of performing whether you鈥檙e having a, good unit test in coverage or not. Right. And then deployment pipelines will just generally, come with the kind of a full stack, deployment which will just deploy your back end fronting and dispatcher all together, together into the non-production environment. And just it to accelerate your productions and replicate your productions pipeline as in our non productions pipeline, you can enable the, functionality for the custom function testing. You can enable the product functional testing into the non production pipeline, which will just test as equivalent what you have in the production pipeline. Then production pipeline basically one thing to highlight here. So full stack all deploy all other back in front end. And your dispatch support. But along with that we do have a also targeted deployment scenario. So especially the use case, you have made the changes especially on the dispatcher side. And you don鈥檛 want to deploy the complete, code. Right. So you have options to deploy only the VM tier configurations, or you have made the code changes only on the front end side. So you can just proceed directly with the deploying on the fronting ports. And this can save you some time also for the deployment rather than always following going with the full stack deployment. And then config is the another one. So especially if you have a web filter role which you can leverage, you can just deploy the changes directly only for the configurations. Part.

All right. So with that we鈥檒l move on to the last topic on functional performance and the security best practices. So when you talk about the performance ISO caching, caching is the one of the key metrics where you can, we, we want to keep an eye. How much content, is your cache? If it is, what we recommend, having a more than 80% cache issue is always optimal for the better performance. So, you have a capability to cache as the fastest hidden layer by adding, classic control header at the dispatch. And also you can catch your, HTML page this or, your, asset mine tabs, the all that鈥檚 it mind tab. You can configure the dispatcher level, which will ensure to cache at the end layer. So by default caching comes for the five minute for the state on the browser. But it can also override with the dispatch at all configurations. And as per your need. Then you can customize whatever the configurations you needed, few of the basic configurations and the best practices, especially in the caching. So what we recommend avoid using user agent as part of the very header, and then use the surrogate cache control header to control the client caching. So rather than focusing on the browser, you can also, change the configurations and ensure to cache. Get it guys the first layer. And then we also recommend like applying a state if you are in state while the validate directive to the allow backgrounded face and avoid cache meat. So basically it will internally, make a call and pull the face data and put keep into the cache so user will not get impacted. User will get have the correct content. It will serve correctly without having any latency. Then. Yeah. Moving on to the security side. So security is also a key aspect when you are just developing. I have seen a lot of questions coming from the security side. How do we, make sure that our DOS stack is not happening? How do we overcome this one? So, traffic filter role, including the web full comes as a additional package. And if you have a skew, like an enhanced security license or the de dos protections, you can leverage, these features. So using the this features what you can do. Basically. So you can block or allow request at the staging layer, you can have a flexibility to control on the weight limit. And you can modify as per your need. And traffic rule can be also applicable on the target or the, publisher whenever you wish. So the way you can implement this, since you can have a configurations at your code level, you add your required, metadata and the traffic rule, and you can deploy your code to the, your production instance. So this way you can have a control. So once you go live you can analyze your traffic. What different checks as segments are coming from where the traffic is coming, whether it鈥檚 a dot stack or not. And based upon that you can just apply your, rules and then you can deploy. So it鈥檚 completely on your control. The customer can just modify the rules and deploy it.

Then another alternative by default dispatcher side, you can have a capability to add few of the security like mod security is enable already. So you can add few of the DOS rules over there to optimize. This does not require any add on, license. And you can just modify the rules. You can play around with the filter and the security headers, all that. These are the best practice in terms of the performance and the security. Now I鈥檓 gonna pass it on to Casey to talk about the different, routing capability for the edge delivery.

Thanks to John, now that we鈥檙e a little bit more familiar with and best practices, I know we throw a lot at you, but now I want to touch on the new ways to author content within, and that helps with your content velocity, digital agility, and of course, your team鈥檚 experience within Am. And then after my brief overview, we鈥檒l give, we鈥檒l get a brief demo of these options.

So the first authoring option for your team would be authoring your site content in and using Universal Editor, which is the new UI for cloud service customers to author and and site. It can be used for any implementation, any content, in any aspect of your content. So the Universal Editor is a versatile visual editor that is part of a site that enables authors or a what you see is what you get. Or with wig editing for any headless or head full experience.

So because experiences and Am can be built in many different ways, any implementation can use the universal editor. So the authors can perform that in context. Editing. Now, a content author should have the same powerful editing experience that we also formerly offered within a and page editor. So the universal editors allows for content authors to edit any content visually and in context, so that supports a and page structures and content fragment and document. You can all author that within that page.

So for our content author content is not just about the information that鈥檚 contained, but also how it is rendered and received. And so we know that your content can come with additional metadata and, rules sometimes. So that鈥檚 why it with also within the universal editor you can understand and edit including like layouts and applying styles. On that page. So really it鈥檚 just a new and improved way to author content within a.

Alternatively, you can also leverage document based authoring. I know that鈥檚 been something that our product team has been, you know, rolling out over the last year or so. And so this is a way to use familiar authoring tools like Microsoft Word or Google Docs to author content. So these documents in Word or Docs become your pages on your website. Really like your headings in the documents will become headings on your website if you鈥檙e building, using italic, underlining, making lists or images on your site, on your doc, that will appear on your website. So all personalized content and automated workflows are also available to you in this format of authoring, there鈥檚 just now zero onboarding required for your content authors to get up and running, because these are tools that they鈥檙e already used to. So with that, let鈥檚 take a look at these options with our demo.

Let me yeah. I should be able to share. So I鈥檓 going to set my screen.

I hope my console visual. Yeah. So, before we go to, HDMI or think capability, I just wanted to touch based upon, best practices from the access content and from the environment and the deployment side. So, as we talk about how we can manage the, users and the group in the center location, that we can also have the interface and can navigate to the users over there and then go to the users group. You can just create a new groups. So you can just say demo and then just save it.

Go to the list users assign the product profile to ensure you whenever the user, whenever a user is part of this group, they are able to log in to that instant. So I鈥檓 just gonna add to the one of the my instance. So.

There are a lot of instance. So I鈥檓 just picking up the instance what I have it. So I鈥檓 going to give you the access positions. So at the users.

And service configurations.

So profile has been added. And then I want to add a users in this group. So I鈥檓 going to add myself in this group.

Alright. So user has been added. And now I鈥檓 going to log in to the Am instance where this group has been going to sync it. So I will go to.

Production instance of the my sandbox.

So now if I go to the user groups, I will see that whatever the groups I have created, what they. Right. So demo has been sync to the our Am instance. So let鈥檚 go to the security group.

And then you see over you can see the demo group has been sync to the Am instance. And if you see the property you will see already the member is already added. So now what are you going to do? So this is image group what you created into the admin console. You want to give the permissions for the ACL to allocate. So what are the privileges they will have. So what I鈥檓 going to do I am going to use the default, Out-of-box group. So you can have, you can create either you can create your own group then add the required ACL. But for the demo purpose I鈥檓 just going to going ahead with one of the time user out-of-box group. So.

Here is the time user which is the auto box. So with the I am group, what I鈥檓 going to do add a group I am is group. What I have created an admin console. So you can add this group as a member of the a m groups.

So now user groups demo groups is a part of the diameter group. So all the access whatever it is inheriting to that. Same. So I鈥檓 going for it. If you want to add a users and want to have a access privilege, you can keep adding all the users to the, user group demo. So I, you and any new user is going to be onboarded. You can just keep adding over here and they will get the same privilege. So you don鈥檛 have to just go to the M, you are going to manage all the central locations into the admin console. So to have that, all the required privileges. But that鈥檚 how you can just segregate the users permissions and how you manage the, groups over there.

All right. This is about the access governance. And then I鈥檓 just quickly, talk about the, you know, environment side and the deployment side. So, if you go, on the, the styles and you have options for the ad environment. So based upon the, your license, like, you might have additional development environments, you have options to use or created. I just wanted to cover on the rapid development, basically, so you can create rapid development and assign to the developer kind of they can swiftly deploy the code once they have set up the rapid development, they can deploy deploy it. You can just select the rapid development and you can select the region and then save it. This environment is going to spin up. And then this can be leveraged moving to the pipeline side. So I will stop, like I have been signed out. So.

On it. Yeah. So, with the pipelines and all. So you have options to add pipelines, with the production pipeline and, non production pipeline. So it鈥檚 basically, I have already created I just wanted to cover, the things like.

Lee, you have different options, like a full stack and the targeted deployment. So targeted deployment, you can select the config, either funding code or the web type. So this separately you can create it. So this can help you to, foster your kind of deployment rather than always going higher with the full stack deployment. And so let鈥檚 go ahead and I will select this once and then.

So this will get created. And I have already created a, production deployment. So basically you can just have the configurations. And another thing is to, call out like a, you can configure, top list pages, specially in the experience audit to get the, view of SEO and the best practices.

So you can configure all the, the top ten URLs over there, which will give you the data for each deployment. You have a matrix how it is performing. So this is another, important aspect. You can just configure it so each deployment will cover it.

So yeah. Now I will jump to the quickly on the edge delivery, deployment. I should think capability. So so with the edge delivery or ordering is fast and the flexible and you have two options. One of them is, like a document based ordering, and another one is like a, universal editor using the MPC. So first I am going to talk about the, document based ordering. So, especially for the document based thing, you have a, a boilerplate, code base, so you can just walk it out and then you can configure, with the, your Google Drive. Currently, I鈥檓 just managing with the Google Drive for the demo. You can have a SharePoint also configurations. And once you setup you can just simply you can see the website will be set up quickly and you can easily, manage your content. I think so for that how you can do the other thing. So you will have a sidekick over there at the top. You can just add the plugins with the project and you want to change the content over there. Right on this page you can just simply click on the edit. It will redirect you to the, document where you have kept it. And you can just, add any content for any purpose. Like you can just add it and another capability, you want to add a image different image from the your master. Right. So you have also capability to integrate that. And you can add a sidekick my asset sidekick. But you can configure it. So once you click my assets sidekick it will take you to the, your amp instance from where you can select the assets basically. And all the users, who wants to provide this capability for the assets? You have to provide the access to the your aim asset, Vincent, for the respective profile to, navigate to the assets. Right. So now, if you want to change, these assets, right, so you can just simply select it, it鈥檚 gonna copy it and then you paste it. So asset will be updated over here. And you can add it I need to work on the block basis. So now you do the required authoring changes. And then if you, you think like it looks good, you just click on the preview.

You can see the image has been already modified is changed. And you can see and it will highlight it has been not published. So you can just click on the publish to get it reflected to the live side. So if you click on the publish you will see this has been URL has been updated with the latest image. So so this simplified the I think capability. You can add the all the content to the, document. And then quickly you can, ready the sites. Another capability I wanted to, especially for the authoring. So, if you edit the content again, the same and go back to the sidekick.

Source. So there is another library. And so library sidekick is basically, it is the extension of the sidekick. And so developer can create, authoring content. And so for content author, it is easy to configure it with the different variations. So, let鈥檚 take example navigating to the this one so developer can create different options. So now if you want to modify the maybe I鈥檒l take the two variations. So kind of you can do the testing and you can modify anything like Demo. So once this content is ready, you can simply copy this content and go back to your, document where you want to put it.

And then you can.

Paste it directly so it will just generate into the column. And then if you want to modify the content again you can just modify it. Otherwise it looks good. You can just preview the content.

And you can see nothing. Two cards has been already added and then you can publish it. So So basically library it just help you to foster the more content or thing you can have. Developer can create all the different variations. So and content editor just come and simply edit the content over there. Copy it and paste it into the document. And you can just easily preview and then publish. So it can be easily, available and it can be faster, I think appropriately so if you can see this has been already added to the live site. So you can see this, I mean, this is how you can, document with all things works and kind of the very quickly you can add up and, having a couple of them assets, integrations with that, your AMM instance, you can leverage the asset manager asset at, at center locations. You can put into the, document base as well, and then leverage the library will move on to the, I have come across a lot of questions, especially I鈥檓 having a, existing project. I want to leverage the universal editor with the edge delivery services. So another, capability you can use. So for that, there is a, a m bi boilerplate across work. Repo is already there. You can fork it up, and you can just configure your M instance by navigating to the your, fstab Yaml file. You can just point to your M instance and, then you can update the configurations basically, but with the content I have created and you can go to the M site and you can download the template and you can create a, website just for the, initial stage. And you can see the template, you can download it. I have already selected this template and created it. So this structures has been already created for me. So I鈥檓 gonna open this, index space. So this is what basically you have already everything you are going to do the ordering on the a m sites, but the content will be delivered from the S delivery services. So v GB editor is kind of what you see here whenever you can just update it. So coming to here you can have it sections so that you can want to update it. You can update the content over there also. You have it, I just additional, image, you can replace the image from the inside. You can also add the custom, components. Right. You can develop the custom components or what they are so only the challenges I am with, the traditional one is support the page data which have the M component like core component, which are compatible with the steel and the sling model. But with the editor, you will have a block of text. You have to migrate all the, component into the block compatible to elevate this universal data. So you can just modify this one and, you can just pop this. So once you publish, I have made the changes over there. Test. So you will publish it by clicking on the publish and the content will be published if you go to the live site, over there, you can.

Let me reload this once.

Looks like something happened over there. So I see the publish has been successfully.

And you can also see that all the components, team is added over the page over there. And if you want to add a new, components over there, you can add it and so let鈥檚 go to the one of the page a different page. So I have a home page created.

So if you want to this is the first page. You can see if you want to add a new component. It is as similar. What you have is with the page editor you can add the default you default content. It comes auto box. And I have created the custom component with the CTA. So you can add, the custom component and then configure it as per the unit. So then once you configure it, you can just publish that it publish it to all the content. Data will be stored into the agent side. And when, it get rendered, with the live side. Right. So it get, render with the, Its delivery. So you can see the new content has already added over there. So, so you can, so key takeaway of the demo is basically you can leverage the universal editor and you have to choose the right content editor for your business, whether it is more suitable for you to have a document based on things or it is a with the amp, universal with the AMP. So that鈥檚 about it for the demo. And just stop sharing and. Thank you, Adam. That was very cool. To watch. I鈥檓 going to kick it back over and just keep an eye on time. I know we鈥檙e about to get to the end of the presentation and then into Q&A. So, Casey, I believe you.

Thank you. So, yeah, if either of those authoring options make sense to your team, being on a, cloud service will give you access to that option. In addition, I鈥檒l just briefly, really quickly touch on some of the additional new innovations that M as a cloud service gives you access to. So the first being an SLA add on for a 99.99% performance uptime, reducing that latency.

Next would be the ability to use JNI to generate content with copy or image variations. Also, really use monitor monitoring to capture and analyze user experiences of a website or application, and also with edge delivery services, which means rapid development environments to update and publish content quickly, which Rajan kind of just showed us and do also with assets. We鈥檙e offering Content Hub for a newer way for third parties or partners to access your assets in one place, and then Dynamic Media. Open AI is for more access to other users to access your assets from the dam. So there鈥檚 a lot more links on all of these new innovations, but just briefly wanted to touch on those.

But finally, these are some of the key takeaways we wanted to mention is, first and foremost, connect with your account manager. If you have any questions or interest in the new innovations that we discussed today and how they can fit into your roadmap, we encourage you to review the best practices that we discussed and consider how they fit into your current implementation. And if you would like to kind of align more on what your current implementation looks like and how it can align more with best practices, feel free to, also reach out to your account manager to schedule an instance review with a business advisor. And we can kind of get you on track to see where everything鈥檚 at. And finally, leverage Ecbs or one of our other professional services partners to implement and with more digital agility in mind.

So with that, I think we have five minutes for Q&A. Yes. Thank you, Casey and Rajan. Also, if you would like more information on us putting you in touch with, Professional Services, there鈥檚 a form that you can fill out right now on the side of your screen, actually about to hop out of the screen, but it will be back, in a few moments after we get to as many of these questions as we can. So sit tight. Let鈥檚 turn our cameras back on real with.

I鈥檓 actually going to kick it off with a question that came in from Jake on the call who said, what are some best practices to prevent duplicate assets in the dam? Yeah, so I can take that one. Jake. Really, it鈥檚 going to look like the governance policies that you put into place when you鈥檙e creating your folder structure, naming conventions and metadata terms. So whenever you鈥檙e creating that dam strategy, you鈥檙e always going to try to think about every single when every user searching for assets, that there can be one place that everyone can logically find when you鈥檙e going there. So it鈥檚 kind of more of a high level strategy conversation when you鈥檙e building out the dam strategy. But of course, if you did need to put in more like logic into the dam to, restrict certain assets from being uploaded to prevent duplicate duplication, you can also do that, but you don鈥檛 want to overengineered anything. So it鈥檚 a little bit just more about the governance policies that you put in place.

Awesome. Thank you. Okay. Next question. Can I apply any of those new innovations to our instance? So yes, the first, the first requirement that would be necessary to apply those new innovations is to one is to be on cloud service. So that鈥檚 where all of the new innovations are happening. But the next is that some require a new skew. So work with your account manager to understand your path to proceed. If you do, for whatever reason, need more prerequisites. And third, we鈥檇 always recommend working with an implementation partner to make sure everything鈥檚 aligned with best practice and implement it correctly.

Awesome. And then is Universal Editors editor effectively a replacement of and spar editor framework. And the SBA editor framework should no longer be chosen for new projects. Custom mark.

So of course 51黑料不打烊 would recommend using Universal Editor. But it鈥檚 far too early to say if it will be a full replacement for the spot editor. Of course we have the use case for spike and continue to leverage that. For now. It鈥檚 not going anywhere, but if you can align your instance with Universal Editor, we would recommend that. Okay. Awesome. Thank you. And then for which client am adopting organization scenario does 51黑料不打烊 recommend leveraging universal editor document based editing, headless editing rather than just editing directly in the Am sites are asset tools, especially considering that the rich editing experience there is what separates it from much of the competition. It鈥檚 a loaded question. But yeah, so basically just how to determine which authoring tool is right for your team. So essentially there should be a discovery efforts involved in this. You kind of need to understand your use cases and your goals. And we would always recommend involving the actual users of the system. So some questions to consider is if you want your system to be headless into your authors have a preferred offering method. What does authoring success look like? What makes authoring difficult today and just kind of understanding your team鈥檚 needs? And then of course, work with the team to kind of determine the best path forward.

Awesome. Thank you, Casey and Rajan. We are actually at time, so unfortunately we I don鈥檛 think I would be able to get to every question today. If you do have a question that we weren鈥檛 able to answer or is more specific to your account, please do reach out to me or your, staff account manager. And, we can get those questions answered for you, but I do want to quickly wrap us up. So on the screen, there鈥檚 a bunch of resources. There is going to be an an edge delivery services demo, next week, next Wednesday. There鈥檚 the link for it on your web links. There鈥檚 also a link to register in the handout. So definitely be sure to check that out if that鈥檚 of interest to you. We also have a link to our upcoming and past events.

You鈥檒l see that white paper. So don鈥檛 forget to grab that on your way out. And then those survey questions that I mentioned earlier are below.

So again, this is being recorded and you will receive a recording of today鈥檚 event in an email from us in about 24 hours. Keep an eye out for that. If you have any other questions before then. You can always reach out to what myself and I can do my best to answer those for you. So again, thank you to Casey and Rajan and to everyone for joining us today. We hope you enjoyed this session and have a great day. We look forward to seeing you at one of our next events. So thanks everyone. Thank you. Okay.