Content
View differences
Updated by Henriette Darge 1 day ago
**Context**
* Sometimes designs don't match the implentation of components
* PVC is considered to be a set of components used to build the predefined design
* Devs outside of the D-Team don't know what it is implemented and can often times not immedately challenge designs
* The Designs are supposed to be the requested outcome and devs get frustrated because the components cannot deliver what is requested
* Julia is supposed to work on the Figma libraries but will need some time for that as it is not only about our components but also those coming from Primer itself
**Possible solutions**
1. Every figma design needs to run through D-Team to do a feasability check
1. Con:
* D-Team will clearly be the bottleneck
2. Every dev is allowed to challenge designs
1. Pro/Con:
* ...
3. We install a weekly call with D-Team & Designers to go through current implementation changes/design requirements
1. Pro/Con
* ....
* Sometimes designs don't match the implentation of components
* PVC is considered to be a set of components used to build the predefined design
* Devs outside of the D-Team don't know what it is implemented and can often times not immedately challenge designs
* The Designs are supposed to be the requested outcome and devs get frustrated because the components cannot deliver what is requested
* Julia is supposed to work on the Figma libraries but will need some time for that as it is not only about our components but also those coming from Primer itself
**Possible solutions**
1. Every figma design needs to run through D-Team to do a feasability check
1. Con:
* D-Team will clearly be the bottleneck
2. Every dev is allowed to challenge designs
1. Pro/Con:
* ...
3. We install a weekly call with D-Team & Designers to go through current implementation changes/design requirements
1. Pro/Con
* ....