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

Adrian H

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

  • Interactive rating component using Flexbox


    Adrian H•420
    Submitted almost 3 years ago

    2 comments
  • Pod request landing page using CSS Flexbox


    Adrian H•420
    Submitted almost 3 years ago

    0 comments
  • FAQ accordion card with no JS


    Adrian H•420
    Submitted almost 3 years ago

    0 comments
  • Huddle landing page curved using Flexbox and media queries


    Adrian H•420
    Submitted almost 3 years ago

    0 comments
  • Coming soon page using Flex/SASS/Media queries and JS

    #sass/scss

    Adrian H•420
    Submitted about 3 years ago

    0 comments
  • QR code component


    Adrian H•420
    Submitted about 3 years ago

    0 comments
View more solutions

Latest comments

  • Nguyen Nguyen•340
    @jesuisbienbien
    Submitted about 3 years ago

    Ping coming soon page - using grid, mobile-first work flow, vanilla JS

    1
    Adrian H•420
    @AdrianX19
    Posted about 3 years ago

    Hi @jesuisbienbien!

    congrats on completing this challenge! really good job! :) The issue you have is caused because <small> elements is an inline and for such elements the top and bottom margin/padding has just not effect, you can do a couple of things to make it working for example you can replace <small> with some block element like <p>, you can change your current element to a block element by adding 'display: block' or you can add margin to your container 'email-error-container' :)

    Marked as helpful
  • James•10
    @jamespaulmiranda
    Submitted over 3 years ago

    Qr code viewer using HTML and CSS

    1
    Adrian H•420
    @AdrianX19
    Posted about 3 years ago

    Hi @jamespaulmiranda!

    Welcome on frontendmentor and congrats for submitting your first challenge! :) a few suggestions:

    • to get rid off the accessibility/html issues there are two things you should do, first use semantic tags, so instead of having 'div' for your container use 'main', and instead of having 'div' for your footer, well.. you can use 'footer' tag! :). Second thing is the h3 you used, heading levels shouldn't be used for the styling purpose, it's just not a good practice and we have CSS for that purpose! so changing h3 to h1 and changing the fontsize through CSS would do the trick
    • you might consider giving some min-width to your card so it doesn't get squeezed so much with smaller viewport width
    • you seem to be lacking the mobile version, you can achieve it on many ways but using media queries it's a good call most of the times! (https://www.w3schools.com/css/css_rwd_mediaqueries.asp) :)

    Have a good day! :)

    Marked as helpful
  • Mister Ślimak•10
    @MisterSlimak
    Submitted over 3 years ago

    RWD, CSS, HTML

    1
    Adrian H•420
    @AdrianX19
    Posted about 3 years ago

    Hi @MisterSlimak!

    really good job! If you'd like to get rid off those accessibility issues just replace your container 'div' with 'main' tag :)

  • Eric Chua Zheng Hua•60
    @bigmac369
    Submitted over 3 years ago

    CSS Grid, ReactJS

    #react#styled-components
    1
    Adrian H•420
    @AdrianX19
    Posted over 3 years ago

    Hi @bigmac369!

    Congrats on submitting the challenge! A few minor things I've noticed:

    • the accessibility issues you have can be solved by changing the #root 'div' to a 'main' tag
    • background colour of the join community section is a bit off comparing to the design, it should be white
    • monthly subscription text should be aligned to left, to achieve that you should probably set 'align-items' property to 'flex-start' for this section
    • the 'monthly subscription' and 'why us' cards should be aligned, I believe you could achieve that by changing justify-content for those cards to 'space-between' and them add the same top and bottom padding for both of them

    Keep it up! :)

    Marked as helpful
  • Renan Tiscoski•1,240
    @DonUggioni
    Submitted over 3 years ago

    Simple price component using CSS Grid

    1
    Adrian H•420
    @AdrianX19
    Posted over 3 years ago

    Hey @DonUggioni!

    A hover effect for the button would be a nice cherry on top but other than that really nice submit!

  • P
    Darrick Fauvel•490
    @DarrickFauvel
    Submitted over 3 years ago

    Order summary component - HTML, CSS, & Parcel

    #bem#parcel#sass/scss
    1
    Adrian H•420
    @AdrianX19
    Posted over 3 years ago

    Hi @DarrickFauvel

    really good job, well done! I would just try to make the sizes a bit closer to the design, right now the card seem to be pretty narrow, I would suggest increasing the max-width on .card element and I would increase padding for the .card-body, other than that it looks really good! :)

    Marked as helpful
View more comments
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