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

Responsive QR Code

Adeniyi Saint Bukola•80
@TopboySaint
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'm proud to have chosen this career path and I would like to be better

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

Fear to start a project or seeing it as what I can not do

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • 6xg0d•210
    @6xg0d
    Posted over 1 year ago

    Hey! That's a great start. Glad you decided to start learning Web Development Adeniyi! I'm not an expert, but after review your code i'd like to give you a couple tips that help me to code and to keep in mind:

    1. Write CSS in a separate file: It's quiet common to write a few CSS styles in the HTML element while learning our first steps in HTML, but it's highly recommended to start writing your CSS rules in a separate stylesheet instead of the HTML document itself. More organize and easy to read especially in projects with a significative amount of lines of code.

    2. Get used to write semantic code: It's important to give our content a semantic meaning, not just for good practices, but for accesibility too. Try to deconstructure your projects in smaller pieces, and start to section every part you think necessary to build you solution. In this case, think about the card: It has a header? A footer? What it's the semantic structure of this card? There's no one "correct" way to define a semantic structure, but a good semantic structure has to make senses to every developer who review your code!

    3. Talking about fear: Everybody had the same feeling at the beginning, and it's ok! Trying to learn something new can be hard, stressful, but at the same time rewarding and joyful! Just keep in mind that you're not going to know everything, but you need to be willing to learn as much as you can about this world :)

    Here are some sources that i'm currently using to learn and hope it helps you too:

    • https://www.w3schools.com/
    • https://web.dev/
    • https://developer.mozilla.org/en-US/docs/Learn/Accessibility
  • Kim•440
    @01057057kim
    Posted over 1 year ago

    I noticed that your card is not in the middle of the page. Here's a very efficient way to center the card:

    Apply this to the body (in order to work properly, don't use position or margins):

    body {
        min-height: 100vh;
        display: flex;
        justify-content: center;
        align-items: center;
    }
    

    I hope it helps!

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