WTH are there no blueprints for dashboards and UI

[Mr_Lemming]

It would be great if you could define (card-)blueprints with input parameters for (parts of) dashboards.
For example, you could show the door sensor, some lights and the temperature on each room dashboard by simply adding a blueprint/template card and providing the required entities as inputs. It would also be very easy to change the look and feel of all the room dashboards afterwards by simply editing the blueprint.

I know there is a way to archive this using strategies. But I would prefer an easier and more blueprint-like way.

[Ildar_Gabdullin]

@Mr_Lemming

for (parts of) dashboards

For cards - it is already possible by a custom decluttering-card.

[smartin]

@Mr_Lemming

But I would prefer an easier and more blueprint-like way.

@Ildar_Gabdullin

possible by a custom decluttering-card.

I set up and still use custom decluttering-card. Great to have it!
But it is not easy to set up, definitely not for an average user, and it is custom.

I see not only the use Case to set up repetitive cards for one self, but a tandem to shared Blueprints, where a Setup gets directly displayed in a nice, preconfigured Way.

[Mr_Lemming]

I would love to share such UI-blueprints. It would be so much easier to create a custom dashboard using community-created templates for specific needs.

[smartin]

A partial or complementary solution would be to make the !input of a blueprint available as attributes of the blueprint.
For Reference:

WTH Access Inputs in Blueprints Read (and probably write)?

Similar to WTH Helper creation in Blueprints, but the other Way around: Instead of creating Helpers via Blueprints, i think it would be really helpful to access Blueprint Inputs via Templates from outside, e.g. any other Automation, on Dashboard etc… The Inputs made could be e.g. set as Attributes of the Automation. That would open the Possibilty to make preconfigured Cards for any Blueprint, as any !input, not only User configured Values, but referenced entities, could be templated using the …

[clintm (Clint)]

The only reason I use yaml dashes is so that I can reduce duplicate code using yaml anchors. I know decluttering card and other options exist as 3rd party solutions but I believe a first party solution is better. And even with yaml templates I find myself using both. It seems wild that we can’t easily make template or reusable in a first part way. Doesn’t need to be yaml anchors or whatever, just any way that I can reduce duplication in my dashes and cards.

[ncd]

Couldn’t agree more with this. The duplication is severe and all the third party tools introduce latency and are more moving parts that can go wrong.
We really need a native solution for templates within dashboards. One of the first things I noticed playing with HA.