Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

QR code component

ha308ing•240
@ha308ing
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?

Nothing to be proud of. I guess next time I should use some fancy frameworks and tools.

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

Tried to achieve pixel perfect layout, getting sizes from photoshop, but didn't get how to get font parameters like line-height and letter-spacing and ended up with font tab of firefox dev tools and extension PixelGrid that draws grid (with option of grid size of 1x1 px, and multiple grids the same time)

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

How to achieve pixel perfect fonts from .jpg design file?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jeje•2,050
    @AkoToSiJeromeEh
    Posted over 1 year ago

    Hey ! great work out there i just notice that you are using margin on the .card in order to center the card component but it doesn't work as expected , i suggest that you use display : grid or display : flex in-order to center the card , thats all happy coding !!

    by adding the display : grid and place-items : center you can achieve to center the card and any future work you create : )

    body {
      background-color: var(--light-grey);
      font-family: Outfit, sans-serif;
      font-kerning: none;
      min-height: 100vh;
      width: 100%;
      display: grid;// add this or you can change display : flex;
      place-items: center; // add this or you can change align-items : center with justify-content : center;
    }
    
    .card {
      background-color: var(--white);
      border-radius: 20px;
      box-shadow: 0 25px 25px 0 var(--shadow);
      margin: 212px auto;// you can remove this
      padding: 16px 16px 40px;
      text-align: center;
      width: 320px;
    }
    
    Marked as helpful

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