ADashboard feature requests ux
Tonight having multiple deployments on vercel linking back to multiple projects on convex was a bit much to sort out.
1. Generated name of convex deployment selected up on top so you don't have to go into settings to figure it out.
2. When a preview deployment is deleted, it should not leave you at a 404 with no way to get back to the dashboard.
3. When you go to enter environment keys a preview deployment should warn you that you should set it in the production env as anything you set here will get overwritten on the next push to vercel.
4. Production env settings should also link back to the project env settings.
5. Project wide settings vs specific, i didn't realize that i was getting confused and consciously noticed the difference till today (or this is newer ux), i just click around till i find what i need. Settings for each dev/production/preview should use the color scheme to increase intuitiveness.
6. Project wide settings should give you a list of the convex generated names of the deployments.
7. It should be noted that each production?/preview deployment should get its own key and should never be used twice on vercel?
8. Searching for a deployment within my projects for fast-falcon-504 etc would speed up debugging greatly.
1. Generated name of convex deployment selected up on top so you don't have to go into settings to figure it out.
2. When a preview deployment is deleted, it should not leave you at a 404 with no way to get back to the dashboard.
3. When you go to enter environment keys a preview deployment should warn you that you should set it in the production env as anything you set here will get overwritten on the next push to vercel.
4. Production env settings should also link back to the project env settings.
5. Project wide settings vs specific, i didn't realize that i was getting confused and consciously noticed the difference till today (or this is newer ux), i just click around till i find what i need. Settings for each dev/production/preview should use the color scheme to increase intuitiveness.
6. Project wide settings should give you a list of the convex generated names of the deployments.
7. It should be noted that each production?/preview deployment should get its own key and should never be used twice on vercel?
8. Searching for a deployment within my projects for fast-falcon-504 etc would speed up debugging greatly.
