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

Responsive QR Code Component using CSS Flexbox

accessibility, web-components, styled-components
Sania Saleem•110
@codeBloom361
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 proud of aligning content using Flexbox and I'll try to write CSS more neatly next time.

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

Aligning content was a challenge for me and Flexbox helped me overcome it.

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

I appreciate your feedback and advice. I like to get feedback on CSS. How can I write it more neatly and efficiently?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bhuvnesh Upadhayay•2,120
    @bhuvi819381
    Posted 6 months ago

    Overview

    1. Favicon Path Correction

    • Ensure the favicon path is correct in the <head> section.
    • Example:
      <link rel="icon" href="/path-to-your-favicon.ico" type="image/x-icon">
      
    • Use the browser's developer tools to check if the favicon is loading correctly.

    2. Use Semantic HTML

    • Wrap everything inside a <main> tag to improve structure and accessibility.
    • Example:
      <main>
        <!-- Your content here -->
      </main>
      

    3. Utilize CSS Variables

    • Define reusable CSS variables for consistency and easier maintenance.
    • Example:
      :root {
        --primary-color: #3498db;
        --secondary-color: #2ecc71;
        --font-size: 16px;
      }
      
      body {
        background-color: var(--primary-color);
        font-size: var(--font-size);
      }
      

    4. Avoid Fixed Pixel (px) Units

    • Use rem or em for scalable and accessible design.
    • Example:
      body {
        font-size: 1rem; /* 16px default */
      }
      

    5. Mobile-First Approach

    • Start designing for smaller screens first, then enhance for larger screens.
    • Example:
      .card {
        width: 100%;
      }
      
      @media (min-width: 768px) {
        .card {
          width: 50%;
        }
      }
      
    • For simple card layouts, avoid unnecessary media queries.

    6. Validate Your Code Before Submitting

    • After uploading on Frontend Mentor:
      • Check for accessibility issues.
      • Validate your HTML for errors using W3C Validator.
      • Review reports and fix any issues found.

    By following these guidelines, your frontend projects will be more maintainable, accessible, and professional.

    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