Skip to content
OverviewSolutions
28
Comments
16
P

JeronimoCardu

@JeronimoCardu580 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

View more solutions

Latest comments

  • Grecco Oliva, Franco•290
    @GreccoOliva-Franco
    What are you most proud of, and what would you do differently next time?

    • Speed of resolution. I'm getting used to tailwind classes and architecting the UI in my head before even trying to code

    • I would like to try implementing some animations to the acordion items

    What challenges did you encounter, and how did you overcome them?

    Non this time. Progress in skill is clear

    NextJs - Tailwind CSS

    #next#tailwind-css
    1
    P
    JeronimoCardu•580
    @JeronimoCardu

    Good!

  • P
    Anamay•470
    @anamaydev
    What are you most proud of, and what would you do differently next time?

    I'm proud that I decided to go beyond the original design by adding buttons to open and close the rating component, turning it into a more interactive experience. I challenged myself to build a simple modal, and I’m happy I was able to implement it successfully. However, looking back, I realise that I used <button> elements to capture the user's selected rating, which isn't the most semantic choice. Next time, I would use <input type="radio"> elements instead, as they are more appropriate for this kind of selection and improve accessibility.

    What challenges did you encounter, and how did you overcome them?

    One of the biggest challenges I faced was learning Tailwind CSS for the first time, just as version 4 was released. Most tutorials I found were based on version 3, and even ChatGPT often gave outdated suggestions. I got through it by using the official docs and finding updated YouTube tutorials

    What specific areas of your project would you like help with?

    I’d appreciate feedback on how I can improve my code, especially in terms of best practices and structure. I'm also looking for guidance on accessibility, as I haven’t focused on it yet but plan to make it a priority in future projects.

    Interactive rating component in React and Tailwind CSS v4

    #react#tailwind-css
    1
    P
    JeronimoCardu•580
    @JeronimoCardu

    Nice way to navigate, great job!

  • P
    GeraASM•500
    @GeraASM
    What are you most proud of, and what would you do differently next time?

    The next time in the part of backgrounds do first and then implements the design

    What challenges did you encounter, and how did you overcome them?

    I had problems in the part range when the questions increment also the background should do but I couldn't do it

    What specific areas of your project would you like help with?

    In the part background the images in the body and the parte linear-gradient change the color when the increment the questions

    New events implements

    1
    P
    JeronimoCardu•580
    @JeronimoCardu

    It's great! The functions are fine, but there's a problem when changing the question — the question and the options on the screen don't update.

  • P
    JeronimoCardu•580
    @JeronimoCardu

    Great!

  • P
    JeronimoCardu•580
    @JeronimoCardu

    Cool!

  • Arash Asghari•220
    @AriArash44
    What are you most proud of, and what would you do differently next time?

    I'm proud of implementing SWR for efficient data fetching, ensuring the dashboard updates dynamically without excessive network requests. The use of Tailwind CSS made styling intuitive and maintainable.

    Next time, I would explore alternative state management solutions(specially Zustand) to improve performance.

    What challenges did you encounter, and how did you overcome them?

    One of the biggest challenges was configuring Webpack properly to bundle scripts for deployment on Vercel. Since Webpack setup can be complex, ensuring everything integrates smoothly required troubleshooting and fine-tuning.

    Another challenge was dealing with Tailwind's purging mechanism. To ensure dynamic classes aren't removed, I created a hidden-classes.html file to reference all the necessary dynamic Tailwind classes. However, I'm unsure if there's a better way to handle this, as it feels like a workaround rather than an optimal solution.

    What specific areas of your project would you like help with?

    Any suggestion about any aspects of the project would be appreciated.

    TTDashboard, Live Data with SWR and Styled with Tailwind

    #react#swr#tailwind-css#node
    1
    P
    JeronimoCardu•580
    @JeronimoCardu

    Good!!!

View more comments