Content
View differences
Updated by Judith Roth almost 2 years ago
In the frontend-daily we noticed that we have an repeated pattern that we use and for which there is no "native" primer component. This is a Dialog with a success message. Currently we're using Dialogs with Blankslates, which is a "misuse" of Blankslates. If Primer Blankslates are changed in the future and no longer fit our use-case, we want to be able to easily adapt. Therefore we decided to build a custom component for this.
### Acceptance Critieria:
* There is a custom component for that
* which internally still uses the blankslate
* The custom component is documented in the Lookbook
* Existing usages are "migrated" to the new custom component:
* Storages setup success
* API Token token generation
* Confirm removal of project from storage in "Enable in Storages" (? - it's maybe too different from the others and currently not implemented with a Blankslate)
Keep using blankslate internally
* ???
Document in lookbook
* The Document pattern ins documented in the UI / UX documentation (done by Marc) Marc
### Acceptance Critieria:
* There is a custom component for that
* which internally still uses the blankslate
* The custom component is documented in the Lookbook
* Existing usages are "migrated" to the new custom component:
* Storages setup success