Simple Flexbox solution of this QR project!

Hi Alan!

Great job with the code, love what you've done man. Just had a few recommendations but feel free to disagree.

In the HTML:

• Get into the practice of wrapping the main content of your project with the main tag, even if it's the only piece of content on the page.
• I know that more than likely the heading in this component wouldn't be a h1 level heading if it was included in a website, but given that it's the only content on the page it should be regarded as the main heading on the page, and therefore does deserve to be written using a h1. The h1 is simply for the most important text on the page, the introduction, and what is the page about. Every page should have one. h2, h3, etc. are for headings of lesser importance, and for them to be of lesser importance, there must first be a heading of greater importance. If the h1 tag appears to be inappropriate it's probably because of its appearance, but don't let appearance prevent you from making your HTML as semantic as possible. You can always fix the appearance later with the CSS.
• I'd recommend looking into the BEM Naming Convention for classes. It makes it easier to write classes for you as a developer, and easier for other developers to understand your code (https://codeburst.io/understanding-css-bem-naming-convention-a8cca116d252)
• I'd recommend using the picture tag, it's better than just using the img tag. More on that here: https://blog.bitsrc.io/why-you-should-use-picture-tag-instead-of-img-tag-b9841e86bf8b

In the CSS:

• I like how you've separated the different properties in your CSS based on what they do, for example how you have the display properties separate from the dimension properties separate from the color properties, etc. It makes the code a lot easier to read. However, I would recommend putting anything that has to do with the dimension of the elements in the same group though, for example, instead of separating width from padding, I'd put them in the same group, because they all contribute to the overall size of the element. Things like a margins, and borders also contribute to the overall size o an element. I also include font-size when I write my CSS, but it's a bit more debatable I guess.
• I'd recommend using em and rem units. Em units for things like padding, margins, border, etc. and rem units for fonts. They are both linked to the font sizes you use so with this method you can easily adjust the size of a lot of things on your page simply by adjusting the font-size in the html selector. Also because em is linked to the font-size, you don't have to scale up buttons if you increase the font-size, it'll do so automatically.

Hope this helps, and sorry for any typos if there are any:)

Hi Alan 👋🏾

Congratulations on completing this challenge. Your solution looks great. I have some suggestions regarding your solution if you don’t mind:

I suggest that you keep all your CSS in one place. It's great that you have your external stylesheet, so you could move the styles that you have in the index.html to your stylesheet.

For better accessibility, try to use semantic elements whenever possible. For instance, the <div class="container"> could be replaced with the main tag, <main class="container"> , and this <div class="attribution"> could be <footer class="attribution">

Overall Excellent work! Hopefully, this feedback helps.