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

HTML CSS

Kristina•300
@frontend-en
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'm using mobile-first flow.

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

I tried to set the background to the entire height of the page and found several solutions.

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

I would like to receive a code review from my colleagues and accept changes if there are any.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 1 year ago

    I tried to preview this but the text is unreadably pale when I view on mobile. I think you need to check the colors you're using!

    Here's other feedback

    1. the use of landmarks is very muddled in this. The wrapper div should be a main, the main should be a div or article or section (whatever you prefer there are no benefits to any of them in particular). There should be no extra article inside the card wrapping only the text content.
    2. The image is the most important content on the page. That means it needs a properly written alt description. That needs to say what it is (QR code) and where it goes (to FrontendMentor.io). There is a good post in the resources channel on discord about how to write good alt text. Remember it is content readable by site users, it's not "code".
    3. When doing single component challenges like these remember to think about the context of where this is going to be used. This kind of card would never act as a page title. That tells you the heading level cannot be h1.
    4. It's better for performance to link fonts in the html head instead of css imports.
    5. Get into the habit of including a full modern css reset at the start of the styles in every project. Andy Bell or Josh Comeau both have good ones you can look up and use.
    6. This really is only a simple card with a few basic styles. There's no need for things like position relative and z-index. Strip out anything you don't need in the styles.
    7. There is no benefit to making the card a flex column unless you want to use the gap property for vertical spacing between it's children. All of the elements in this challenge stack by default so again the flex column properties could be removed.
    8. There should be no explicit widths or heights in this challenge. Remove them all. The card component only needs a single max width in rem. The image only needs display block and max-width 100% (and width 100% if you want).
    9. Font size must never be in px. Extremely important!
    10. There is no need for a media query in this challenge. But if you need them in future remember to always define media queries in rem or em not px
    11. The card should have padding on all sides. Make sure you understand the difference between padding and margin (there's another post about that on FEDmentor.dev).
    12. Make sure the component cannot touch the screen edges. That means either a wrapping element like body in this case can have a little padding on all sides or the component itself can have a little margin on all sides.
    Marked as helpful
  • Mahesh Ulpi•20
    @UlpiMahesh
    Posted over 1 year ago

    N/A

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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