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

CSS classes, Google Fonts, CSS attributes

Burak Uğraş•90
@burakugras
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 will feel free to ask any AI assistant. I am loosing my time while trying to push myself unnecessarily.

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

I could not find suitable attribute. And I had problems with div alignments. But solved the problem by searching new attributes.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mahmoud-AbdelKarim•600
    @Mahmoud-Abdelkarim777
    Posted 7 months ago

    I saw your coding, I think it's good, but I have a comment that will help you. Remove the margin and use a height in body and the problem will be solved. I think you should study flexbox more so that you can learn how to center the element in the middle of the screen. body { justify-content: center; align-items: center; font-family: sans-serif; display: flex; background-color: hsl(212, 45%, 89%); flex-direction: column; min-height: 100vh; }

    Marked as helpful
  • Asilcan Toper•2,960
    @KapteynUniverse
    Posted 7 months ago

    Merhaba Burak, good job.

    You didn't ask for feedback but here it is :D (I always give feedback to fellow turkish people nonetheless)

    Since you used flex on the body, instead of margin: 15%; you can give body a min-height: 100vh; to center the card vertically.

    Landmarks, (or this page) are essencial for accesibility. Every page needs one main. Wrapping your card div with a main would be good.

    Avoid using fixed values like width: 200px;, for better responsiveness use max-width: 12.5rem;. 200 is a bit small tho, 20rem would be better.

    Images need a meaningful alt text, unless decorative. For this case, i think something like "QR code leading to frontendmentor.io" might be ok.

    Never use px for the font sizes. So people with visual impairment can adjust the font size on their browser. Use rem for especially font sizes and media queries. You can also use clamp function for better responsiveness.

    The WCAG criteria states that line-height should be at least 1.5.

    I recommend you to use a modern css reset for every project. You can check Andy Bells reset too.

    Also using a external CSS file might be better than internal

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