Open colleenskemp opened 3 years ago
Note that this should use the /resource/{entity}
post endpoint that @sutjin is working on as part of #54.
The UI should be similar to #5 but with the fields appropriate for the entity type. Probably there should be two components: one for VMA uploads and the other for resource entities. Resource entity uploads would include Adoption, TAM, and any other resource beside VMA. (VMAs are different because they are individually associated with a variable ID).
See the UX sketch in #5 for general UX concept as well.
No Adoption Sources could be selected as reference or scenario, though we can confirm this with Chad.
Time estimate: @sutjin - please estiamte
Need: As a user, I can upload a new adoption scenario source
Description:
There is not a design for this. Please infer the design using the style guide, the icon below, and this design reference: https://www.figma.com/file/QImAyi1guE4AICGMN7uODK/Drawdown-Portfolio-UI-Figma-Chakra-UI?node-id=1369%3A0
Acceptance criteria: As a user, I can upload my own adoption scenario source.
Open question: This is specific to scenario source and not on reference source? If so - is there another way/ space where new reference sources can be added? @eethann