Response Time
24 — 48 hours
my feeling is that technically the stackideas components (ES, EB, ED) are slowly but increasingly merging.
but what I miss over the years is a solid uniform look and feel (UI) of the components.
A lot of users have asked about better unifying the toolbars, module layout’s and many more things that could be harmonised over the components.
Why do you make it so difficult for yourself and try to build up your own experience design per component when there are some great ones out there?
if i look at tailwind as an example, where you can easily integrate component examples into existing projects and simply adapt them, saving a lot of time to work purely on the technical tasks of the components:
https://tailwindui.com/
There will soon be an interface for ecommerce too. that could be fit well for the marketplace design in ES:
https://tailwindui.com/ecommerce
jreviews are also going in this direction for the development (read about “Locality of Behavior”):
https://www.jreviews.com/blog/the-next-evolution-of-jreviews
stackideas team, save your time to worry about the design. use it for the important things: implementing new ideas from the voices, fixing bugs and improving and simplifying the interaction of the components.
but what I miss over the years is a solid uniform look and feel (UI) of the components.
A lot of users have asked about better unifying the toolbars, module layout’s and many more things that could be harmonised over the components.
Why do you make it so difficult for yourself and try to build up your own experience design per component when there are some great ones out there?
if i look at tailwind as an example, where you can easily integrate component examples into existing projects and simply adapt them, saving a lot of time to work purely on the technical tasks of the components:
https://tailwindui.com/
There will soon be an interface for ecommerce too. that could be fit well for the marketplace design in ES:
https://tailwindui.com/ecommerce
jreviews are also going in this direction for the development (read about “Locality of Behavior”):
https://www.jreviews.com/blog/the-next-evolution-of-jreviews
stackideas team, save your time to worry about the design. use it for the important things: implementing new ideas from the voices, fixing bugs and improving and simplifying the interaction of the components.
3 Replies
The replies under this section are restricted to logged in users or users with an active subscription with us
