Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 28 days ago

Responsive design using flexbox.

react
Vivek Singh•130
@viv2711
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 am just proud that I was able to complete it.

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

Since it was first challenge on this roadmap, it was farely a simple challenge . I didn't came across any major challenge. It was first time to work with figma design that was some what challenging.

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

None. I was able complete it by myself.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alejo2304•40
    @Alejo2304
    Posted 28 days ago

    Does the solution include semantic HTML?

    The code is clear and includes sematic HTML, for example:

    <main>
        <div className="container">
          <img src="/image-qr-code.png" alt="qr-image" />
          <h1>Improve your front-end skills by building projects</h1>
          <p>Scan the QR code to visit Frontend Mentor and take your coding skills to the next level</p>
        </div>
    </main>
    

    The <main>, <img>, <h1>, <p> are really descriptive for the solution.

    Is it accessible, and what improvements could be made?

    Yes it is, and the live site works fine for both mobile and Desktop

    Does the layout look good on a range of screen sizes?

    Surely it does.

    Is the code well-structured, readable, and reusable?

    The use of React for the project make it really readable and easy to divide into components.

    Does the solution differ considerably from the design?

    No, there is really small difference on the style for the style <h1> <p> tags.

    For the <p> the font size looks a little bigger on the solution, and on the <h1> you may see on the solution the text is arrange on 3 rows, thought this doesn't really affect the overall experience.

    Nice fist project!.

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