Umbraco Commerce Technical Team Lead @ Umbraco HQ | Co-founder of CODECABIN | Creator of UMB.FYI
This post discusses controlling the display of "quick actions" in an application using filtering and conditions. Filtering is used to display items based on static attributes, while conditions control display based on dynamic runtime conditions. Custom conditions can also be implemented.
This post discusses how to enable the replacement of elements with a custom user controls in Umbraco v14. It covers updating the manifest definition, implementing the required interface, and overriding the default element with a custom component. Developers can now replace the default button element and update the manifest to use the custom component instead.
In this post, we explore the use of "kinds" to create reusable manifest definitions, reducing repetition in manifest definitions by preconfiguring settings. Kinds are registered with the extensions registry and used to prepopulate properties in manifests.
The post discusses enabling developers to override default button behavior in Umbraco v14 by updating manifest definitions, UI components, and API implementations, allowing complete customization of button behavior. Next, it hints at exploring swapping out the button component entirely in the next post.
Matt Brailsford discusses componentizing quick actions by creating a web component with a manifest property, registering the component globally, and using umb-extension-slot to render quick actions. Next, he plans to explore customizing the buttons' click handler.
Matt Brailsford suggests using TypeScript path aliases to simplify import paths. This blog post explains how to set up and integrate path aliases in TypeScript and Vite for Umbraco package developers.
Matt Brailsford discusses creating UI extensions in Umbraco v14, focusing on "Quick Action" buttons. He defines a manifest interfaces and implementations, register them, and renders the quick action buttons. Future posts will explore further customization options.