Decker currently (v1.8) has a facility for making "child cards" which inherit all the widgets of some "parent" card. In principle, this offers a way to centralize and re-use repetitive structure within a deck. I am increasingly of the opinion that this feature is too rigid, and overall is not actually very useful. I am in favor of deprecating it, and possibly introducing a better re-use mechanism with a different design at a later time, but I'd like to know more about how (if at all) this feature is currently used "in the wild".

Decker users, have you ever made a deck that uses inheritance?

Honestly, I wouldn't have known such a feature existed if I hadn't read this. But I think it will come in handy when creating a blog!

I'd like to emphasize that I do not encourage users to make use of this feature! I'm trying to gauge how disruptive a deprecation will be (if at all) to figure out whether I can rip this band-aid off quickly or if I need to provide a more gradual transition.

Getting rid of inheritance will greatly simplify Decker's implementation and help pave the way for better capabilities in the future. Instead of filling out "template cards", I think it would be much more powerful and flexible to have a mechanism for making "custom widgets" that can be re-used throughout a deck and imported/exported like fonts and modules.

Based on the lack of responses, it seems safe to assume that this feature is not in active use, so I can fast-track deprecating it. Card inheritance will be removed in v1.10.

I was planning to remake a tiny book I made so that it would use inheritance for all pages. Haven't thought or planned for any other use and think the simpler implementation is a good choice!