-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[dashboard] Re-implement Plans page for new dashboard #3550
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
9c4ee93
to
55364d3
Compare
bb08e33
to
1864cf7
Compare
9db5de9
to
9c5ef33
Compare
Ready for review! Please take a look @svenefftinge @AlexTugarev @gtsiolis 🙏 (Note, the gitpod-com deployment works, this one here won't work.) |
Looking at this now! 👀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's the plan! This looks great @jankeromnes! Left some comments. 🗺️
</div> | ||
</div> | ||
<div className="flex justify-end mt-6"> | ||
<button onClick={doUpgrade}>Upgrade</button> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: What do you think of introducing a secondary button variant for the confirm (green color) action? Using the following attributes could could suffice. Feel free to add this inline here.
text-green-600 bg-green-100 hover:text-green-600 hover:bg-green-300
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, thanks! Do you think this should be added to our current centralized button variants?
gitpod/components/dashboard/src/index.css
Lines 36 to 51 in ec62ded
@layer components { | |
button { | |
@apply cursor-pointer px-4 py-2 my-auto bg-green-600 hover:bg-green-700 text-gray-100 text-sm font-medium rounded-md focus:outline-none focus:ring transition ease-in-out; | |
} | |
button.secondary { | |
@apply bg-gray-100 hover:bg-gray-200 text-gray-500 hover:text-gray-600; | |
} | |
button.danger { | |
@apply bg-red-600 hover:bg-red-700 text-gray-100; | |
} | |
button.danger.secondary { | |
@apply bg-red-50 hover:bg-red-100 text-red-600 hover:text-red-700; | |
} | |
button:disabled { | |
@apply cursor-default opacity-50 pointer-events-none; | |
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally yes, but this will become more clear on the way as we split components down to smaller pieces and the need for component hierarchy, variants, etc becomes obvious for everyone one the team. I'd say both approaches are completely fine here for now! 🔥
/werft run 👍 started the job as gitpod-build-jx-plans.18 |
0f35b07
to
7102e2b
Compare
/werft run 👍 started the job as gitpod-build-jx-plans.23 |
/werft run 👍 started the job as gitpod-build-jx-plans.24 |
1198a94
to
5d7e2ee
Compare
@jankeromnes could you center the cards? |
@jankeromnes, the cards could use more width, no? I count at least 5 ellipsis. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's center the cards as @AlexTugarev mentioned in #3550 (comment) and merge this! 🚢
Fixes #3358
TODO:
plans.ts
from gitpod-com to gitpod-io