In the effort to create a re-useable UI component library, @penumbra-zone/ui package was made. However, it's grown a bit bigger than expected. It's time we split some things out.
1. @penumbra-zone/ui
Keep components that we expect that would fit well within brand guideline-esc component library. This would likely include basic elements like:
Button
Card
Slider
Box
Dialog
Table
Pill
Tabs
Icons
Identicon/Avatar
And perhaps more complex ones like
Block-sync-status
AccountSwitcher
TestnetBanner
2. Minifront
A number of things in the current UI package really only pertain to minifront and we don't expect it to be re-used. We can create either an additional internal UI package or simply just bring them into the minifront app folder. Candidates:
dutch auction component
logo
FadeTransition
GradientHeader
3. Prax
We should asses components in penumbra-zone/ui that are only used in Prax and are ones we don't suspect will ever be re-used by other apps---and migrate it to Prax repo. Candidates:
Network
Others?
Deployment
A part of this task is to ensure UI package can properly be exposed and consumed externally.
In the effort to create a re-useable UI component library,
@penumbra-zone/uipackage was made. However, it's grown a bit bigger than expected. It's time we split some things out.1.
@penumbra-zone/uiKeep components that we expect that would fit well within brand guideline-esc component library. This would likely include basic elements like:
And perhaps more complex ones like
2. Minifront
A number of things in the current UI package really only pertain to minifront and we don't expect it to be re-used. We can create either an additional internal UI package or simply just bring them into the minifront app folder. Candidates:
3. Prax
We should asses components in
penumbra-zone/uithat are only used in Prax and are ones we don't suspect will ever be re-used by other apps---and migrate it to Prax repo. Candidates:Deployment
A part of this task is to ensure UI package can properly be exposed and consumed externally.