ÃÛ¶¹ÊÓƵ

Transcript

All right. Good morning, good afternoon. Hello, everyone. Thank you so much for joining us. Welcome to today’s content authoring webinar. My name is Will Harmon and I’ll be your host for today’s session. I’m part of the Adopt Your Intention and Marketing team here at ÃÛ¶¹ÊÓƵ. We have two fantastic guest speakers lined up for you. But before we jump into that, I have a few housekeeping items that I want to go through. While I do that, I invite you all to please say hello to each other in the chat. And while you’re there, I would appreciate if you could share where you’re joining from, where you’re coming from today, and what you’re hoping to learn from today’s session. While you’re doing that, I’m going to share a couple reminders. First of all, this webinar is live and being recorded. We’ll be sending out a link to the on demand recording after this webinar, mostly within the next week or so. One of the things you’ll see on your screen is a resources box. We’ve shared a number of links related to today’s topic, as well as some really great upcoming opportunities, like the AEM Virtual Skill Exchange in August, which you can check out. It’s a free digital learning event that has a ton of content for content authors, practitioners, developers, with some really great speakers lined up in sessions. So definitely recommend you check it out. That’s coming up on August 14. And throughout our session, if you have questions for our presenters, simply type your question into the chat pod on the right of your screen. And of course, if you’d like to talk to other attendees, we recommend using the chat pod for that as well, to share experiences and to get to know each other. Towards the end of today’s session, we’re going to share a really brief survey. It’s only four questions so please, please, please, before you go, make sure to take that survey. It really helps us select speakers and topics that we can include in future webinars. So that information is really, really important to us. All right. Real quick here, as a refresher for today’s topic, today we’re here to talk about how some of the most expert AEM users have successfully deployed a content strategy that is allowing them to scale across multiple regions by adhering to a number of best practices. And we’re going to talk through what those best practices are today. So I’ll let today’s guest speakers introduce themselves here in a moment. But just so you know, it’s coming. We have a wonderful session planned that will dive into a number of core AEM features and best practices behind them, including components, content and experience fragments, blueprint and more. Again, as a reminder, this session is live and will be taking questions. Definitely recommend you taking advantage of this really valuable opportunity to ask questions directly to some really, really expert AEM users. So definitely recommend take advantage of that. Of course, as a reminder, those questions will go in the chat box throughout the session and then I will provide them to our speakers at the end. All right. With that, let’s get started. I will pass it off to Mary Alice and Rajeev.

Awesome. Hello, welcome, everybody. We are going to be discussing unlocking success at scale with a global combination today. So we’ll be talking about AEM sites and what globalization means for use cases at our firm Alliance Bernstein. And we’ll get into introductions in just a moment. So for today’s agenda, we’ll kind of walk through a little bit about us. We’ll give you a little bit of the lay of the land and a background on AEM globalization.

We’re going to hit some key topics today around component administration, blueprint, workflows, content fragments, and experience fragments, tagging. And then we will walk through a couple of quick key takeaways from this session, and then go into Q&A. So a little bit about us, I’ll go first. My name is Mary Alice Orr, and I work in digital product management at Alliance Bernstein. We are a financial asset management firm. And I have been there for five years, based in Nashville, Tennessee, where Alliance Bernstein is now headquartered and work on the client group digital experience marketing team. I have a digital marketing technology background with a platform focus on AEM, Marketo and Target. I was named an AEM champ for 2023 to 2024. I’m also a user group chair for the AEM Southeast chapter. So if you live in the Southeast United States, definitely check it out. But we also have some virtual events if you guys ever want to join. So definitely not something that has to be hindered by your location. And lastly, I was a 2024 ÃÛ¶¹ÊÓƵ Summit speaker. Oh, and so fun fact for me, I once met Glenn Frey, Charles Barkley, Michael Bolton, all in the same day. So I’ll let Rajiv go next.

Hey everyone, Rajiv here. I’m working as an AEM architect, tech lead developer, whatever my role makes me do at Alliance Bernstein. I’ve been with AB for two and a half years, but I have an overall experience in AEM of over 13 years. And I’ve worked in different domains, different clients, like before AB I was in consulting. So that gave me a lot of exposure. And fun fact, like when people originally meet me or work with me, they don’t talk to me a lot, but after they start talking, they talk a lot and sometimes share some secrets, which they should not be sharing, but that’s, I feel is a good thing that people trust me.

Yeah. That is pretty much about me. Morales, you can start with the session.

Awesome. Thanks Rajiv. That is true. We all love Rajiv. We bug him probably too much. That’s probably really what he’s alluding to. Awesome. So we’re going to be talking about globalization and what that means to us at AB as I mentioned. So just kind of discussing a little bit about our global remit. We’re focused in America. So North America, Latin America, Offshore, as well as EMEA and APAC. And then we also serve globally institutionally, as well as our teams really kind of focus holistically and globally across. So we work in a variety of different ways, depending on the day and depending on the client that we’re working with. And we have to accommodate a lot of different nuances, requirements, just general, like the way that we want to structure templates and components, we have to think about that at scale. So we might be doing that on a specific day. We might be rolling out for a very specific team. We might be rolling out something for our US retail business or maybe for Taiwan. But every time we initiate anything, we have to be thinking about it on a much broader scope because we have to think about how is this going to work for other people? And if it’s not, then how can we sort of limit the amount that isn’t shared? And we have roughly around 70 plus sites that we manage today amongst 29 regions, countries, depending. We have five different audience segment types that we can kind of live in and 13 different languages that we also support. So there’s a lot of moving pieces and a lot that we have to think about. And also some of that content is very much shared across globally, or maybe it’s shared in this particular segment or region, or maybe it’s shared only in one specific country. And so all of that kind of comes into play when we think about how we want to expand and build. So currently, we have these five items that we’re going to be talking about today. Component administration, we’re going to be talking about things like policies, variations, i18n, translations, some configurations, blueprint, you know, kind of how we do rollouts, how we treat live copies, how we think about component and page inheritance amongst blueprints, which comes up quite a bit with our stakeholders. And we have to think about when we want to, when we do want to inherit when we’re when we’re okay with this inheriting and make sure that we’re very sure about that. We’ll talk a little bit about workflow management, both for data sync and approval processes. We’ll talk about content fragments and experience fragments, how we customize those with languages, how we think about variations for those, and then translations when it comes to tagging.

So for component administration, we also have to think about those cultural differences in a very specific way. So we think about, you know, with different regions, if we’re in APAC, for example, they really like bright colors, they don’t necessarily like to use black colors and components that they use, we might have different changes depending on, you know, like how much padding that a certain region wants for, you know, spacing to be more top of fold, because of the way that the language is read. So depending on translations, we may or may not be able to show as much content in a typical design. So we have to think about that a lot for things like header styles and text, and how things kind of wrap and what does that look like on a consistent basis. And sometimes we also think about things like interactivity. So again, like our APAC audiences do a lot more with kind of almost gamification type of feel, more animation, more interactivity, and, you know, our Americas and EMEA audiences are usually a little more traditional in the way they style, but are also very personalized. If we think about things like legal compliance regulations for EMEA, we have to think about GDPR. And we also have to think about with our fun pages or charts or, you know, different proprietary data, we have to think about risk disclosures and footnotes. And how do we reutilize those? How do we share them? How do we make it easy for us to manage that stuff? So we a lot of times utilize things like content fragments for that on a consistent basis. We also have a very strict segmentation setup, which I’ll kind of go into a little bit more in a bit. But we think about relevancy of content to our specific audience types. And we only allow certain content to be seen by specific audience types. And we try to personalize that content to those specific needs. And then we have things like different specific components that have variations among them to fit regional needs. So we have things like our homepage heroes, which might have a different colored font text in Taiwan, which we really don’t want to allow across borders, simply because, you know, somebody could go and put any kind of color that they want somewhere, and that’s really not the use case for that specific region. So we have to mitigate risk and things like that. And we also even display sometimes the H1 slightly differently based on how on a specific region wants to display like campaign titles and things like that within their their homepage. We have a component that we call our watch list that has funds information, you know, based on whether it’s kind of like a saved library of whether you want to see insight articles, or funds that we have and be able to kind of watch those. And all of that information is also slightly different region to region. And the content from the insights could be completely different because it’s indexed for that specific region, and not for this one. And the fun data is also very different from, you know, between continents. And we have fun cards that also kind of rely on the same thing. So you know, we could have completely we could have a strategy on a fund or we could have different type of like asset class type, and all of that within the way that we have to navigate our component variations. And then we also have blatantly regional specific components. So we have some things that we built only to be used in that region for very specific use cases. So we have things like our CTA cards and awards that we built for kind of our APAC audiences, and those don’t get reused elsewhere. And instead of trying to keep those up, and potentially augment them in other regions and kind of weigh down the code base there, we’ve decided to kind of partition those out. And so those only really exist in those specific areas. So we have to think about when and why do we want to do those customizations, because ideally, we want 80% to be shared and about 20% to be unique, or even less if we can help it, you we serve a global remit, and we don’t want to have a ton of components in our in our stack. So with that, I will pass to Rajeev to talk a little bit about I18n.

So as Meryl said, one of the challenges that comes when it comes to globalization is a balance between reuse of components and brand guidelines and authoring interface. So we have to balance between all three of them so that no one is ignored, but no one is given too much emphasis, because we need to maintain all of them at the same time. So coming down to an example from our website, like how we are using I18n. So what we have done is we have extended the out of the box I18n support from AEM. And what we have done is like based on our content structure or the URL structure where the request is being made from, we are loading a custom I18n for that language. What that means is, if we have defined the I18n for that language, you will get the language specific labels for the website. And if there is no I18n defined for that language, then it falls back to the English ones. So that gives us a flexibility where we don’t have to go and create an I18n for every locale that is present on the earth. And most of the times, like English is same for most of the regions, but sometimes it might be like I recently came to know like Singapore English is different than the English that is in US. So things like that we are handling using this customization on I18n. In the background, what it does is basically the servlet that you see on the call, you can also go on the website and do the same as you see in the screenshot. It’s a public website. In the I18n, we have an I18n, and that’s what we return to the users. Yeah, that’s pretty much at the high level of the I18 globalization piece that we are using. Marilis, do you want to go to the next one? Thanks, Rajeev.

So we’ll talk about Blueprint, which in our world is sometimes the name that shall not be named, because sometimes we fight with it a bit. But to go into kind of how we have set it up in our instance, we essentially have four master Blueprint paths. So we have our global master, which essentially lines out the majority of our site structure. So that would include things like our homepage, things like capabilities pages, or strategy pages, kind of like what we call our core pages, about us, contact us, could have kind of our landing page for our articles, landing page for fund pages. And so we can easily be able to copy all of that down in a new region from the global master is the idea behind that and be able to kind of reuse the same structure. This especially was very helpful in our EMEA audiences as a lot of that structure somewhat stays roughly the same. And we also utilize a language master, which is exactly what it sounds like. It basically assesses, it takes that global master and breaks it down into the regions that we serve. So the 13 languages that we utilize. And then we have a fund master Blueprint, which basically, again, exactly like it sounds, it serves our funds that we roll out with specific fund metadata and literature that’s tied to those funds. And then our article master, which we have a number of different categories for our articles and a number of different, you know, Blueprints types that we utilize. And so some of that stuff is globally shared, on our corporate site has probably the majority of the shared content. When you get down region to region, in some cases, there are articles we literally cannot share in a different region. Like it breaks compliance rules. And so it becomes inherently more and more clear both with the funds and the article Blueprints that we have to be really cautious of that as we roll stuff out, because we don’t want to have any kind of legality issues. One thing I kind of want to just mention, as I’m explaining this, and it’s not necessarily relevant to Blueprint, but it is kind of relevant to understand how we set up segmentation. So we have a very specific site segmentation mechanism where you can opt into segment content by agreeing to T’s and C’s, and then we drop a cookie to identify what segment you’re a part of, and then you’re allowed to read that content. And so we also, in some cases, have a redirect in place in case you view a specific article, you could get redirected to your correct segment in that case. And so segmentation is a very big part of what we do. And we have 13 different regional article Blueprints, five different regional product Blueprints. And then we’ve also created roll out and publish workflows for easy publishing. So we have a third party vendor that we utilize for some of our authoring, which comes into play for our usually kind of our article work. But that’s very helpful for us so that it’s not just if we have to do it internally, that’s great. But like, we’ve made it easy enough that we have outside an outside vendor that we trust that can come in and do this work easily. And for us, that’s a big improvement in sort of our day to day process flow. So with that, I will pass it to Rajeev to talk about Blueprint live copy and rollout.

So for everyone who knows about Blueprints, and for everyone who don’t know about Blueprint, it is more of like a copy of your content that you created once. And now you want to use it at multiple places, but you want to roll it out so that you have unique URLs for your content.

So the screen that you are seeing is you will not see a Blueprint tab or a live copy tab by default when you get a page in AEM. You only see this when you have created a Blueprint and a live copy. And what that means is you create a site and then now you want to use the same site structure for every other site that you have or a couple of sites out of it.

So what you are seeing here is when it says current live copies, what it is saying is the page that we are on, the properties of it, it is telling how many live copies are created out of this Blueprint, like how many copies are there. Now these copies are updated or created based on what you call as the rollout config that you see in the dropdown. So if you do a dropdown, you get a bunch of out of the box rollout configs, most commonly the standard rollout config, and one which we use heavily is a push on modify. As the name suggests, push on modify is like as soon as you modify the Blueprint, the live copy also gets updated. In case of a standard rollout, you can see that the rollout config is more of an on demand rollout. Now how do you decide between whether what type of rollout config you want to use? So taking our example site, so as you see the insights pages, insights pages are mostly like they are not impacted by compliance and stuff. If one of the Blueprint is like compliance, then with compliance, then you can just roll out and you don’t have to worry about it. That’s where we use push on modify. So as soon as you modify any insight, all the live copies get updated. But when it comes to fund pages, we do a standard rollout, which is on demand rollout, because not all funds get rolled out in every country at the same time. Sometimes it is at the same time, sometimes it might be after a few days, a few months, maybe. So based on your content, you need to find, determine if you want to use a push on modify or a standard rollout or the other options that are there. There’s also a push on modify shallow, which does mean that it just rolls out that one page. And if you just select push on modify, it’s basically to all the children pages also anywhere you make a change, it will just roll out to all those child pages also. In addition to that, this rollout config, you can do simple customizations as well as heavy customizations. So you can define a custom rollout config.

You could just be modifying the resource type of a page. What that means is you have a desktop page. Now you want to roll out a mobile page. So you can do that with a very simple customization, which AM allows you to do. And then you will have a mobile version of the page. Why would you need it? Because sometimes the content on mobile is not as much the content that you see on the desktop, but you don’t want the author to spend another couple of hours to author the same content again on the same page. Now, coming to heavy customization, you could also do like heavy customizations where you do the rollouts using the AM APIs, which are there. We don’t use it, but I have seen it in my previous firm where the rollout requirements weren’t fully satisfied with out of the box options. But it’s a choice that you make. You might be impacted during upgrades if you do heavy customization, if you keep customization simple as ÃÛ¶¹ÊÓƵ suggests, then you are much more safer doing your upgrades. And that’s an important criteria when you are doing any kind of customizations. Yeah, that’s pretty much it on the slide. Yeah, so this the next slide, you are just seeing the options here, the push on modify, as you can see here and the checkbox just says like copy inheritance. You could actually suspend this inheritance. You have the options on the top left where you can say suspend and detach. One of the things to note between suspend and detach, detach means you are doing it one time and you cannot set the inheritance back. But with suspend, you can roll back and you can go back to inheritance. One of the best practices or you can say as a documentation says to use suspend rather than detach. And we have personally seen issues with detach because then you get something called as an SM move pages if you have detached a page from a child level and the parent is still connected. So if you are planning to use blueprint live copies, use suspend as a documentation says and our experience also says the same thing. This is just a screenshot of how a standard rollout looks like. If you are using push on modify and you try to roll out, you won’t see these options. So don’t be alarmed. It’s not an issue. It basically says that you don’t have to roll out because it’s already auto set and it will be the changes will be rolled out automatically. So you see this kind of a screen only when you are using standard rollout. This allows you to check to what all like sections of the site you want to roll out so you can control. And that is what standard rollout is. You have a full control of what gets rolled out when.

Yeah, let’s move to the next slide.

Thank you, Rajeev. So I’m going to talk a little bit about workflow management and how we utilize it today. So we utilize it mainly for fund with our paired with kind of our literature that’s attached to specific funds as a workflow mechanism for approval. And we also use it for data sync purposes. So we have to think about things like how and when we want to create a fund, when we want to change or edit it, what does that look like? You know, if we delete, what are the impacts of that, especially because information that we have gets passed to our marketing database to get updated and then has to be like ingested for changes to render. So we have to think very clearly about that because if funds go down or a fund doesn’t display correctly with the correct data, we’ve got big problems. So the approval process for that is, you know, something that is very much important to us for that reason. We also have the ability to, you know, set flags for some of that information to be passed back again to the marketing database so that we can preview some of that data before we publish in some cases. So that helps us to be able to kind of preview what we want to see before it actually goes out. One other call out, I will just say, you know, you can also do things like workflow management like this with insight articles, like our what we call our insight articles, which is basically our blog library. We could do the same thing there. We chose not to do it simply because you can also create a bottleneck depending on how intense your workflow needs to be. So that’s just something to keep in mind of like when or how do you want to use something like a workflow. Sometimes it’s definitely necessary and especially for legal and compliance regulations. In this particular case, we absolutely needed it and had to have it, but you don’t always. So that’s just a call out to that. With that, I will pass it to Rajeev.

So as you can see on the screen, so this is what we have as our fun page metadata, I can say, as you can see, like we have developed what you call as a global form for all the countries. So and what you see here in the dropdowns are like different sources of data. So some of the data is authored and some of the data comes from third parties, all the financial data related funds and all. So what we created here is an option to switch between different sources of data, like some regions use public funds, some use some use unity and some want all data to be completely authored. So that is what you are seeing here. How this form works is we have different countries, authors from different countries or different people handling different funds. They’ll author the data here and then after the data is authored, they start a workflow. That workflow is approval workflow. What that does is it basically sends the data from AEM to our web APIs and the data sits there and when the fund is live or when it is the right time to show the fund or it is active, the web API pulls the same data and shows it on the site. So this is for the fund piece. In the literature piece, we are doing an announcement where basically we are eliminating that sync of data from AEM to the web APIs. What that would do is we would expose an API from AEM and the web API is basically a wrapper which will take that as an input and show it on the site. That gives us a flexibility of not having to sync the data between two systems and maintain it duplicate data at both the places. That is again something if you are doing or you have something of a use case like that, you should definitely try to do that so that the data is not duplicated at both the places because then there is a problem with the maintenance of data. What you need is the data at that instance. You cannot go for changing the integration at that point. So we are also trying to move out of the syncing of the data on the funds also that we are doing to the database and trying to move towards like a direct data dump from AEM and API is basically working as a wrapper for it. In terms of approvals, we do have something for a universal group and we can actually also target individual groups but as Mero said we did not want to create a bottleneck for approvals. So we have not gone to too much of approval groups or something like that for now but it is extensible and it can be done at any time. And as the workflow approvals goes like we have the usual process like you need to set up when a workflow fails or we need to give options for retries. So that is something you should consider when creating workflows. Any type of approval flows that you need to have retries because there could be a system glitch which caused it to fail. You don’t want at that time to directly contact your tech team to solve your issue. You should be able to have a retry option. That’s pretty much on that one. Mero, this can move to the next part. Awesome, thanks Rajeev. So let’s talk about content fragments and experience fragments and variations of those. So we utilize both content fragments and experience fragments today heavily to basically utilize dynamically shared content. So obviously content fragments allow us to share specific types of data or values that can be you know think something as simple as text or field values that we create in a custom content fragment model which is how we utilize our bios today. So we have a custom bio content fragment model that intakes information about a person that works at AB either in the sense of as an author or a portfolio manager. So we ingest information like their name, title, location, years of experience, things like that. And then we utilize that in conjunction with you know fully rendered pages as well as components on the site. And we also utilize it with tagging. So we can basically tag a specific person to that bio content fragment model and an AAM service gets called to render a version of a style of a bio component snippet in the UI. And so we utilize content fragments a lot and that is globally shared for our bios. So we use them not only across one code base but on two code bases simultaneously for our bio content. We also utilize as I think I mentioned earlier disclosure text and things like risks, footnotes, things of that nature kind of more bread and butter use of content fragments today. And then we also have experience fragments that we use on every site mainly in the form of header and footer. And again those are all regionally maintained and can be adjusted within specific regions and also have you know language variations applied to those. We also use it as a our bio profile highlight of kind of some interesting accolades within a person’s bio. We utilize an experience fragment for that as well. That is not technically rolled out globally yet but probably in the future. So it’s just a call out to that. But overall we utilize variations heavily and we use these two features of AAM heavily within our globalization strategy. So with that I will pass to Rajeev. Thanks. So as you can see with experience fragments what we did is we did a little bit of extension of the existing experience fragment especially for the header and footer.

What that means is like whenever you are including the experience fragment component as a header or a footer we basically check the structure the content structure with where it is in and there is a matching content structure for the experience fragment that you see on the left hand side. So we needed like different header and footers for every segment that we had. Now some of those might be some of them had different information. Let’s say for a contact information which is at the footer. So that might be different for advisor and that might be different for an investor. So what this does is like it’s kind of like you are auto selecting the header and footer based on the content structure you are in. So it basically gives us the flexibility of using different header and footer in different segments. But what we also did is as a part of that extension we made it so that you can also override a header and footer within a content substructure also. What that means is if you have a partner who wants to create not exactly a microsite but some set of pages their set of pages with their header a specific header and footer which enhances their experience we don’t have to go and set up a new microsite. Within the same content structure we can actually create a header and footer which is very customized for them and in the content in a normal content tree where we have the sites the pages we can create their microsite without having to go through the whole process of setting up a new server anything like that and within the same content structure you can use all the components that are already available to you to create the pages. Coming to content fragments so in content fragments like the example for bios which Marilu just said we are using the variations in content fragments so as you can see from the screenshot based on the url structure we are again picking the locale from the url and picking the variation that is there for that content fragment. If a variation is not created then it falls back to the master variation so here like whatever the biopage that you are seeing it’s kind of a headless implementation of content where we are using the content fragment and we have like ACS Commons dispatcher flush rule setup which says like whenever you publish a content fragment associated with the author the page is also fleshed out so that is something that you need to be careful on that your page caching in case of headless where you don’t actually have a page with the actual content you have to set up these flush rules so that the author doesn’t have to go and request stuff like an entire flush of the entire site. Now once you are using content fragments there are additional things which you can do like now graphql is also there so you could actually make your APIs return the data that you that the way you want and you can customize it you can change the field names and everything without actually doing a code deployment and it has some additional pieces like you can do a read up or like how to use graphql with content fragments and how they are customizable and how they’re performant also but as you can see like we use this for now for as you see the authors we are also doing something called guest authors and you can extend it the way you want like you can have very complex or customized not customized different content fragment inside a content fragment you can define those layers so you can actually reuse it so that is a little bit on like how you can use content fragments variations and how they can map to different languages yeah that’s pretty much it.

Awesome thank you Rajeev. So tagging.

So we utilize tagging in kind of a variety of different ways today we use it both you know in the sense of just metadata tagging on especially for our like insights articles when we’re trying to search for a specific article we have a number of different buckets of different types of tags that we utilize like things like our format for a specific article which would be an article type like a blog a white paper a video a podcast that sort of thing we’ve also got author tag as I mentioned that we utilize for our bios we have asset class for things like funds and sub asset class as well and we have generalized topics so we utilize tagging a lot just for some of those categorizations but obviously tagging can be utilized more functionally because you know when we actually render a bio if we’re utilizing the bio component snippet that we were kind of referencing earlier you would go into page properties or the component itself and tag that specific person that you want to show so we also utilize it for functionality one thing that is on technically tagging but kind of in the same vein we also utilize categorization in our site structure to kind of formulate categorization and taxonomy within our site for insight articles so we within our site structure every article can only get one specific category and we treat those as folders on the site and then those folders inherit that category indefinitely we use out box translations fields for our different language variations for tagging we also as I mentioned have the different formats with the people media and financial data and then our tagging in blueprint rolls out to live copies without any kind of custom rollout functionality associated with it so we use tagging in a lot of different ways with that I will pass back to Ajit yeah so in terms of tagging as he said like you can create tags like the same structure how we created for experience fragment where you can create node structures where it says like everything is for a specific country or you could go ahead and use these out of the box translations that are present so benefit of using these out of the box fields for translation is that when you do roll out you don’t have to modify the paths for those tags you are still using the same tag and you in your code where you are rendering it as you see on the screenshot on the right hand side where we are just showing the translation for it you can just have one code and just based on the locale you can pick the tag translation that you are you need it on the page so our suggestion is like and adobe also suggests like use the translation fields that are available with the tag properties what if you don’t have the language that you need or you are using a different locale structure right instead of en underscore us you are using en hyphen us right so you could actually add to this list of drop down like the language versions that you need you can have your custom language and you can write your code to pick those translations if that is the use case but yeah like with tagging it’s best to use these translations that you have so it uses it reduces your work in some other areas which you have to do if you are doing a custom structure for tagging and as you can see like you can a lot of those languages are already included by default so you don’t have to do anything with that yeah that’s pretty much with tagging and you can also use tagging for some other purposes like how we used that tagging in the bios you can also use it to ensure like you have data that someone is hitting and like if you have something like a implementation you have selectors you want to be careful that you are not violating any security guidelines given by adobe otherwise you might end up in scenarios where there is a denial of service attack and people are able to access your pages and or with junk selector names and able to cache those files in your web server so ensure to follow the security guidelines from adobe when you are type of headless implementation either using content fragments or along with tagging yeah that’s all awesome thanks for jeev so we’re going to wrap this up so we can get to q a but just a couple of key takeaways from today’s session so obviously component customizations and administration allow for regional nuances and requirements so obviously being able to customize the way that you need to specifically region to region or globally so that you can accommodate that in one place is very helpful blueprint helps you scale and control shared content and be able to inherit or disinherit from it when you need to workflows allow for approval processes the ability to preview specific things and also pass information back with data sync so it’s very helpful for global stakeholders and for making sure that you’re not dealing with any kind of inherent risk content fragments and experience fragments save you a lot of time a lot of a lot of effort they’re they’re efficient they also save from manual risk as well so if you’ve got duplicative content across regions that you need to share or even like within a region that you need to share but need to control those are great for that and obviously globally run sites can greatly benefit from any of the features that we discussed today so thank you guys for joining again if you’re interested in the amu user group for in southeast please sign up there’s also the virtual skill exchange that will mentioned so definitely check that out and feel free to reach out for more information i’ve got my qr code for my linkedin if you guys have any other questions that you’re interested in please feel free to connect and ask and rajiv thank you thank you so much for deep mariales that was awesome um i really appreciated the format of mariales you kind of talking through the strategy piece for alliance bernstein and then rajiv diving into the content usage i think that was that was super helpful so thanks so much for taking the time to put that content together we are now going to jump into the q a with our remaining time so we have collected a few questions ahead of time so we’re going to go through those i’m going to switch to the q a format here and before we jump into the q a it’s the old question explicitly listed for that question again we’re just trying to gauge um how helpful this content was to you if it moved the needle with with your understanding of these topics so for the purpose of that question because i didn’t list it out um let’s say one is not knowledgeable at all and five is is much more familiar with these topics okay so with that let’s jump right into the q a um this first question i believe it’s for marialis um and so for maybe a newer account or an account or a customer that’s expanding um and looking to implement globalization for the first time what areas should they be thinking about before they start is there a checklist or framework they should be following what’s what’s your advice on that yeah so i think there’s there’s a myriad of ways you can think about it i think documenting as much as you know that you need to plan for is probably the best place to start when we first migrated our first initial site migration to am you know five years ago four and a half years ago however it’s been a long time um we really couldn’t just think about the fact that we were migrating our uk sites over first we had to think about the fact of like what else are we going to be moving here and what does that look like so i think that’s really always kind of your number one step taxonomy i think was a big piece that we spent just a ton of time on um in figuring that out as well as kind of site site structure for moving forward so if you’re like us and serving a global remit and you have to think about regionally do you want your site structures to match up and you’re going to host a number of different like home pages that are like the same and you’re going to have the same type of content across all of these sites roughly you want to mirror those especially if you want to use something like blueprint you have to think about that early so i would start there just very bare bones and the rest of it sort of just comes but i guess planning for for that scale or if you’re building out a component for example that maybe you might need to to scale in a bigger way and add a variation later down the line you’ve got to think about it from that lens of like how would i maybe approach that or how would i keep it open ended to build on it so and is there a timeline you would associate with this kind of strategy i would assume it would vary greatly on the needs of the business yeah uh i mean in our case right we had like as i mentioned like almost 70 sites that we were migrating over that we had to get off of a platform that was no longer supported so in our case it was as quickly as that could possibly be done but i think it really depends on are you migrating 10 sites are you building 10 sites you know in either case um so i think the timeline is really custom to your individual use case it’s hard for me to put it yeah makes sense something i would like to say from the technical side of it also some of the things to consider is like what is the url structure that you want when you are globalizing sometimes different regions have different preferences for the url how they want the end user url to look like so that is an important consideration one of the other things is like how much of content is going to be reused is it like the content is totally different or is it almost similar um sorry my sensors just went off right um and um another thing that you need to consider is like uh seo like when you have duplicate content like we need to be careful about seo we did learn it a hard way but if that is something you should be considerate of like you’re not duplicating the content if you are doing are you doing like the best practices for handling duplicate content which is whether it is hreflang using canonicals so that is also important consideration when you are doing globalization people tend to miss that in the initial um implementation and it comes very later so i think that’s a good point to have in your when you are doing the strategy also yeah and actually as you’re saying it like the other good piece of the shared content not just shared pages but your assets and how you want to structure uh also comes very heavily into play and how you want to restrict like the user control mechanism of it as well how do you want to restrict certain people in specific areas does that matter does it not matter um as well gotcha totally yeah that makes sense um and we have time for a couple more questions but as we do that i’m actually going to flip it to this layout so you should see some more um more poll questions again please um if you have the time take take these questions before before you leave before we finish up q a here um this content is really helpful for how we can determine what topics we choose next for future webinars for future sessions whether it’s summit another webinar another virtual event um and of course align align our our amazing uh customer speakers like mary alice and rajiv to those to those topics so thanks for that we’re going to dive into a few more questions um on the more technical piece of ab strategy um rajiv what are some of the challenges you either faced in and overcame or are currently you’re working through regarding blueprint and live copy specifically um so one of the things that we did come across with blueprint and live copies was we are running too many pages now which is not good for like the overall am performance um because as we migrated like 20 30 40 70 sites a lot of those pages are now getting duplicated now it is okay from maintenance like in terms of content maintenance but from the system perspective we are running too many pages uh a lot of which is duplicate we were able to handle the seo piece of it um but now we are like actually working towards something uh new architecture of insights where we would be able to create a single copy and be able to use a single copy at different places so it’s more like not exactly synthetic resource what we have in am which again is a feature from am we are something working something on those lines so that we don’t have to create duplicated pages and all um but yeah again we are trying to use whatever um features or things adobe suggests or provides um that way it is much more easier when you go for upgrades that is like one of the primary things that we also have we try to avoid customizations too much too many customizations or we do the customizations as is supported by adobe like we did our latest upgrade and we had like just five tickets to go through uh otherwise usually when you do too many of customizations those upgrades become very costly in terms of you have to redo your customizations so that’s something again to keep an eye on gotcha yeah so it’s it’s scaling with fewer um more flexible pages as opposed to creating a new copy for each each use case and scenario that you would need a page for yep gotcha and we we also try you know we do customize in the sense of like we try to extend you know functionality of like core components but then we we tweak it we tune it and i think that’s if you’re looking to start trying to customize that’s a better place to start than trying to do things from complete scratch sometimes you do that but um i think to that end uh trying to to limit that as best as possible but framing your system to what you need um as best you can is always a good strategy yeah um okay i think maybe we can go quickly for this last question i think we have time for one more um so can you talk a little bit more about the difference between standard rollout and push on modify sure uh so standard rollout uh is and push on modify is more like a difference between um i’m not sure like um like how can i say like in databases you have triggers right and what it does is like as soon as you do some operation some other operation happens in parallel to it right you don’t have to explicitly say like do this when this happens so push on modifiers as the name says like as soon as you update the blueprint it will push whatever changes you did on the blueprint onto all the live copies that you have so you don’t have to know like i have like five different places where i need to push this change and it will be automatically uh done for you as soon as you update all you are left with is just publishing those live copies but that also takes away your control so let’s say you had five push on like five live copies which are on push on modify as soon as you updated the main one it updated all the five uh the life copies right in uh standard rollout you basically have that control while you are selecting rollout you click on rollout and you have those check boxes you can select those check boxes and decide where you want to roll it out if you don’t want to roll out a page change to one live copy that you created you can control it but it is an extra authoring step that you need to perform and push on modify you are just relieved of that authoring step and you’ll be assured that changes are there everywhere gotcha perfect well thanks that’s all the time that’s all the time we have for today’s session huge shout out big thank you to Mary Alice and Rajee for putting this content together and we thank you all for joining and sticking around please keep an eye out for more amazing webinars like this one in the future and we hope to see you in August at our digital am skill chain soon so thanks everyone and we’ll see you soon thanks everyone for your time