Skip to content
OverviewSolutions
48
Comments
26

calvinvin

@calvinvin1,060 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

  • Prem Kumar•370
    @prem-kumart
    What are you most proud of, and what would you do differently next time?

    Data fetching.

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

    Custom CSS select dropdown menu. Created an unordered list with dropdown functionality and aria-attributes

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

    Better Coding Practices and project structuring

    Responsive Countries Landing Page

    #react#react-router#tailwind-css
    1
    calvinvin•1,060
    @calvinvin

    Very goooooood!

  • calvinvin•1,060
    @calvinvin

    Very good!

  • Azzy dvyastia kesuma•1,425
    @azzykesuma
    What specific areas of your project would you like help with?

    i'm using vite as react-wrapper/compiler for most of my project, and when i'm previewing all of my static assets (prod) , all of them usually broken unless i put it in root public, why is this always be the case?

    Product list challenge

    #shadcn#tailwind-css#typescript#vite#motion
    1
    calvinvin•1,060
    @calvinvin

    Because the <img> element’s src attribute comes from variable image.mobile, which is "/image-waffle-mobile.webp", and Vite looks into the root/public directory for /.

    You can reference this page for more information: Static Asset Handling.

  • aurel0123•60
    @aurel0123
    What are you most proud of, and what would you do differently next time?

    I am to have realized even if I encountered difficulties at the level of Js. It was very funny

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

    I had problems managing cards dynamically with js, but I managed to do it

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

    I would like some help with the backend with node.js

    responsive product list with cart

    1
    calvinvin•1,060
    @calvinvin

    Good work!

  • calvinvin•1,060
    @calvinvin

    Good work!

  • Cesare•560
    @Cesare94
    What are you most proud of, and what would you do differently next time?

    The project is very long and I am proud to have covered all the expected areas.

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

    The responsive part was the most difficult.

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

    I don't have any particular areas to ask.

    Space-tourism-website

    1
    calvinvin•1,060
    @calvinvin

    Good work and functions well!

    Some things that would look better for me:

    1. background-repeat: no-repeat; background-size: cover;
    2. font-family not imported
    3. wrap <nav> in <header> for accessibility
    4. the % unit of the margin and padding of the <img>, <hr>, <ul> elements was calculated from the window viewport width, is that really what you want? It seems too large for most scenarios and makes the elements become positioned at bottom right (due to large value of margin-top and margin-left).
    5. there are <h1> and <h3>, but no <h2> on home page.
    6. the default style of <button> looks awful on my macOS safari, moreover if added designed styles on top of it. If you want to make the style looks universal across browsers, may reset the default style with border: none; background: inherit; on button elements at the beginning.
    7. you used the grid-area to design the layout of the crew page, but added bottom property to .btn, which makes the .btn element positioned inside the grid area of the .text, seems weird for me.
View more comments