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

Prakhar Nagpal

@slightlybelowzen60 points

Machine Learning, Software-Development, Web-Development, and Graphic Design enthusiast. Imperial College 20204 (MEng, AI + ML)

Latest solutions

  • Recipe card solution


    Prakhar Nagpal•60
    Submitted 9 months ago

    Mostly the best way to make it responsive without adding too many media queries.


    0 comments
  • Social media profile links using flexbox


    Prakhar Nagpal•60
    Submitted 9 months ago

    Any feedback is always appreciated, especially towards making the design responsive.


    1 comment
  • Blog preview card using flexbox


    Prakhar Nagpal•60
    Submitted 9 months ago

    Open to feedback if anyone feels something could have been done better.


    1 comment
  • Simple QR Code component using flexbox


    Prakhar Nagpal•60
    Submitted 9 months ago

    1 comment

Latest comments

  • Oladeji Omolabake•70
    @lab1210
    Submitted 9 months ago

    Recipe Card

    1
    Prakhar Nagpal•60
    @slightlybelowzen
    Posted 9 months ago
    • The font sizes are too small, they need to be updated 0.6rem is about 9.2px, which is much smaller than the required font size. It is 14px for the base text.
    • Use semantic HTML, going from <h1> to <h5> is not a great idea, making the section headings h2 would make much more sense semantically.
  • P
    Shayne Wuver•60
    @WindowsM16a
    Submitted 9 months ago

    Social links profile

    1
    Prakhar Nagpal•60
    @slightlybelowzen
    Posted 9 months ago
    • The font weight of the heading seems to be off, although I could just be missing something with that one.
    • The font weight of the links is also off by 100, the design system specifies 700 (use inter bold)
  • MacRay-lab•40
    @MacRay-lab
    Submitted 9 months ago
    What are you most proud of, and what would you do differently next time?

    I am proud of the improvement in my css for now but I look foward in learning more.

    blog-preview-card-main

    1
    Prakhar Nagpal•60
    @slightlybelowzen
    Posted 9 months ago
    • Usually good to separate your constants in the style sheet as variables in the css, so you don't have to wonder what the value represents and go back to it again and again.
    • Some of the values in the css are not taken from the design file, which is why the solution screenshot looks different, you can see the value of the spacing, line height, max-width etc. from the design spec. (Not sure if this project provides access to the figma design file without premium)
  • Abbas•30
    @abbas-devlop
    Submitted 9 months ago
    What are you most proud of, and what would you do differently next time?

    i would use flexbox to center the div instead of the old way where we use position absolute

    CSS old fashion

    1
    Prakhar Nagpal•60
    @slightlybelowzen
    Posted 9 months ago
    • The <h2> element hasn't been sized correctly. The design spec uses 22px to style it, and since no size has been specified in the css, it defaults to the browser default of 1.5em which is 24px assuming a base font size of 16px (also since the base font size hasn't been set in the css for the body element.
    • It's a good idea to apply a reset of
    * {
      margin: 0;
      padding: 0;
      box-sizing: border-box;
    }
    

    so you don't have default margins of elements messing with spacing and padding of elements.

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

Beta Member

This badge is a shoutout to the early members of our community. They've been around since the early days, putting up with (and reporting!) bugs and adjusting to big UX overhauls!

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