Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

qr_frontend mentor

Felix D. Lozano•10
@Felix4854
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


All feedback is welcome, have a nice day

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bryan Li•3,530
    @Zy8712
    Posted about 2 years ago

    Looks pretty good. Some things I suggest you add if you want your code to appear slightly more similar to the original design:

    body { 
    min-height:100vh; /* this makes your box vertically align to the center */
    background-color:  hsl(212, 45%, 89%);
    }
    
    .modificador h1{
    text-align: center;
    }
    
    .modificador p {
    text-align center;
    }
    

    One other thing is that I would suggest you to use <h2> instead of <h1>. Besides that it looks like you a firm grasp on the fundamentals 👍.

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted about 2 years ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have other recommendations regarding your code that I believe will be of great interest to you.

    CSS 🎨:

    • Looks like the component has not been centered properly. So let me explain, How you can easily center the component without using margin or padding.

    • We don't need to use margin and padding to center the component both horizontally & vertically. Because using margin or padding will not dynamical centers our component at all states

    • You already using Flexbox for layout, but you didn't utilized it's full potential. Just add the following rules to properly center the component.

    body {
    min-height: 100vh;
    }
    
    • Now remove these styles, after removing you can able to see the changes
    body {
    margin: 1.25rem;
    margin-left: auto;
    }
    


    • Now your component has been properly centered

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

  • roodhouse•520
    @roodhouse
    Posted about 2 years ago

    Hey. Great job! You have the spacing and padding/margins down really well. IMO you should utilize more container divs to help with the styling. For instance if you were to drop a <div> <div> <h1> then you would be able to manipulate the 2 higher up divs before you touched the h1. This would allow you to then see what styling is left to implement on h1. You might find one or two things or nothing is needed at all. Personally, I attempt to place the bulk of my styling on divs and if needed, then I style the data directly. Anyway, great start and keep it going!

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
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

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

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