Control-level overrides is exactly what I'm trying to achieve with using yaml and anchors, that's very interesting! I don't suppose it would be possible to get a sneak peek just to learn how you've solved that and also give you some feedback if you're interested?
Creating canvas components in a library is definitely something I've considered, but there are a couple of things lacking in the maker experience department - like being able to define categories and icons to make it easier for the makers to find and use the components. If you make an app in Teams and export it in a solution and then import that into the makers portal you get a new menu item called "modern controls", it would be nice to be able to do something similar to that as well.
And OnReset seems a bit unpredictable if you have a component with a fill colour that's declared in a variable in the OnReset property. I've found if I have a custom "trigger" property with "Raise OnReset when value changes" ticked off I don't get the black background you normally get where the component is used, as long as the property type is Date, Screen, Image, Video or audio, Record, or Table. It needs a value, so {} for example for record or Now() for Date. And weirdly enough if I call the notify function in the OnReset property as well as defining the variables, that only gets called if I use the Screen Type, but the variables are still initialized with the other types as well. And I still need a hidden button that calls Reset(MyComponent) inside the component to initialize the variables while working on the component.
But I digress, I appreciate your work, I haven't really found a lot of people who focus on the design aspect of Power Apps so this is very inspiring 😊
