Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
9
Comments
7
Leo
@Leonardolvq

All comments

  • P
    Erik S. Carlsten•290
    @ecarlste
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    This was my first time playing around with grids in tailwind and I wasn't very familiar with them in general. I'm really glad I finally dove in and played with them when I created this component.

    Testimonial grid in React, Next.js, tailwindcss, and TypeScript.

    #next#react#tailwind-css#typescript
    1
    Leo•150
    @Leonardolvq
    Posted 3 months ago

    Nice work on the project! The modularity of the code, especially with the separate card component, is a great touch. I see you used TypeScript and Tailwind CSS, which is impressive – though I’m not super familiar with them, I can tell they add a lot of structure.

    Some small details weren’t fully followed, but it’s clear you know how to implement changes. By the way, I noticed there are documents from other projects in the repo.

  • Denis Omar Cuyo Ttito•350
    @OTF31
    Submitted almost 3 years ago

    Responsive design using NativeBase

    #react
    1
    Leo•150
    @Leonardolvq
    Posted 3 months ago

    The code is clean and modular, especially with CustomCard, which keeps things reusable. Just a few typos to fix. Looks like NativeBaseProvider is handling the styling and theme, but I’m not too familiar with it yet.

  • Bloxer58•110
    @Bloxer58
    Submitted 4 months ago
    What are you most proud of, and what would you do differently next time?

    Responsive layouts.

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

    Creating different layouts for mobiles and desktop. At first I had problems with positionig different divs. But after learning responsive layouts: display: flex etc. I overcame this problem.

    Product preview card component (HTML & CSS)

    1
    Leo•150
    @Leonardolvq
    Posted 4 months ago

    Hey,

    Thanks for introducing me to the <picture> element! I didn’t know about it, and it’s a great way to handle responsive images.

    The rest of the code looks solid! Just a heads up about the nested CSS—if it's not SCSS, it won’t work in regular CSS. You might want to either remove the nesting or set up Sass.

    Everything else is great though, nice job! 👍

  • Anton•140
    @antonbest444
    Submitted 12 months ago

    CSS Variable, Box-model, Semantics

    1
    Leo•150
    @Leonardolvq
    Posted 12 months ago

    Good clarity! Well done!

  • teixeirabrenno•70
    @teixeirabrenno
    Submitted 12 months ago
    What are you most proud of, and what would you do differently next time?

    Managed to finish the project in less time than usual.

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

    I couldn't find a way to make the pointer cursor black.

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

    I read about how to make the pointer cursor black and found out that there's no way to change the color of the cursor through CSS directly. Instead, I would need to get an URL to a black pointer cursor and then implement it on the CSS. I couldn't find a website to do this though, so any recommendations would be great.

    Social profile page using HTML and CSS

    1
    Leo•150
    @Leonardolvq
    Posted 12 months ago

    To customize your cursor, you need to get an image. You can find cursor images on various websites like Flaticon, The Noun Project, and many others. Numerous websites reference these sources.

    Ex: cursor: url('./images/custom-cursor.png'), auto;

    Marked as helpful
  • Ane Marinheiro Weber•20
    @AneWeber
    Submitted 12 months ago
    What are you most proud of, and what would you do differently next time?

    I updated my name, avatar and date according to my informations. It was a great project to start.

    Blog Preview Card Challenge using HTML and CSS

    1
    Leo•150
    @Leonardolvq
    Posted 12 months ago

    Using relative units like 'em', 'rem', or '%' instead of 'px' is a great way to make your project more responsive. These units adjust based on the user's settings and screen size, ensuring your design scales appropriately across devices. Keep up the good work! 👌👌

    Marked as helpful
  • Wasiu Olaoti Sulaimon•20
    @sulaimonwasiu
    Submitted 12 months ago
    What are you most proud of, and what would you do differently next time?

    I need to learn more about FIGMA.

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

    How to find my way around FIGMA file given.

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

    I am okay for now.

    This is a simple frontend QR-CODE cahllenge.

    1
    Leo•150
    @Leonardolvq
    Posted 12 months ago

    Focus on using HTML5 semantic tags like <main> to properly structure your page content. This enhances the readability and accessibility of your HTML.

    For responsiveness, use relative units (em, %) in your CSS instead of fixed units (px). This ensures that your website adjusts well to different screen sizes and devices, providing a better user experience.

    Implementing these practices will make your code more semantically meaningful and responsive, improving both usability and accessibility of your website.

Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub