Where are my Adobe AEM components being used?
Let’s face it.
If you author in Adobe AEM, you know how messy it can be when using components to build a web page.
And good luck trying to keep track of what was used and where.
But when you’re asked this question, you’ll be happy you listened to this quicktake.
I’ll tell you about a little unknown report that you can run today, in 1 minute, that will clarify how your components are being used and where.
Over the past decade, I've helped dozens of companies better understand Adobe technology and project delivery. Along the way I've had the opportunity to see a lot of what works and a lot of what doesn't. My goal is simply to share with YOU what I've learned. And I hope that gives you back a little sanity in your day.
💡 What do you think? Share your thoughts in the comments and let's have a conversation about it.
___________________________________________________________________________
Transcript:
So you manage Adobe AEM. You're a product owner, a development lead or marketer. And you're asking yourself, where are my components being used and on what pages? Well I'm going to tell you exactly how to find that information out.
All right, so let's get into it. I'm often asked by clients, Hey, how can I optimize my component library? It's a complete mess. I have way too many of them. And it seems like I can't reuse any of them on any different pages.
Now, this is a bigger topic than we can cover in just two minutes.
But the first thing I point out is a little unknown report that you can run today in AEM as an author that will go a long way of making sense of your component library and what components are used on what pages? And where, so then you can use that for optimizing, improving your page speed or just doing a component audit.
Okay. So the name of this magical report, wait for it. Component report. Not the most original name, but trust me, this is a report that you're going to want to leverage and run. So let's get into how you run it.
You're going to want to head over to the tools console and select reports. Then new, give it a title and a name and follow any of the workflow steps as was required to create the report. You can do some configurations in terms of the columns and sorting and those types of things.
But what you're going to get is the ability to see who authored the component, the component path, right? Or the URL in which that page is living on, the component type, the last modified, and then ultimately the page name that the component is. Now you can export this into a CSV file and then go ahead and modify it in Excel as needed.
But the key value as you can probably already think through is you can figure out which components are being used more often and on what pages. Then you can take that information and help optimize the page speed for SEO, as an example. If you're redesigning the site, you can create a list of components that you'd need to make sure that you can test and redesign CSS, clientlibs, those types of things.
As well as this is also helpful for doing large regression testing across your site. So hopefully you found this useful. There's a lot more reports. I'll cover those in future mini pods. Thank you for listening. If you have any questions, please leave them in the comments and we can discuss.