Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
12
Comments
10

glowri57

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

  • Responsive Three-Column preview section using Flexbox


    glowri57•190
    Submitted about 2 months ago

    How to reduce the size. It's look bigger when hosted.


    0 comments
  • Resposive Testimonial Grid Section using CSS Grid


    glowri57•190
    Submitted about 2 months ago

    I would like for someone to check the code and tell me how best to reduce the grid section without the text overflowing and how best to use grid for the styling of this section.


    1 comment
  • Responsive Four feature Section using CSS Grid


    glowri57•190
    Submitted about 2 months ago

    I would need help in the better to write my code. Especially the grid part.


    0 comments
  • Order Summary Component


    glowri57•190
    Submitted 10 months ago

    I would need feedback on how to improve my code. Thanks!


    1 comment
  • NFT-Preview-Card-Component


    glowri57•190
    Submitted 10 months ago

    I would need feedback on how I can improve the code. Thanks.


    1 comment
  • Responsive Result Summary Component using CSS Grid


    glowri57•190
    Submitted 10 months ago

    Any feedback would be welcome. Thanks


    1 comment
View more solutions

Latest comments

  • P
    LaStellaa•570
    @LaStellaa
    Submitted 5 months ago

    Responsive mobile first testimonials grid layout

    1
    glowri57•190
    @glowri57
    Posted about 2 months ago

    Hi LaStellaa, your code is very nice and I loved how you used grid-template-areas for the grid. There is one major thing I noticed in your html file, you had h3 first before h2. Order is very important for semantic and SEO purposes. Ensure that there is always an h1 in your document. You can make the display of h1 display:none so it would not be visible. Check the article below to understand more. Why heading order matters in HTML

    Marked as helpful
  • Sanjay Kumar SR•260
    @srsanjaykumar
    Submitted 3 months ago

    Four Card Feature Section

    1
    glowri57•190
    @glowri57
    Posted about 2 months ago

    This is a very good program. Keep it up 👍

  • Thomas-Ngo-1•90
    @Thomas-Ngo-1
    Submitted 11 months ago

    QR Code Solutions

    3
    glowri57•190
    @glowri57
    Posted 11 months ago

    Hi @Thomas-Ngo-1

    Here's what I noticed:

    • font-weight have values 100, 200, 300...900, you don't need to add px
    • add some space at the bottom of your paragraph
    • the paragraph should have color Slate 500
    • Since you styled the class .slate-300 and the rest, the property should be defined in your HTML file. Here's an example:
    <span class="slate-500">...</span>
    

    Then the color assigned to slate-500 would be styled on the span tag.

    • The background-color: in those color classes should be changed to color: You're trying to define the color of the text, not the background-color of the text.

    I hope you find this helpful!

  • CptnRedbeard•40
    @CptnRedbeard
    Submitted 11 months ago
    What are you most proud of, and what would you do differently next time?

    I was able to make an example similar to the original but it didn't adjust correctly when the window was resized. I'd try to find a solution without watching a video next time.

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

    In my original file, when you resized the window everything would get squished because I was using percentages. I was able to follow along with a video explaining pixels, rem, and padding that helped out a lot.

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

    How do you decide when to use pixels, rem, or percentages?

    QR-Code-Component

    3
    glowri57•190
    @glowri57
    Posted 11 months ago

    Hi @CptnRedbeard

    To answer your question, you should use px when dealing with properties that you want to remain fixed in value no matter the viewport. you can use px with properties like: border, border-radius, etc.

    rem and percentages are relative values.

    rem is used with properties like font-size, margin, padding, @mediaquery min-width and max-width values.

    percentages are mostly used in width, height, min-width, max-width, min-height and max-height properties. They are relative to the width or height of the webpage. Check this article to understand more. Why font size must NEVER be in pixels

    I hope you found this helpful!

  • Feuzi•110
    @Feuzi
    Submitted 11 months ago

    Recipe Page

    3
    glowri57•190
    @glowri57
    Posted 11 months ago

    Your GitHub repo is not visible. You probably set it to private. It would help if you changed it to public so that others could view your code and give feedback.

  • jevcenkokozlovska•150
    @jevcenkokozlovska
    Submitted 11 months ago

    pProduct preview card component with css grid

    2
    glowri57•190
    @glowri57
    Posted 11 months ago

    This is a wonderful piece of work. You could use the <s> for the old price.

    Marked as helpful
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