ÃÛ¶¹ÊÓƵ

Transcript

Hello and welcome to the AEM Edge Delivery interview series. I’m here with Darren Kudze, a Cloud Services Architect for the Edge Delivery team on the engineering side here at ÃÛ¶¹ÊÓƵ. He’s going to talk to us today about integration with Edge Delivery and AEM assets. Darren, do you mind giving a quick introduction to yourself? Sure. Yeah. As James mentioned, my name is Darren. I’ve been with ÃÛ¶¹ÊÓƵ 13, 14 years now, primarily in the AEM space or CQ as the timers. I’ve been around a long time. A lot of people know me from AEM Rockstar in the community, and other various events. Nice to be here. From an assets perspective, James, Edge Delivery, especially if you’re doing document-based authoring on Edge Delivery services, pretty straightforward. It’s unusual in the content management space because there’s no, in Edge Delivery itself, there’s no traditional BAM. It can use assets from any number of sources. If you’re online sources, Firefly for generative AI type stuff or whatever, homegrown stuff that you’ve heard in Photoshop, Illustrator, and so on. With the document-based authoring, you literally just paste it into the document. With other blocks, components in the traditional AEM sets, just paste them in there. If you’re scrolling through the document, you see your image in context for whatever if you have your whole asset library created in AEM assets, for example. I mean, how do you get those into Edge Delivery? There’s a pretty cool extension to the Sidekiq that was created called the AEM Assets Sidekiq plugin, which puts a little button on the bar at the top of the Sidekiq, read alongside, edit, publish, and all that stuff. If you click on that, it opens up a window that once configured to an AEM, I believe it’s Cloud Service Instance or Assets Essential Instance. You can configure it either way. You log in as the user that you are, so you get context-specific assets. You only get the assets for which you have access to, which is nice, so you start with some big all or nothing. Once you have that, you can filter by type, videos, PDFs or assets too, so images, videos, PDFs, documents, whatever. You’re able to browse through them like you traditionally would in a Cloud Service or in AEM assets you probably used to. It’s calling out directly to that instance, so it’s not like it’s caching things in between everything. It’s a live, real-time interaction with that repository. Then you find the asset you want to use, and depending on what type it is, you just click on it, and when you click on it, it’ll say copy success or something like that. Then that’s on your clipboard and then you just pop your cursor in where you want it on the document, paste it, and you’re good to go. There’s a couple of slight differences there in that if you’re doing videos, since video is not like a major or whatever like that, that I don’t know if Word supports video directly without some extra plug-in type thing. When you search for a video in that, the copy process will actually put it in what’s called a bed block. It puts a little table in there, it says embedded. Great. A link to your video. Same thing with assets, can be just based on the link to the assets, which is in there posted on your assets instance, just like publishing sales. You can also leverage things like dynamic media too, so those links that you generate in dynamic media, or even in the old C7 world. Those types of links work just fine, since it’s literally just links to imagery or whatever like that. The native pasting of the raw image in the document is pretty simple, but once you get into the dynamic media world, which it has a URL, it has a bunch of query parameters for you, format, size, stuff like that. Those will have to be pasted into special blocks that render out these images for the image tag right. Perfect. That’s super useful, Darren. Thank you. I appreciate it. Sure.