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

Mobile-First Solution using css flexbox

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

Solution retrospective


Towards the end when I had everything laid out properly and I was playing with the font properties, I realized I could never get it just right. Even using the provided font size that I was supposed to use. Is this expected that you cannot get the exact words on each line with the right size?

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • v•110
    @ughvop
    Posted about 2 years ago

    You can fix it by padding- right & padding-left in the text, also you're not using the font-family Outfit

  • Steve•1,170
    @peanutbutterjlly
    Posted about 2 years ago

    hey 👋,

    yea, it can be a little tricky getting the solutions 100%, especially if you don't have the figma files.

    One thing I noticed is that your font-family looks different than the design, and that you set your font-size in pixels. That's usually frowned upon because if someone wanted to bump up the font sizes on their screen, that pixel value is 'locked in' - that's the reason it's usually better to go with REM's to change font-sizes.

    Another think you might want to look at after you've played with font-sizes and line heights is the margins you have set on your p tags and in your div - the fonts will fit in its box but it depends on how much margins/padding you have as well.

    Overall good job 👍 keep up the good work!

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