
Keystone's UI Kit / Design Language needs a home and documentation.
packages/{PKG_NAME} with README.mdName and logo are quite close to Archlinux. Not sure if that's a problem..? Maybe something that emphasises the location of the keystone could be used to distinguish.
Totes awesome other than that!
Dammit...
"There is no such thing as a new idea."
--Mark Twain
@BorisBozic @lauren-tm halp plz?

#yourewelcome #notjustaprettyface #whenengineersdraw #whogavethatguyapencil
Would this be helpful to use Storybook to showcase arch-ui components?
@gautamsi I think the plan is to rename arch-ui to keystone-ui and use docz. It's not something we are going to get to soon so if you are interested in doing this I would definitely welcome PRs. 馃憤
Important note: The plan is to only rename keystone-ui once we refactor arch-ui a bunch and properly decide what should exist there and what shouldn't.
I will try to add docz support and not rename anything now.
may still be good to have arch-ui name.
It looks like there hasn't been any activity here in over 6 months. Sorry about that! We've flagged this issue for special attention. It wil be manually reviewed by maintainers, not automatically closed. If you have any additional information please leave us a comment. It really helps! Thank you for you contribution. :)
For context: The plan, eventually is to have a UI library/design system (probably elemental) that underpins Keystone. This probably will not be an immediate thing and will happen gradually as we improve the adminUI and less gradually if we eventually make that leap of refactoring onto a different platform (I don't think that will happen soon)
Regardless of the above I think it is safe to say that there are no intentions currently to further promote archUI
Most helpful comment
#yourewelcome#notjustaprettyface#whenengineersdraw#whogavethatguyapencil