A Deep Dive into Tools for AEM Sites

Transcript

Hello, good morning, good afternoon, everyone, and welcome to today’s content authoring webinar. My name is Will Harmon. I’m part of the Adoption and Retention Marketing team here at Adobe, and I’m going to be your host today. We have a fantastic guest speaker lined up for you. But before we jump into the content, I have a bit of housekeeping to do. So while I do that, I invite everyone to say hello to one another in the chat.

So using the chat, I’d love for you all to share where you’re joining from and also what you’re hoping to learn out of this session today. While you’re doing that, I’ll go ahead and share a few reminders. First, this webinar is being recorded, and we’ll send out a link to the on-demand. Oh, there goes that light. We’ll send out a link to the on-demand viewing next week, so keep an eye out for that. This webinar interface is completely customizable, the one you’re seeing in front of you. You can drag windows around, resize the videos or the slides, minimize things. So feel free to make it your own. One of the things you’ll see on your screen is a Resources box. It’s probably in the top right. We’ve shared a number of links related to today’s topics, so some documentation, articles, learning paths. Be sure to check this out because those will add context that we talk about today and be helpful. Throughout our session, if you have questions for our presenter, simply type your question into the Ask the Presenter box on the left of your screen, and those will be populated for the Q&A towards the end of this webinar. If you’d like to talk to other attendees, you can use the Attendee Chat panel. There are a lot of folks in here today, so this is a great way to share your questions and experience and get to know each other. Lastly, along the bottom of your webinar console, you’ll find a few things. You’ll find additional information about our speaker, a survey. Please be sure to take the survey before you leave today. That’s how we pick topics and presenters for future sessions. And you can even give the presenters a bit of love with the Reactions button, so feel free to give that a try right now.

All right. So today, we’re here to talk about various features and functionalities available to you in Tools, in AEM Sites. And more importantly, we’re going to give you a look at how an AEM champion is putting all of these things together to optimize our organization’s content strategy. I’ll let today’s guest speaker introduce herself here in a moment. But again, as a reminder, this session is live, and we will be taking questions. So please type them into the Ask the Presenter box if you want Cindy to answer them towards the end of the session. Or you can also type it directly in the chat to hear directly from your peers and other viewers who are attending as well. So with that, let’s get started. And I will go to the next slide, and Cindy, pass it off to you. Thanks, Will. Hi, I’m Cindy Underwood. Thanks for joining me today. I live in Orlando, Florida with my husband, my daughter, two very large dogs, and a kitten named Toast. I’ve enjoyed travel, home design, and renovations, especially when they’re done. I have 25 years of AEM and Adobe CC experience. I’ve implemented AEM both on the cloud-based and on-prem instances. My AEM experience is in travel and financial services.

Let’s get working with our tools. In the AEM main menu, select the Tools icon. Then you will see the Tools side rail. According to your administration access, this may be what you see. Tools can seem a bit intimidating at first, but as you begin to work with them, they make sense and increase your control. I may have tools you don’t see, and you may have tools I don’t have access to. It may also appear a bit different if you’re in the Adobe Cloud as opposed to an on-prem instance. We are looking at the tools from an administrator user point of view. Many of these tools developers use, but we won’t focus on those today. I’ll briefly walk through what each panel is. We’re going to concentrate on a few tools after that. If we talked about all the tools now, it would take us days, weeks to go into depth into the whole hall.

Here is your general tools. You configure much of AEM assets and sites here. CRXDE Lite is embedded into the AEM and enables you to perform standard development tasks in the browser. I go in there to check on content containers and look around a little bit if something’s going on, but I generally leave it to our developers. There’s also where you can configure your search forms, tagging that we’ll talk about later. You can configure your browser templates and components. In workflows, you create and manage your workflows. You can create workflows for a variety of reasons. I have one for archiving assets, asset approval, and many other things. You can create workflows for your sites, asset approval, and if you are in an on-prem instance, you will need a workflow to create renditions, and there are a lot of workflows available.

This is the operations tool. This is your system overviews, web console, monitoring, and diagnostics. You can also run jobs and do backups. To me, it’s a best practice to run backups each night incrementally in a full backup once a week. And then we have sites. This is where you have your content launches, external link checker, context hub, and sites report.

And then there’s assets. This is where you’re going to manage your content fragments, metadata, desktop tools, and reports. You can also configure Adobe Analytics, and then GraphQL is an API query language to expose data or content fragments to downstream applications. And then your resources. That’s where you have your documentation and developmental tools. If you select documentation, it will take you right to the experience link. And then deployment is where you configure your delivery. And then security is where you administer groups, users, and permissions. There’s also OAuth, SSL, and trust store management. We’ll talk about security a bit later for administering users, groups, and permissions. And in commerce, you administer your payment and shipping if you have it on your site. And communities is where you configure your storage, communities, and templates.

And then ACS AEM Commons. It’s an open source library of pre-built AEM tools and functionality. I encourage you to look around in here. There are a host of tools to solve problems and increase your productivity. And then cloud services. This is where you administer instances that are updated and managed in the Adobe Cloud.

Let’s go into our tools. Our tools for today, we’re going to focus on three. The general tools in the tags panel, your asset tools with metadata reports panel and desktop tools. And then your security tools with users, groups, and permissions panels.

We’re going to go to tools, general, and tagging to talk about tags. Before we go too far, I want to talk about the differences between tags and keywords. I find a lot of people are confused about them. Both are useful to manage pages, content fragments, or assets. Both can be used to search within AEM sites and assets. The difference is how the information is seen once it’s published for the page or the asset. Tags can be seen by the public. Keywords are hidden and seen only by search engines after publication.

This is the tagging console. To start with, you could either create the structure of your tags manually with AEM or use an Excel CSV file and import them into the system. Namespaces are the foundation on which taxonomies are built. The namespace is to the far left, and the taxonomy builds from there. Swartags are incredibly useful, but enabling and training tags could be its own session, and it’s a topic for another day.

You start to tag in the Properties tab. You check the Tags field, and if it’s built, your tagging taxonomy will come up. You can also create a tag by typing the word in the Tags field. This should be permission driven and used with thought and care to not dilute your taxonomy.

And this is the Tags panel that comes up. Keep in mind, tags are built as subsets on the tags list with an AEM. You can select several tags at the same level on the list, but you can’t select tags on another level at the same time. You have to select a tag, go back into Properties, then back to Tags for each selection. If possible, keep your tag structure somewhat flat to increase your speed in tagging.

To create a new tag, go to Tools, Tagging, Create, and select Create Tag. Here’s a few guidelines for creating tags. Tags must be unique. They can’t be anywhere else in your tagging taxonomy. It’s also best to reduce the number of tags related to the same idea. Don’t use colons or forward slashes. They are used on the back end and are suppressed to the UI. Newly created tags need to be activated and published before you can use them in a page or asset. Make sure to package tags with the pages that use them. You can move tags, but unless the tag is not referenced anywhere else, it’s best not to delete them. Content fragments are assets. So when authoring for a headless project, you can add this tag the same way you would any other asset. And tags can be controlled by applying permissions to control the creation and the application.

Now let’s talk about metadata. We’re going to talk about how to apply metadata. There are three metadata panels within the Assets tool, metadata schemas, folder metadata schemas, and metadata properties. Now I’m going to be saying the word metadata a lot. So we’re going to walk through this, and we’ll figure it out together. But metadata is going to be said a lot. I want to start talking about metadata with a visual and a story. I worked on a project where the assets I worked with published to a website and online travel agencies. To get the images to the website in OTAs required a lot of information. We even had to supply longitude and latitude. To enter this information over and over for each asset would be time consuming and fraught with errors. If any of this information was inaccurate, it wouldn’t publish to the site or the specific OTA. The process I’m about to describe solved for this, and we’ll come back to this image later.

To understand how this works, let’s start with the Properties panel. I’m going to get very basic to create the workflow. Assets have properties with fields where the metadata information is, like we see here. There are several tabs for all the metadata. Out of the box, there’s Basic, Rights, IPTC, IPTC Extension, Insights, and References. You can also create custom fields and tabs to meet your specific needs. Metadata can be added directly in ABM. Some metadata will come with the asset, or you can embed the metadata before the asset is added to the system.

Here’s the Metadata Schema Form Editor. From here, you can build the forms for the metadata, like we saw previously in Properties. It can be used out of the box or customized. Out of the box, there are three basic metadata schemas, content fragments, collections, and default. It’s simple to drag the fields on the form or rearrange them, then create settings for each field. I find it’s best to start with the basic schema and build from there. And here’s the Settings tab. There’s a field label, the name of the field, and property to map it to, and a Rules tab. For each field you create, you will set the rules for how it will act.

Folders also have properties with fields for the metadata information. You can see the tabs we have right here.

Folder Metadata Schemas. This is the same type of Form Editor where you can build forms on the folder metadata. Again, you can drag and drop to create the fields you need, then add the settings and the rules.

Metadata profiles marry the two. If you want to have the folder metadata to be inherited by the assets, both the folder and the assets must both have the same fields. So keep in mind, folder metadata and the asset metadata forms must reflect each other. With the metadata profile, you can again use a Form Editor. The magic happens when you apply the metadata profile. Then all the information on the folders will automatically cascade into the assets field when the asset is created or reprocessed.

So coming back to this image to bring it all together, you can see I’ve used the Metadata Schema Editor to create a new tab in Properties and added the fields I needed. My parent folder has all the same information. So using the folder metadata schema, I add the fields and then fill it out when the folder is created. Using the metadata schema, I added the fields that need to be filled out when the assets created in the dam. Then I apply the metadata profile. Then any information on the folders will be inherited by the assets. I added all this information once to my folder. Then any asset I add to the folder will inherit that information going forward. It may sound a bit complicated, but once you’ve built it, it’s really brilliant. Now let’s talk about reports.

There are a couple of places and tools you can add, you can create reports, sites and assets. In my workplace, we have created predetermined page reports within sites that certain user groups have access to. We can report on expired assets, modified, excuse me, expired report, report expired, modified, or published pages, or audit reports for our website.

In the asset tool, our reports are somewhat predetermined with customized capabilities.

Our predetermined reports give us a launching point. I choose the report I need and then hit Next.

Here you can see a few reports we’ve already created. One for the creative team and another for is a content fragment audit. Hit Create to start a new report. This works the same way for either sites or assets.

Fill out the fields, decide if this is a report you want to run regularly or ones for a specific user time period. You can also choose to set schedule a report. After filling out the information and choosing the path and date range, hit Next. There are standard columns and custom columns. I usually want to dig deeper or need specific information, so I use the custom columns a lot. The columns all map back to a specific field in your metadata. According to your builds, it’s somewhat tricky, and you may need to test where the information is pulling from. I usually document where I’m pulling the information since it may be a month or more before I go back to run that data. And heaven forbid something’s misspelled in the build. It’s happened, and it’s quite a challenge. After I finish with the columns needed, hit Create. There is a report initiated notification. Hit OK, and it will take you back to your report screen. When I select my report, I have three choices, view, download, or delete. If I select Download, it will give me the report in a CSV format that I can open in Excel or Numbers. If the report is something I’m sharing, I convert it to an Excel workbook. Kind of fussy about my reports, so before I send it out, I make them audible, and et cetera.

Reports can also be viewed on screen. If you are using a report created by someone else, if you select Overview, you can tell what columns are configured. And now let’s go on to Users, Groups, and Permissions. According to your admin rights, you can create the user groups and permissions. You can also access this panel to verify users and what group they’re in. Or you can look at the permissions to see what each group can do. It is very important to define the permissions for each user role and then create the user group. Each user should only have one group with defined permissions. If you give a user more than one group, this will cause confusion, and they may have access issues.

The user can be given access to sites or assets. You can start with defining each role that a basic user can use. They start with read, create, modify, delete, or publish. Once you define the roles for a user, you can create a group. The basic groups are admin, editor, and viewer. You can create custom groups with a combination of capabilities, plus your read, create, modify, delete, or publish permissions. Then each user is assigned a group. That is defined with access and capabilities. They may be able to add assets but not create content fragments. They may have read-only access or can only see certain folders. It’s a time-consuming process but well worth the effort that it takes to clearly define what each group is and assign it to the user based on their need to function in sites or assets.

There is also a security panel where these user groups and permissions are administered. Frequently, it’s the job of a company’s security team to control access. But you must understand that the security team is not required to access the permissions. And that’s what you must understand and predefine the permissions and user groups before anyone is given access. Here is an example of a section of a spreadsheet I’ve created to show some of the permissions and user groups who have them. You can see at the top, there are my different user groups. And then down to the side, you can see what their permissions are. Some can create content fragments. Some can edit the tagging. Some can create a list of things that they can do, whether they can reorder, create a collection, impersonate. This list actually goes on much longer than this, but this gives you an idea of the things you have to think about as you’re creating. And now let’s go to the desktop tools.

Two tools I’m excited about are the Adobe Experience Link, excuse me, are the Adobe Experience Manager Desktop App and Asset Link. Throughout my career, I’ve used what is now Creative Cloud. In many ways, it’s given me a unique perspective of the tools we use. Adobe Experience Manager Desktop App works to make the assets available on local desktops and can be used with Adobe Creative Cloud apps. What’s great is you can upload new assets from your desktop. Assets can be previewed, revealed in your Finder, opened in other Adobe apps, changed locally, or placed in documents. Any changes are saved back to the dam and a new version created with correct user permissions. It also has the ability to bulk upload and even supports nested folders. This is a time saver, and it’s also great to be able to work locally.

Adobe Asset Link is an extension that will connect any cloud-based Experience Manager assets environment that the user has entitled into. All environments that are accessible appear within the Manage Environments view of Adobe Asset Link. Asset Link is natively built for Creative Cloud. It was announced at Summit that integration between assets and Frame.io is also coming. This is a great benefit that you can provide to your creative team. It keeps your assets as a single source of truth, since users won’t be saving assets to their desktop. The usability will create adoption for your dam and increase speed to market.

Final tips for today. Explore the tools. They’re not scary, and they have so much to offer. Plan your user groups and permissions. Think beyond Read, Create, Modify, Delete, and Publish to all the capabilities. If you have a lot of information to add to assets consistently, create a metadata profile, apply it to the folders so the assets will inherit all the information when created.

Thanks so much for taking the time to talk with me today. I hope I’ve answered a few questions and made the tools a little easier to use.

Great. Thank you so much, Cindy, for that super, super helpful content. We have a few questions that have come in from our audience, and we’ll take those now. And if you haven’t had a chance to submit a question yet to our presenter, you can do so now via the Ask a Presenter profile or Ask a Presenter panel, excuse me. So get your questions in now if you haven’t already. Also, if you have to leave, please don’t forget to take our short survey. It’s just a few questions, and it helps us select the best topics and presenters for future sessions. With that being said, we’ll launch right into the Q&A now with some of the questions that have come in so far. So Cindy, starting with this first one, when you create a tagging taxonomy, can you have more than one namespace? Yes, you can. And although you can repeat tags in the namespace, it’s best not to. It can cause confusion, especially if it’s something that you’re going to publish with.

And then someone asked if you could explain the difference between the AEM desktop app and Asset Link. So both give you access to the AEM locally on your computer. The desktop app lets you work on the assets locally through your Finder. Asset Link brings the assets into the Adobe CC apps. You can see the asset panel within each program. Designers can link from the AEM assets right to InDesign without downloading the file. And when it’s time, a PDF can be created without downloading all the information or all the assets. And when you go to package a file, it will collect all those assets to make them easier to send. It’s the same with Photoshop, Illustrator, XD, and hopefully very soon, Frame.io.

Great, getting into some more chat questions here. This one is a multi-parter, so we can take it step by step. First step is, what would be the situation where one would choose a metadata profile versus a metadata schema? And let me read the whole thing out in case it affects me. Yeah, so that would probably help a little more. So what would be the situation where one would choose a metadata profile versus a metadata schema? Can I use both at the same time? What is the relationship between the two? Right. So your schema is going to be what shows in your properties consistently. The profile is what can be applied to the folders so that you can put that information. You create your profile, and it’s different from your schemas. So the profile is something that you use to apply to your folder, like I was showing earlier, so that the assets will automatically inherit that data. It’s more of an overview as opposed to your metadata schema is where you’re living and breathing in your assets.

Thank you. Here’s another one. Someone, an attendee, is in the process of setting up smart tags for their dam with about 20,000 existing assets to auto tag assets upon ingestion. Is it possible to retroactively apply smart tags to existing assets? And if so, how could he go about doing that? Well, have you tried reprocessing? A lot of times when you reprocess, it almost acts like they’re being added new again. So if you’ve trained your smart tags and you have your smart tags functioning, I would try reprocessing, and chances are it will take those smart tags.

And this one is interesting. This is kind of combining some of our newer functionalities. And I don’t know if you’ve used Sensei yourself, Cindy, but someone’s asking if Sensei can be used to automatically generate alt text for assets. Again, it goes back to how you trained Sensei. Sensei, yeah, I have worked with it. So your alt text, it acts like tagging. You would have to train it like, OK, I’m adding these assets. When I add this type of asset, then Sensei would know it and then add your alt text. So again, with any AI, you have to do some training first. Another question from the chat. Since we have a lot of users that want to define tags themselves, what are some practices we can use to make sure that they are not lost on version updates? Yeah, well, there’s a couple of things in here. So first of all, if you have people wanting to add tags, you have to make sure it’s permissions-based, because you can say who can add a tag and you can’t. You want to be careful, because you don’t want to delete tags. You want to make sure that you’re You want to be careful, because you don’t want to dilute your metadata schema. So you can do that. And then when you update, so that’s where you really can’t, when you’re individually adding, it’s not a good practice. Because when you have your whole tagging taxonomy and those things are correctly created, when you update, they maintain. Things you kind of add on the fly, it’s easier to lose as you do an update.

Can you set up auto-tagging based on the folder, so at the folder level? That’s a good question. I’m trying to think. I think you can, but that’s something that I would need to verify. Great. Yeah, I just marked that down as something for possible follow up. Yeah, sorry. I tried to know.

Another question. How does a workflow setup to archive expired assets work? Is that something you’ve used in the past? Yeah, yeah, I have that now. So you create the workflow. And what you have to do as you create the assets, and I put two things. I put a review date that’s about a month ahead so that we can say, hey, these assets are about to expire. Do you want to keep them, change the expiration date? And then the second thing you put in is your expiration date. When that expiration date comes, I have a report that comes to me that says, hey, in the next few days, these assets are going to expire. And then I share it with the group, making sure where we want to be. And then they automatically go down into my archive that I’ve created. And it’s almost a mirror of the assets dam. So what happens is it will move down there. It will move into the correct folder. And then it has an expired tag on it. And so then it’s living in my expired assets. I have a rule that sets that keeps it for 10 years. In the business I’m in, we have to really keep things. So then it just moves down there. And it’s an automatic workflow. It’s really great.

Great.

Actually, this one is from the chat directly. When should we ideally create a separate namespace for tags? So it could be according to what your business need is. You can have several namespaces. And it could be different parts of your business. Like I said, it’s really best to not have tags in two places. So if you have something that’s really directed at a different part of your business, that’s when a namespace comes in. Or if it’s for a specific project, then that’s when you need a separate namespace. I would think that your kind of enterprise namespace needs to be that thing that works across the board. It’s consistent. It’s maintained. And then you could do another namespace for a different reason, a different website, whatever it is you need.

Great.

How do you set permissions on tags so that users can only add tags and not edit tags at all? So that does go back. It’s not so much permissions on the tags. It’s permissions you’re giving your users when you create your user groups. So then you can say, yes, this person can type in a tag. This person can edit tags. This person create new tags. That goes back to your permissions that we talked about and thinking through all of those capabilities and what you want the people that you work in the site can do.

And then I like this question. According to you, Cindy, do you have any best practice you’ve made sure around naming your assets that you’ve identified over the years? Oh, yeah. Sorry, it’s a hot topic with me. Oh, it might be. Yeah. So for me, the lowest common denominator is everything has to be lowercase, a dash between each word, no spaces, no underscores. That is my lowest common denominator. Because if you have odd characters, can’t have that either. If you have those things and you look at your path with an AEM, it automatically fills it with odd characters. It fills it with ampersands and all kinds of crazy stuff. So you want to have just lowercase dash your extension. Then you’re not going to have a problem with your paths making sense for your SEO. If you have a screen reader going on, they can read it. So I also suggest making it understandable, but not so long that you have an entire sentence in the name. I’ve had some assets provided like that. Also that it makes sense. Don’t do image one, image two, image three. You want to have it somewhat relate to either the project or what the image looks like or what the content fragment is about. Whatever it is that you’re working on, have it make some sense.

Thank you.

And this one is more open-ended. But do you have any more best practices that you haven’t already spoken about today that you could share about workflows and how your organization is using and optimizing workflows? Yeah. Yeah. I mean, you have to kind of, as you’re working through your workflows, you have to really, it’s a process. It’s A, B, C, D. So in order for it to work correctly, you have to think about what you need done and where it needs to go. So like if you are creating a workflow for renditions, you need to think about, OK, what are the renditions my website needs? Is that rendition going to be JPEG, PNG? So you have to kind of think through the process. And it may take some trial and error. Will this work? Won’t this work? To accomplish what you need to do. I mean, there’s so many different ways to do workflows. It’s really hard to say this is all best practices. But just think about mapping it out. Just like you think about mapping out a website, you want to map out what that workflow is going to do and what you’re looking to accomplish. If I want to archive my assets, I have to think, OK, how do I tell it to archive? Where am I telling it to go? How long am I going to keep it? So all of those things kind of go into thinking about how that’s going to work.

Great. This is actually a follow up to the last question about best practices for naming assets. Someone was wondering if it was a good idea to have the same name path if, say, for example, you’re working on different countries. Or do you think it should divert at that point? Or is it up to the preference of that organization? Well, it’s also according to how complicated it is. I mean, if you’re just doing Spanish, that’s a little more simple. If you’re international and you’re working with 17 different languages, then you have to think about what you want to do there. I’m always a proponent of keeping it as simple as possible. If it is possible to keep everything with the same name but have an extension at the end that tells what language it is, then I think that’s great. I mean, do that. But if it’s going to cause confusion within your system, then you have to think about what is my best way I want to do it. Would I want to maybe put it in a different folder? I mean, and also you don’t want to duplicate your assets too much. So you could also have versions that it’s one asset, but within it, there is a Spanish version, there is a European version, or whatever you need. So there’s a couple of different ways according to what you need to do.

Gotcha.

How about this one? Do tags have a limit or a max amount of tags to apply to assets? You can apply a lot of assets. Excuse me. You can apply a lot of tags to assets. Your list can be super long, but your tags kind of need to be really one to two words at most.

Gotcha. And this is, I think you touched on this earlier, just for clarification, did you mention Frame.io will have an asset link integration? Right. OK. That was the question just confirming that they understood that correctly. Yeah, it was announced at Summit, and I’m super excited about it because our video team already works in Frame.io. So I am on the edge of my seat to get the two together. Awesome. Excited to see more about that when that’s further along.

Here’s another great question. I’ve been attempting to train smart tags to tag assets, but have been unsuccessful. Do you have any advice on how to successfully train smart tags? Any strategies you’ve deployed for that? Yeah, with any AI, you have to, again, trial and error, but you have to be kind of specific about retraining it too. And I would start with something very simple. Start small. Don’t start with the big step. Start with, and this is super simple, but this image is blue. And then just begin to, or if it’s your namespace, if it’s your company name, start with those things and then begin to build it. If you give AI too much information at once, AI is great, but it’s not that smart. So you need to kind of, it’s a system. It’s step by step to get to where it’s trained correctly.

Here’s another one from Chad. Is there a restriction on how many assets we can have inside of one folder? I know this. I think it’s 10,000. But again, if you have a lot of things because it lazy loads, if you have a lot of assets in one folder, you’re lazy loading for days. And if you want to reorder, then you’re kind of reordering for days. So for me, a best practice is to keep the folders manageable.

Great. I’ll do one last call for any final questions for Cindy. I’ll give it a few seconds here and see if any more come through the chat or the Q&A.

All right. Cindy, so much. Thank you so much for taking the time to put all this really wonderful content together and share it with our users. As a reminder, please take the survey before you leave. And we will have the slides and recording live on Experience League within a week or so. And we will send that out in an email to you shortly. And actually, as I say in that wrap up, a couple of questions have come in. So Cindy, if you don’t mind, I just have a couple more for you. Sure. And then we’ll wrap for good. OK. So another question just came in. Will moving an asset to another folder break the original URL? If you have set your system where when you move, it cascades, you’re fine. If it’s embedded, then you need to provide the path to whoever is working on the site. Or if you’re working on the site yourself, you’ve got to update that path. What I typically do is if I’m moving something and I know it’s published, then I will have what I have published do the move, confirm that it’s cascaded, reload the page, and then make sure nothing is broken. Great. And then we’ll do a final question here, if you can speak to it. Cindy, but is there any best practice you can share about tagging content fragments? Yeah. I mean, content fragments are an asset just like anything else. So you can still use your same tagging taxonomy. Some of your tags may go to what business unit it is or the audience that you’re talking to. And then you can also use the tag tag. So if you have your content fragment and I want to publish it to a certain area of my website, then I have to have that tag ready to go, put it into the content fragment, and then when I publish, that tag will go with it. Great. Thank you. Thank you so much, Cindy. With that, thanks again to Cindy. Thank you so much for attending. We hope to see you at the next session. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. We’ll see you at our next webinar, and we will send out all of this recording and slides to you next week. We hope to see you at the next one. Thank you. Bye. Bye.

Bye.