Request for Feature Enhancement (RFE) Summary:
Update the Sidekick browser extension when navigating Edge Delivery Sites, to include the following:- Ability to move the sidekick. Right now it's anchored to the bottom
- Have a way to show if the page that we're on can show what other pages are linked...
I am looking for some recommendations on configuring Search for AEM Assets. I know that the search rail can be customized to a certain extent. Would it also support having a little more dynamic behavior, such as hiding a panel if a dropdown value is selected? This is for AEM as a Cloud Service.
We've now learned a good deal about Agentic AI as per Adobe Summit 2025. Does anyone know what the release schedule looks like for these? I'd love to know what's coming this summer, later this year, and anything that might go into next year.
Aside from the Google Assist saying it couldn't load, I copied your code and brought it into my feature branch. It seems to work as expected. So there must be something else not happening there:
Typically, you should be able to make this change in a feature branch, and then configure the sidekick to "point" to that feature branch. That's how I've done this, to see my changes.
I wrote an article on LinkedIn about our experience with using AEM Edge Delivery Services. Do these still hold true? I think they do. I also might add a 6th consideration, which is DA Live (Document Authoring, fka Dark Alley). Link to the article: https://www.linkedin.com/pulse/aem-edge-delivery-ser...
Maybe it's possible to only show/hide on initial load for the default (1st) tab. But 75 fields sounds like a lot...any better way to split those up? Separate components?
Hi,Once you have the content in documents, then yes, you would move forward with document-based authoring, but there would need to be a plan put together that has the timeline for the events, such as content freezes. I think this would be like any other migration plan. And there's probably some upda...