Currently we are using Keen-ui as our Material Design library for Clay-kiln. The next release of it includes breaking changes. I updated a branch with these breaking changes, although I had to use the !important flag in the css on at least one property to get it to work. https://github.com/clay/clay-kiln/tree/update-keenui . Any plugins would also have to update their implementation to work with this version.
Instead of implementing this latest version I think we should take this opportunity where we would have to update the code around keen-ui elements and instead switch to a better maintained library like https://vuetifyjs.com/en/ . Changing to a new library would also be a breaking change for plugins because they would need to switch to this new library, but if we're going to force users to make changes it may as well be for a better supported library.
Keen-UI is maintained by one developer who has released 14 versions over the past couple of years, with the latest 4 months ago. It averages 500 downloads a week
Vuetify is maintained by a team who have released 287 versions over the past couple of years, with the latest just 3 days ago. It averages 135,000+ downloads a week, so there is much greater support for it.
There are plenty of other Material Design frameworks for Vue now as well, which may have not been the case in 2017 when Keen-ui was chosen, so if anyone discovers an issue with Vuetify before implementing, there are plenty of others to chose from.
TTaitFoster
commented
5 years ago 
Currently we are using Keen-ui as our Material Design library for Clay-kiln. The next release of it includes breaking changes. I updated a branch with these breaking changes, although I had to use the !important flag in the css on at least one property to get it to work. https://github.com/clay/clay-kiln/tree/update-keenui . Any plugins would also have to update their implementation to work with this version.
Instead of implementing this latest version I think we should take this opportunity where we would have to update the code around keen-ui elements and instead switch to a better maintained library like https://vuetifyjs.com/en/ . Changing to a new library would also be a breaking change for plugins because they would need to switch to this new library, but if we're going to force users to make changes it may as well be for a better supported library.
Keen-UI is maintained by one developer who has released 14 versions over the past couple of years, with the latest 4 months ago. It averages 500 downloads a week
Vuetify is maintained by a team who have released 287 versions over the past couple of years, with the latest just 3 days ago. It averages 135,000+ downloads a week, so there is much greater support for it.
There are plenty of other Material Design frameworks for Vue now as well, which may have not been the case in 2017 when Keen-ui was chosen, so if anyone discovers an issue with Vuetify before implementing, there are plenty of others to chose from.