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

QR Code Challenge - using Next.js and Tailwind

next, tailwind-css, react
P
chelsea-here•160
@chelsea-here
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 biggest challenge for me was getting the Github and git working. I tried to follow the provided instructions but kept getting errors due to issues with trying to merge two independently created repos.
In the end I found the solution I needed here: Github Solution

The other item I struggled with was getting the card centered vertically AND horizontally. I described my solution in the README.md file.

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

I don't think I need help with this, but if anyone has suggestions on best practices or optimization it would be appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gwenaël Magnenat•1,540
    @gmagnenat
    Posted about 1 year ago

    Hi, congrats on completing the challenge ! I checked your repo and your url. there are a couple of essentials basics you should fix.

    • I have an issue with the text color. it display as white on the live url. (firefox and chrome).
    • Currently the solution isn't accessible in case of default font size change by the user. You can do a reflow test to see this. Update the default font size of your browser. Your layout should scale correctly and respect the user settings.
    • The reason for this are the arbitrary values you added in pixels. You should never use pixel for everything related to fonts and sizes to keep your design responsive and accessible. Why font-size must NEVER be in pixels. By default tailwind uses rem so you can add the values as rem in your config file or use rem in arbitrary values.
    • I don't think you need the min-w-screen on your main. By default the full width of the screen is already set.
    • I don't think the <header> is correctly used here. it should be outside of the <main> and have a banner role (repeated navigation and header on multiple page)

    I hope this review helps to improve the solution and refresh some important concepts on the basics.

    Happy coding !

    Marked as helpful
  • neven.cebic•530
    @redizork
    Posted 12 months ago

    99% pixel perfect :)

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.

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