Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 22 days ago

QR component center using flexbos

Curtley•80
@curtleyAk
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 that I could complete it with my current knowledge. Layouts are quite tricky, and I need more practice.

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

I tried using grid before, but I was overcomplicating it a bit. Then I used floats, but the concepts of floats are still a bit tricky to understand, but I will get there with more practice.

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

Mostly, the CSS layouts as a whole, some tips and tricks would do me well to understand them better.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Michael•140
    @Networksentinel
    Posted 22 days ago

    Hi there!

    You did a great job—it looks awesome!

    I just have one small suggestion regarding semantics.

    I learned a valuable rule that stuck with me: "If there's a more semantic tag you can use, go for it—avoid <div> when possible. Your SEO and accessibility will thank you later!" 😄

    You used a <div> to group related content—sound familiar?

    I think <section> would be the ideal element here. 🙂

    Keep up the good work and good luck with the grind!

  • Renan Guilherme•30
    @codebyneander
    Posted 22 days ago

    Não aplicou semântica corretamente.

    1 - Utilize tags como <main> para colocar o conteúdo principal dentro, para alertar os navegadores.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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