Closed sandrahoang686 closed 1 month ago
@sandrahoang686 's comment in #799 ticket https://github.com/NASA-IMPACT/veda-ui/issues/799#issuecomment-1898872649 made me think that testing on a test instance for actively changing components from veda-ui package might be annoying.
VEDA-UI currently has a sandbox page (not getting published on production), which is an isolated environment for the development of the components: https://visex.netlify.app/sandbox.
For active development on a component, to see changes right away without having to spin up the test instance, we can import those components into the sandbox page within veda-ui which is only used for development purposes. One cons is we can't test if something goes wrong during the library's build process (#800 ) in the sandbox page - at least for now.
I would be great to create a parallel Figma library so any changes in the codebase are reflected on the design components 👍
@hanbyul-here @sandrahoang686 @dzole0311
Is this ticket still needed? Seems old and seems to be overarching a lot of work. Should we close in favor of other tickets, or maybe narrow the scope a bit?
This ticket is kindof also captured here https://github.com/NASA-IMPACT/veda-ui/issues/997, i'll scope down
We have decided to continue developing on top of the prototype. Closing this because of that.
Description: This ticket is to create the Template Instance repository and scaffolding. This ticket is the after experiment of the prototype work. This is just to create the skeleton.
Acceptance Criteria:
NASA-IMPACT
?)veda-ui
v2 so we can consume components