Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

QR-code

4rd2•60
@4rd2
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am most proud of being able to get flexbox to work properly. If I had to do this differently next time I would start with centering.

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

I had a lot of challenges with how to properly start the whole project. After an hour of cluelessness I decided to come back to the project and was able to get a start in.

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

I wasn't sure how to do mobile and desktop sizing. I also had trouble understanding if I was supposed to use exact measurements or use some other kind of method.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kostya D.•20
    @dvgldev
    Posted 11 months ago

    Well, lets see. You probably forgot to change the font of the text, for this job it was enough to add a line to the body, since there is only one font.

    font-family: 'Outfit', serif;

    html, body {
        height: 100%;
        background-color: hsl(212, 45%, 89%);
        display: flex;
        justify-content: center;
        align-items: center;
    }
    

    Also, you didn't set the pixel dimensions for the container and it's much different from the dimensions in the layout.

    <div id="container">

    width: 320px;
    height: 499px;
    

    The same with the image, but here you indicated the size, but it is not correct.

    <img src="images/image-qr-code.png" alt="qr-code">

    width: 288px;
    height: 288px;
    

    I would also advise you not to use ID when you are not working with JavaScript for example. It is better to use classes, because it can get confusing.

    Not bad for a start, I really hope to see your work in the future with progress. With love from Ukraine ;)

  • bedende•100
    @bedende
    Posted 11 months ago

    Basically exactly like the solution, impressive!

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

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