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

html-css-qr-code-component

devguff•10
@devguff
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?

This is my first frontend mentor solution. I really tried to make the solution to be as easy to change as possible using css variables. I'm not sure if I am using all the recommended best practices for things. For example, I think there should be some sort of css property for ensuring the screen width can never be less than the width of your component. Not really sure what this is right now but just trying to get used to flow of how to build this type of stuff.

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

Figuring out how to get the included attribution required me to ai search for a solution. I understand how it works but it feels like there may be a better way. Also the spacing around items was a bit tricky.

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

Know what best practices I could be using that I am not. Want my solutions to be less hacky in the future.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • RobinsonGabriel•60
    @RobinsonGabriel
    Posted about 1 year ago

    Hi dev,

    I don't think it's a terrible crack at it at all really. Esp if you don't do this stuff a ton it can take time to adjust. Points for using variables as it will make life easier on larger sheets, and I forgot CSS even supported them until I did a few designs myself (we all learn at our own pace... mine's just a bit unique.)

    That said, what do you think is hackney in your design? Generally what's To answer the question around the component fitting the screen: you are probably thinking of working with a media query.

    https://www.w3schools.com/css/css3_mediaqueries.asp

    ^^short explanation of them. So for example: you might have your component set to a certain unit as your minimum, generally when it starts to mess around with the text orientation, pic size, etc.

    Hopefully this gives you something to chew over

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