#32 Stepper UI Examples and What Makes Th...
1 messages · Page 1 of 1 (latest)
I'm sure this could be handy for situations where each step is well-defined.
That said, HA is often a configuration UI, not just a task UI. Many of these (like setting up an automation) would be a "draw the rest of the owl" kinda scenario. HA doesn't decide when you're done setting up, only you can know that.
Well, @wooden atlas beat me to it. I do think that we need to work on reducing dead ends by providing more clear direction on what could be done next
Im some ways there are "steps" by giving setup pages a chronological order. Easy example would be creating a new tile card. We see this layout in many areas inside HA already but there are for sure things that can overwhelm users.
I feel we can already go there without a proper wizard, which is always problematic in the sense that leaves you with a "now what" feeling - my goal would be that you can understand what the dashboard editor does in a proper way so its easier to move on and do more things on your own, no handholding needed
that's what I'm doing in my research btw - leave people in front of dashboard editor with tasks and locate the biggest issues
I have one topic I'm going or next that goes in the direction you @wooden atlas and @vocal island are mentioning, and is better suggested cards and a better path to pick what you want to control -- here's a card https://github.com/home-assistant/roadmap/issues/75 but there will be a lot more things to do
Does that include getting rid of all the outdated cards, or unify them? IMO cards are just a presentation of entitiesand it's attributes. A sort of graphical shell for presentation.
But I'm not sure (after 3-4 years of using HA) if this is exactly the case...
I am not a huge fan of gigantic scopes 🤣 right now I feel quality of the experience can be hugely improved if we just change how things are presented
I am also trying to create scoped solutions so they are discussed easier
but yeah I could see a card celanup at some point - no idea how, I will open a discussion at some point to get your inputs
This doesn't have to be a big discussion. The goal could be "yes" or " no".
the path to it... Wel... That's a whole other story
oh yeah the answer is YES then - but not now
just because with research at 50% I can already sense that is not the main culprit
I see... It would open up a lot of possibilities for the themers among us. But also makes changing cards appearance much easier...
Cards could be templatable/themable and stylable having some sort of templating mechanism, and does not force you to develop just another card, because the layout isn't exactly what you are after...
We did just that in another open source system where I was working on back in the days: Drupal
A bit different, but the goal was the same
( I did design/develop the Garland theme (together with Steven Wittens) for that in my most active days there)
oh cool! I will ping you then hehehe. BTW the roadmap tickets like the one shared there are open, feel free to comment or participate - surely we don't need to do everything there (nor can, tbh)
Feel free to ping me if appreciated.