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

QR-code-component using Html and Tailwind CSS

tailwind-css
Paulgulti•100
@Paulgulti
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

The parent div with the 100vh vh needs the property display flex inorder for the child div elements to arrange vertically.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Feng•400
    @niuguy
    Posted 6 months ago

    (Below is generated by cursor and edited by myself)

    1. Semantic HTML Looking at the HTML structure:
        <div class="body h-[100vh] flex bg-slate-300">
            <div class="card w-[280px] h-[420px] m-auto bg-white rounded-2xl p-3">
                <div class="">
                    <img class="rounded-lg" src="images/image-qr-code.png" alt="qr-code-image">
                </div>
                <div class="p-4 mx-auto">
                    <h1 class="font-bold text-slate-900 text-center">Improve your front-end skills by building projects</h1>
                    <p class="font-normal text-slate-500 text-[12px] text-center my-2">Scan the QR code to visit Frontend Mentor and take your coding skills to the next level</p>
                </div>
            </div>
        </div>
    

    he solution uses basic div elements without semantic HTML tags. It could be improved by using:

    • main for the main content wrapper
    • article or section for the card component
    • header for the title section
    • footer for the descriptive text
    1. Accessibility

    Several accessibility improvements could be made:

    • Missing alt text is descriptive but could be more specific for the QR code
    • No ARIA landmarks or roles are defined
    • Color contrast appears good (dark text on white background)
    • Missing language attributes for text content
    • No skip links (though not critical for this simple layout) Suggested improvements:
    <main class="h-[100vh] flex bg-slate-300">
      <article class="card w-[280px] h-[420px] m-auto bg-white rounded-2xl p-3" role="article">
        <div class="qr-container">
          <img class="rounded-lg" src="images/image-qr-code.png" 
               alt="QR code linking to Frontend Mentor website" />
        </div>
        <header class="p-4 mx-auto">
          <h1 class="font-bold text-slate-900 text-center">
            Improve your front-end skills by building projects
          </h1>
          <p class="font-normal text-slate-500 text-[12px] text-center my-2">
            Scan the QR code to visit Frontend Mentor and take your coding skills to the next level
          </p>
        </header>
      </article>
    </main>
    
    1. Responsive Design

    The layout uses:

    • Flexbox for centering
    • Fixed width (w-[280px]) and height (h-[420px]) for the card
    • Viewport height (h-[100vh]) for full-height layout While this works, it could be improved by:
    • Using responsive units (rem/em) instead of fixed pixels
    • Adding media queries for different screen sizes
    • Considering minimum margins for very small screens
    1. Code Structure The code is: ✅ Relatively clean and readable ✅ Uses Tailwind CSS classes logically ✅ Maintains consistent indentation Areas for improvement:
    • Separate components into reusable parts
    • Use more semantic class names
    • Consider extracting common styles into Tailwind components
    1. Design Fidelity

    The implementation appears to be aligned with requirement on:

    • Centered card layout
    • Rounded corners
    • Appropriate spacing
    • Typography hierarchy
    • Color scheme using slate colors
    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