Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
13
Comments
7

Lucas Silva

@lucasfs022São Paulo, Brazil260 points

Hey there !! 👋 I'm Lucas Silva, a front-end developer based in Brazil. I'm a creative person who loves using the latest technologies to create unique websites and apps. I'm also enthusiastic about learning new skills and tackling the challenges that come with them.

I’m currently learning...

React, redux and SQL (MySQL).

Latest solutions

  • Testimonial Grid Section


    Lucas Silva•260
    Submitted 5 months ago

    1 comment
  • Four Card Feature Section


    Lucas Silva•260
    Submitted 5 months ago

    1 comment
  • Product Preview Card


    Lucas Silva•260
    Submitted 5 months ago

    1 comment
  • Simple Omelette Recipe Page


    Lucas Silva•260
    Submitted 5 months ago

    I'm not sure if the HTML on this page is as semantic as it should be. If anyone could take a quick look at it and tell me what changes I should make to keep it 100% semantic, I'd be very grateful.


    1 comment
  • Social Links Profile


    Lucas Silva•260
    Submitted 5 months ago

    2 comments
  • Blog Preview Card Solution


    Lucas Silva•260
    Submitted 5 months ago

    1 comment
View more solutions

Latest comments

  • Carla•150
    @Carlitaalt
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    Je suis fière d'avoir utiliser CSS GRID avec plus de facilité, cependant je voudrais savoir mieux gérer les dimensions

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

    J'ai du modifier mes dimensions CSS GRID car elle ne correspondait pas

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

    Que pensez vous de ma solution? Est elle responsive ? Le code est il lisible et clair ?

    TESTIMONIALS GRID SECTION

    1
    Lucas Silva•260
    @lucasfs022
    Posted 5 months ago

    Great job! I have some tips that might help make your design closer to the original one.

    1. Unless it is strictly necessary to define a width (for columns) or height (for rows), it is preferable that you use fr instead of pixel (example below):

    Instead of using

    grid-template-columns: 270px 270px 255px 255px;
    

    Use

    grid-template-columns: repeat(4, 1fr); 
    

    or

    grid-template-columns: 1fr 1fr 1fr 1fr;
    

    Using units like pixels can break the page's responsiveness.

    Here is a more in-depth explanation on how to use grid layout.

    I highly recommend this free css grid course as well. It helped me a lot.

    1. You don't necessarily need to define rows when using grid layout (and if you do so, follow the same advice as the item 1 about the fr). As you define the number of columns, the items will automatically be allocated in each one of them, and if there are more items than columns, new rows will be created to allocate these items.

    Overall, this is really well done project. Congrats.

    Marked as helpful
  • Anh•400
    @anhvu1012
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    I am most proud that I managed to understand and use the CSS Grid :)

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

    I didn't manage to implement the straight inner top left and top right border of the cards like the original design :(

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

    How can I achieve the top left and right border just like the original design? Can someone please enlighten me? Thanks a bunch :)

    Four cards feature section using CSS Grid

    1
    Lucas Silva•260
    @lucasfs022
    Posted 5 months ago

    Great job! I have some tips that might help make your design closer to the original design.

    1. I would not set a min-width for the cards. When we resize the page, it breaks the responsiveness.

    2. Since the cards don't have min-width, I'd set a 2-column grid for tablet screen sizes (between 768px and 1024px) so the card's content won't be squished.

    3. About the top border, if you change the card's border-radius to 5px, it'll be closer to the original design.

    Overall, this is really well done project. Congrats.

    Marked as helpful
  • P
    kindlypi8MCeN7•170
    @kindlypi8MCeN7
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    Nothing.

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

    Fiting the whole image whithin the height, it has some white space left in the bottom, "height: 100%" to the image helped me fit it.

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

    The ratio of the image in the tablet/mobile is not good, the parfum is not centered, tried multiple thing but it didn't work.

    Product preview card (HTML/CSS with flexbox)

    2
    Lucas Silva•260
    @lucasfs022
    Posted 5 months ago

    Great job! I have some tips that might help make your design closer to the one proposed in the challenge.

    1. I noticed you used media query to change the image for mobile. In this case, you can add both images to the <picture> tag itself via <source> and define which screen size the image should be displayed on.
    <picture>
      <source srcset="./images/image-product-desktop.jpg" media="(min-width: 768px)">
    
      <source srcset="./images/image-product-mobile.jpg" media="(max-width: 767px)">
    
      <img src="./images/image-product-desktop.jpg" alt="Gabrielle Essence Parfurm">
    </picture>
    

    Here is a more in-depth explanation of this tag.

    You could also use the <figure> tag as the parent of the <picture>, thus making the code more semantic.

    1. Neither the "green" price nor the crossed out one are using the proposed fonts ("Fraunces" and "Montserrat" respectively)

    2. I'd add some padding at the <body> for table/mobile screen sizes so the product card doesn't touch the device edges.

    Overall, this is really well done project!

    Marked as helpful
  • edixlk•50
    @Edixlk
    Submitted 5 months ago

    Recipe page (Sematic html)

    1
    Lucas Silva•260
    @lucasfs022
    Posted 5 months ago

    This looks really good, nice job! I would just centralize the recipe container.

  • Saima Ahmed Sial•1,220
    @saimasial-bit
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    I really proud on this project...next time I will try my best.

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

    Faced UI, responsiveness, and performance issues. Used Flexbox, lazy loading, and API optimizations to fix them. Improved state management and security for a better experience.

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

    Need help with UI/UX, responsiveness, performance, state management, or API integration? Let me know the specific issue!

    social-links-profile-main

    1
    Lucas Silva•260
    @lucasfs022
    Posted 5 months ago

    This looks good, nice job! I would adjust the image path, as it's not being shown.

  • ChinweGlory•160
    @ChinweGlory
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    I tried to follow the html semantic for accessibility, normally I would have use header for the for the learning with the yellow background but instead I used span which is inline by default, which makes it easy to add padding and background styling.

    I used semantic HTML for better structure and Used relative units

    1
    Lucas Silva•260
    @lucasfs022
    Posted 5 months ago

    I noticed some styles that are different from those proposed in the challenge. First, most of the background is black, in this case, it should be yellow (#f4d04e).

    Because of the background color, we can't see the frontend mentor attribution, since there's a lack of contrast.

    I also noticed that the font-family differs from the one in the challenge ("Figtree").

    I believe that these small adjustments will make the project closer to the proposed challenge.

    Congratulations on the project and I hope I've helped.

View more comments

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

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