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

Qr Code Generator made with HTML and Tailwind CSS

tailwind-css
Rafiza Hanif Rahd•180
@raffee12
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?

Finishing this project is something that I am mostly proud of . But next time I will focus more on the responsiveness.

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

Adjusting the image on the container was the most challenging part. Then I put widths to the container that's how I solved this.

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

I made a mistake while doing the project which is I didn't notice that my browser was on 150% zoomed in. So if someone click on the link to see the actual result they may watch this project more smaller. So I might encourage if someone help me with the adjustments . The specific width that can make the site look alike with the original.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Huy Phan•3,430
    @huyphan2210
    Posted 7 months ago

    Hi, @raffee12

    This challenge includes a Figma file that you can open to view the page layout. If you're unfamiliar with using Figma, I recommend researching how to navigate and utilize it effectively.

    Once you open the file, navigate to the Designs page. There, you'll find the layouts for how the card should appear on both mobile and desktop.

    Use Figma's tools to measure dimensions, spacing, margins, and other design details. Mastering these tools is crucial as you work toward becoming a front-end developer.

    Hope this helps!

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

    Everything is good You should use one h1 in everything project.

    And another thing you link css but using tailwind css I can't even find tailwind css cdn link

    How you do that

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub