Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

First attempt at using HTML and CSS

Riley Green•10
@GreenDiggy
A solution to the QR code component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The biggest struggle I had was the sizing of elements and having proper ratios to match with the design pictures. What are some more effective ways of approaching the scales and sizing when basing the design off of a static image?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    Hello there, Riley! 👋

    Congratulations on completing your first Frontend Mentor challenge! Good effort on this challenge! 👍 It's great that you are able to finish this challenge without any media query! 👏

    Three things that can be improved.

    • First, put all the styling on the styles.css. I notice an inline styling on the body element. It's a good thing to always separate the styling from the HTML. In a big project, it can prevent a lot of issues because inline styling has the highest specificity.
    • Second, the QR code is the main content of this page. It should not be hidden from screen reader users. Add an alternative text that says something like, "QR code for Frontend Mentor".
    • Third, I would highly suggest using flexbox to center the card. Absolute positioning is not a good choice if flexbox and grid can do the job. Also, add max-width to the card element to prevent the card from becoming too large on the widescreen.

    That's it! I hope this information is useful! 😁

    Marked as helpful
  • Arthur Roberts•410
    @arfarobs
    Posted over 3 years ago

    Hey. If i was designing this just from the picture. I would use the text as a method to scale a close size. In the downloaded files for the project there should be one that tells you what styles to use. This will tell you the font sizes, colors, etc.

    In the design picture you can see that the heading is two lines. After the word "front-end" you will see that the line breaks. By looking at it this way you can make a better estimation for the components width.

    In a project like this i think its best to try and style things in relation to the information that you are given in the style guide.

    Marked as helpful

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

Oops! 😬

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

Log in with GitHub