Done property editors on v14 now - https://dev.to/kevinjump/series/26366

Great guide! You mention here that you have seen properties (configuration?) defined both on the schema and the UI manifests. This is because you can define configuration on either, say, if you just want a UI configuration that the server doesn't need to know about, it's perfect to put on the UI side. A good example would be a rich text editor, which can have configurable buttons on the UI that doesn't matter as to how the data is processed, so you would create a UI property editor for a specific implementation such as TinyMCE, ckeditor, or others, which saves the data down to a simple Umbraco.RichText property editor. In doing so, you can have multiple UI implementations using the same schema. https://cdn.discordapp.com/attachments/1205291816291926036/1205426003946766397/image.png?ex=65d85373&is=65c5de73&hm=96e2085c8218cbab23d83cb4ece89c6330034eb6afccaa0d8e4bf26dbac77369&

Ahh. that makes sense ! 👍