Skip to content
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

[Frontend] Migrate Vault Stake and Withdraw pages to Tailwind #535

Closed
djeck1432 opened this issue Jan 29, 2025 · 5 comments · Fixed by #544
Closed

[Frontend] Migrate Vault Stake and Withdraw pages to Tailwind #535

djeck1432 opened this issue Jan 29, 2025 · 5 comments · Fixed by #544
Assignees
Labels

Comments

@djeck1432
Copy link
Owner

🚨 Attention: Please read the guidelines before applying; otherwise, you will be ignored. 🚫📋

Guidelines

  1. Telegram: Please join our Telegram group to keep in touch.
  2. Read the guideline: Please read this guideline thoroughly before starting.

Tasks

  1. Set Up Tailwind for the Target Components

    • Migrate (Withdraw) /withdraw and Stake(/stake) ( pages to Tailwind.
    • Ensure all existing styling in this parts is translated or replaced with Tailwind utility classes.
  2. Maintain Current Layout & Responsiveness

    • Ensure responsive and visually consistent after migrating to Tailwind.
    • Make sure both desktop and mobile version looks just like in Figma and in previous version of application.
  3. Preserve Components

    • Do not modify or migrate Button and Sidebar components, because it will be done as a part of another task.
    • Continue using Button and Sidebar components as it is without altering its internal styles.
  4. Clean Up

    • Remove any redundant CSS related to these components, if it becomes unnecessary post-Tailwind migration.
    • Avoid touching other components, pages or global styles that are not part of this ticket.
@Yunusabdul38
Copy link
Contributor

Yunusabdul38 commented Jan 29, 2025

Could I grab this task?
I like pineapple
TG: yunusabdul38
ETA 5h

@Pvsaint
Copy link
Contributor

Pvsaint commented Jan 29, 2025

Can I try solving this issue?

@gabito1451
Copy link
Contributor

i will migrate withdraw and stake pages to tailwind while maintaining layout and responsiveness. i will keep the Button and Sidebar components unchanged, and remove redundant CSS without affecting other styles.

i like pineapple

telegram:@gabbie 306

ETA:12HRS

@kayceeDev
Copy link
Contributor

kayceeDev commented Jan 29, 2025

my name is Leonard, I am a frontend developer and I like pineapple.
I will efficiently migrate the existing styles of the stake and withdraw pages to tailwind styles.
With also the use of tailwind I will make sure these pages remain responsive across all devices.

My TG handle is @iam_bodo

ETA: 8hrs

@chiscookeke11
Copy link
Contributor

chiscookeke11 commented Jan 29, 2025

Hi, I am Chinedu a frontend developer and i like pineapple. I would love to work on this task to contribute on your project.

How to resolve the issue; since the jsx structure has been set up, migrating it to tailwind to css wont be a hassle, I will carefully go through the css and assigned the tailwind classes to the elements. Then i can also create cutom styles in the tailwind.config.js file, ETA: 12hrs

telegram handle: Okeke Chinedu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
6 participants