The UIs look great, but the build seems to be catered more towards the demo or widget type items. As a good programmer with a terrible eye for design, I was wondering if you had considered building out the project using the atomic design approach and / or utilizing an import type system to allow the dev to start clean, but have a method in place to import the parts needed in a consistent way using theme variables rather than dissecting pre-built elements? For me, I wouldn't pull in the theme changer unless it was required.
Sorry if this seems like a gripe, you do great work. It's just aimed at a more novice user for right now.
I love Vuetify by the way. Always happy to see that.
Fully Coded UI Tools to create web and mobile apps
UI Kits, Templates and Dashboards built on top of Bootstrap, Vue.js, React, Angular, Node.js and Laravel.
Thank you for your feedback! ❤️
At the moment, we (Creative Tim), only think of our design in the Atomic Design structure, and the products that we sell, as simple templates.
The problem that we have with what you are asking for, is the fact that in our product, we already use "an import type system" - i.e. npm packages and libraries, such as vuematerial.io/ or bootstrap-vue.org/ or vuetifyjs.com/en/.
And the moment, it does not make sense for us, to implement the same components as these libraries already did.
Our main focus is to only change their styles, and use these components into already arranged pages so that developers could start adding their own code on top of that.
It is a very good point what you are asking, and we see that more and more of our clients want something like npm packages and libraries instead of website templates. We are in discussions of how we could achieve this, with our styles over these libraries and packages that we use in our products and we want to make this happen as soon as possible.
Best,
Creative Tim Staff
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The UIs look great, but the build seems to be catered more towards the demo or widget type items. As a good programmer with a terrible eye for design, I was wondering if you had considered building out the project using the atomic design approach and / or utilizing an import type system to allow the dev to start clean, but have a method in place to import the parts needed in a consistent way using theme variables rather than dissecting pre-built elements? For me, I wouldn't pull in the theme changer unless it was required.
Sorry if this seems like a gripe, you do great work. It's just aimed at a more novice user for right now.
I love Vuetify by the way. Always happy to see that.
Hello Dallas,
Thank you for your feedback! ❤️
At the moment, we (Creative Tim), only think of our design in the Atomic Design structure, and the products that we sell, as simple templates.
The problem that we have with what you are asking for, is the fact that in our product, we already use "an import type system" - i.e. npm packages and libraries, such as vuematerial.io/ or bootstrap-vue.org/ or vuetifyjs.com/en/.
And the moment, it does not make sense for us, to implement the same components as these libraries already did.
Our main focus is to only change their styles, and use these components into already arranged pages so that developers could start adding their own code on top of that.
It is a very good point what you are asking, and we see that more and more of our clients want something like npm packages and libraries instead of website templates. We are in discussions of how we could achieve this, with our styles over these libraries and packages that we use in our products and we want to make this happen as soon as possible.
Best,
Creative Tim Staff