How can we let extension developer creating new Authoring Experience using our new UI Extensibility feature deployed as an AppBuilder extension? This practical presentation will go through a full use-case of integrating the AEM with Generative AI to generate assets.
This will cover all the tools that are available to our extensions developer.UI Extensions will enable you to modify the UI to display new components. Runtime will take care of the asynchronous communication to external systems. AppBuilder will make sure your extension is available to anyone in your organization.
The learning that we will conclude with is that it has never been this easy to augment your AEM Authoring experiences dynamically, without requiring deployment.
Does this only apply to Content Fragments UI and similar? (Adding custom "Content Finder" rail tabs etc (TouchUI /editor.html) is a pain, so it would be nice if we have something for that as well.)
Do we have to use AppBuilder, or Extensions can be created/integrated via custom implementation?
You need to use app builder ( it works really well!) You don't need to use adobe io for backend though (but then you will have a bit of extra work with authentication)
Hum, good questions. In the end the only thing that makes an extension is using the uix-sdk client, have it hosted publicly. You would then need to register manually your extension with extension registry, I don't know if this API is documented publicly. This is the extension registry is the service we use when "publishing" an extension from console developer. In short probably, but you would loose of a lot of the added value of AppBuilder.
Any plans for 6.5?
Is this documented ( extension points)?
Are the API calls towards AEM running in the logged in user‘s context?
Is there any permission system behind the workspaces? AFAIK there is no way, and i fear, that a developer accidentally deployes into a production workspace.
What impact does e.g. the demo extension have on loading authoring UI?
No, this is only for Content Fragment Admin and Content Fragment Editor with plans to include Universal Editors.