First of all great news! Really excited about the direction things are going! I do have a small (non-grumpy) concern though. We’re just wrapping up a fairly large project with quite a few custom property editors, custom sections, and backoffice extensions. Once it’s closed, we’ll likely move into a support & maintenance contract (which we usually recommend anyway). My only hesitation is this: if significant backoffice changes land not long after go-live, clients may ask why we need to “fix” or refactor parts of a project that was just delivered a few months earlier From your perspective, what’s the best way to stay ahead of potential issues? And just to confirm, UUI 2.0 will only be fully available once v18 is released (currently planned for June 25), correct? Would love your thoughts on how you’d future-proof custom extensions at this stage

Hey, thanks for the great questions! So first of all, the UI library 2.0 is intended for Umbraco 18, that is correct. The library will - from the perspective of the CMS/Backoffice - not bring any changes to how extensions are created. The element names stay the same, for example

<uui-button />

is still there and so on. The reason to bump this version as a major is that we are refreshing the styles of the UI library and changing the way we work component source files internally in the UI library. The public API stays largely the same except for the two long-deprecated components (uui-popover and uui-caret), which have had replacements ready for more than a year now. That hopefully answers your question around what we do to support extension developers. I fully expect that any code you write now will work in version 18, at least in terms of using UI components.