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

Aligning Everything in Order using div

Matthew•40
@gmatt20
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?

Honestly, I am proud of making a duplicate of something simple! Even though this was marked as beginner easy, it was not easy for me. I had to jump over a large hurdle to learn but eventually I got it! What I would do differently is to prepare myself. I cannot simply throw myself into code!

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

A big challenge I encountered is generally CSS. My weak spot right now is general styling and CSS. Particularly I want to improve on layouts, aesthetics, and positioning so I can make awesome websites and programs! I overcome them by literally coding more simpler. Whereas before, I had longer lines of code on HTML (which was unnecessary and the final lines of code on HTML is much shorter) and very little lines of code on CSS because I had no idea what I was doing. However, by watching some youtube videos and completing some curriculum classes on freeCodeCamp, I was able to make the final product! It was actually really easy to do.

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

As mentioned, I am having a tough time with general styling and aesthetics. I need to work on layouts, positioning, and aesthetics.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Steep Salvador•10
    @steepsalvadorman
    Posted about 1 year ago

    I think you should take the time to sit down and try to make it much more similar, as the size and spacing of the text are not the same. But the rest is very good, and I think it is a good job.

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