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

QR Code Webpage using HTML/CSS

snhaydar•20
@snhaydar
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 proud that I was able to create this project in just a few hours. I have coded in these languages before, but not well and not for a very long time. Next time, I will try to apply these new skills to break down the problem in a more orderly way instead of all willy nilly.

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

I encountered problems with the spacing, padding, Google Fonts -- even setting up the project was quite a challenge for me. I overcame them by searching my problems on Google and was able to troubleshoot solutions.

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

Here are a few things I would like help with:

  1. How can I make my code more efficient/readable? Are there things that I did that seem convoluted or could be done in a simpler way? Are my names descriptive enough?
  2. What could I have done better to get a pixel-perfect site? I had to play around with a lot of the pixel amounts and wasn't sure if I should be doing something to get padding that perfectly matched the Figma file. (Ex: Look at my "card" class in my CSS file. I just chose 14px because it looked somewhat right. What could I have done to get the right value instead of guessing?)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rayane Taguti•80
    @tagutirayane
    Posted about 1 year ago

    Hey!

    Your HTML file is great. It is awesome that you found a solution different than mine. Maybe using "display: flex" at the body component would be easier to space things out without having to create a new class (the container) to work with the text.

    One site that always helps me with flexbox is this one: https://css-tricks.com/snippets/css/a-guide-to-flexbox/

    Abraços from Brazil!

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.

Oops! 😬

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

Log in with GitHub