Similar to native inheritance in blueprints, it would be nice to have a similar idea available within widgets - with a bit of twist. Today, the only widgets that can be added to a dashboard page are the built-in ones.

We find ourselves making similar opinionated widget instances over and over (e.g., repositories are the center of our universe, and several pages contain a table widget of repositories - the only difference being the title/description of the widget, and an additional filter or two applied to the table config itself). While having some level of widget inheritance would be nice to speed up creation, the bigger need feels like it would be ongoing maintenance. If we decide to change the displayed attributes, or reorder them, or any other UX-type change, that same change needs to be manually propagated across all similar instances (to keep the experience consistent for the user).

If instead I could configure/maintain a new type of widget ("repository table"?) that had some opinionated configuration (and allowed for minimal configuration - title/description/additional filters?), then both creation of a new instance on a dashboard page and ongoing maintenance of all of the existing instances of that widget would be significantly simplified.