Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
8
Comments
6

Guilherme Costa

@cdGuilhermeBrazil100 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

  • QR code component (resubmit)

    #accessibility#bem

    Guilherme Costa•100
    Submitted 6 months ago

    Looking for feedback about what I might have missed or could've done better.


    0 comments
  • Testimonials Grid Section Solution

    #sass/scss#bem

    Guilherme Costa•100
    Submitted about 1 year ago

    Any tips about CSS Grid or general code quality are welcome!


    1 comment
  • Four card feature section solution

    #sass/scss

    Guilherme Costa•100
    Submitted about 1 year ago

    Any tips regarding SASS or CSS Grid will be highly appreciated. I would also appreciate feedback about my code quality, if you find anything that could be improved please let me know!


    0 comments
  • Product Preview Card Challenge


    Guilherme Costa•100
    Submitted about 1 year ago

    Nothing specific. However I'm open to feedbacks about code quality or anything I can improve. If you find anything please let me know! 🙏


    1 comment
  • Omelette Recipe Page Challenge


    Guilherme Costa•100
    Submitted about 1 year ago

    I would like to know if my code follow best practices. This could be anything from code quality to accessibility. I'm open to feedbacks!


    2 comments
  • Social Links Profile Challenge


    Guilherme Costa•100
    Submitted about 1 year ago

    I am looking to get feedback about the quality of the code that I've written, I tried my best to code while following best practices but maybe I missed something. I'm open to feedbacks for accessibility tips and code quality. Any advice will do! Thank you :)


    1 comment
View more solutions

Latest comments

  • karthickg24•130
    @karthickg24
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    NA

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

    NA

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

    NA

    Mobile First Testmonials Grid Section Using BEM with SCSS

    #sass/scss#bem
    1
    Guilherme Costa•100
    @cdGuilherme
    Posted about 1 year ago

    Great job on your solution! It looks just like the desired design and you did a good job with semantic html too. Just a small pointer:

    • Consider using h2-h6 elements to all titles inside the testimonial card. This helps identify headings to all articles. For more info see: The HTML Section Heading elements - Accessibility concerns

    Hope this helps. Good luck!

  • Bartosz Dudziak•720
    @bartoszdudziak-dev
    Submitted over 1 year ago
    What are you most proud of, and what would you do differently next time?

    I'm proud of my solution with grid-template-areas. Code looks clean and maintainable for me. I feel control over the grid layout in this way.

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

    The biggest challenge was creating responsive grid layout.

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

    I'm still not much confident using semantic HTML. I need to catch up.

    Four Card Feature (SCSS)

    #sass/scss
    1
    Guilherme Costa•100
    @cdGuilherme
    Posted about 1 year ago

    Solution looks really close to the design, well done!

  • Eric•70
    @esurreal
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    I'm proud of the fact that I'm learning this stuff.

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

    Media queries took a little time to understand. Making the page responsive was the biggest learning curve.

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

    I think I need help with image sizing and keeping everything within the container, but It'll probably come with practice.

    Responsive Product Page Using CSS, HTML, and Media Queries

    1
    Guilherme Costa•100
    @cdGuilherme
    Posted about 1 year ago

    Hi Eric, great job on submitting your solution!

    Here are my suggestions:

    Does the solution include semantic HTML?

    • Good job using the <main> element. This is good for accessibility as it helps screen readers identify a page's "main" section.

    Is it accessible, and what improvements could be made?

    • <grid> and <p3> are not valid HTML elements, instead use a div with a class for the price container and use h2 and h3 elements for the prices.
    • Font sizes must never be inpx as it prevents the font size from scaling with the user's default setting.

    Does the layout look good on a range of screen sizes?

    • The layout breaks on some screen sizes. I suggest removing fixed widths and heights, this is something you should rarely do because components should be able to adapt for different screen sizes.
    • Other than that you did a good job with flexbox for the container, it adapts well when changing from column to row on different screen sizes.

    Is the code well-structured, readable, and reusable?

    • For better reusability, you can store colors inside CSS variables using the :root pseudo-class.

    Does the solution differ considerably from the design?

    • Desktop viewing is too wide, I would suggest decreasing the container width using the max-width property.

    • As for the image sizing I suggest setting a max-width and max-height to 100% for the img element.

    • You can switch images from desktop to mobile using the <picture> element with media queries.

    Hope this can be useful! Good luck! 🙏

  • zlatan-cic•90
    @zlatan-cic
    Submitted about 1 year ago
    What are you most proud of, and what would you do differently next time?

    I'm most proud of successfully implementing a responsive design that looks great on both mobile and desktop devices 📱💻. However, next time, I would spend more time planning the layout to avoid any last-minute adjustments and ensure a smoother development process 🚀.

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

    One of the main challenges was handling the image display for mobile devices. Initially, I had to place the first image in the body and then use CSS to set it to display: none for desktop and display: block for mobile 📱. I overcame this by leveraging media queries to conditionally show and hide images, ensuring a seamless and responsive design experience 🎨.

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

    I would appreciate help with optimizing the layout for different screen sizes to ensure a more consistent look across devices. Additionally, advice on improving the overall code structure and efficiency would be highly valuable. Any tips on enhancing the user experience and accessibility would also be greatly appreciated. 😊

    HTML and CSS

    1
    Guilherme Costa•100
    @cdGuilherme
    Posted about 1 year ago

    Hi, great job! Regarding accessibility, you can use <section> tags instead of divs to separate different sections of the page and <footer> for the attribution. The use of semantic HTML elements helps to clearly describe its meaning to both the browser and the developer. Hope this helps! 😊

  • Carlos Espinoza•80
    @GalaxyPliego
    Submitted about 1 year ago

    Social Links Profile: Responsive and Mobile-First Design HTML & CSS

    1
    Guilherme Costa•100
    @cdGuilherme
    Posted about 1 year ago

    Hey! Nice work on your solution. I like how you make the use of different CSS files to make the code more organized, and I also like the use of semantic HTML.

    Here are my suggestions:

    HTML:

    • You can use the <footer> tag instead of a div with a class of footer. Using semantic elements clearly defines the purpose of the element to the browser.
    • Don't put your site's header/menu/footer (repeated content) in your <main>. From Should the header and footer tags be inside the main tag on stackoverflow

    CSS:

    • Import fonts locally using:
    @font-face {
        font-family: "Inter";
        src: url(../../assets/fonts/Inter-VariableFont_slnt\,wght.ttf);
    }
    
    • The website breaks when trying to zoom too much and you can't see all of the content. This can be fixed by centering the card container using:
    body {
        display: flex;
        flex-direction: column;
        justify-content: center;
        align-items: center;
        min-height: 100svh;
    }
    

    And removing the following line from .main__container: height: 100vh;

    But other than that, congratulations on completing this project! Hope this helps 🙏

    Marked as helpful
  • Qudusy•10
    @Qudusy
    Submitted about 1 year ago

    Responsive qr code card using html CSS

    1
    Guilherme Costa•100
    @cdGuilherme
    Posted about 1 year ago

    Hello there!

    Congrats on completing the challenge!

    I've noticed the layout works well on mobile, however the card gets too big on desktop (landscape orientation) because the image grows so much. For this challenge I'd like to suggest using an absolute length width for the QR code container.

    I hope it helps!

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

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