It is often the case that there are sets of properties applicable to many blueprints. For example, documentation related URL properties could be created and attached to each blueprint without a need to copy-paste them. This capability is known as a Mixin (see https://en.wikipedia.org/wiki/Mixin).

A Mixin nicely complements inheritance, since there is no need for an additional data type just to enable reuse of implementation. In other words, thankfully to mixins we could eschew implementation inheritance, which on long run usually causes maintenance problems. For an idea talking about inheritance see https://roadmap.getport.io/ideas/p/native-inheritance-in-blueprints