Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 8 months ago

Semantic HTML5 markup, CSS custom properties, Flexbox

Artem Kotko•230
@artemkotko14
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 am proud of making my first project on Frontend Mentor. I hope it's just a beginning of something great.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    clickglue•440
    @clickglue
    Posted 8 months ago

    Wauw if this is your first project, you've done an excellent job and there will be great things coming! Your style of coding is clean and precise. You keep things simple and well structured, very important. Three tips that you might find usefull: the more complicated the projects become, the important it will become to plan your work in steps. Maybe you already doing that, but it might help. Secondly: many good websites use a CSS reset, to make sure the design shows up correctly. Het is a link. Thirdly, you might consider looking into CSS variables. This helps you making consistent layouts, also in complex projects. Good luck, you will be great!

  • Grace•32,130
    @grace-snow
    Posted 8 months ago

    The html is pretty good in this, well done! The only improvement to suggest there is to treat this card more like a card component you would build in a real site — that means consider the context of how an where it would be used. A card like this would never be used to serve the main heading on a page, so you know it shouldn't have a h1. Use a lower importance heading level like h2 instead. Also, the alt text on the image would be more specific to the card where it's used. So instead of just "QR code", this should also say where that code goes ("to FrontendMentor.io").

    Last thing in html - make sure you Indent the code consistently so it's easier to read and spot bugs. Your code editor can even do this formatting automatically for you with prettier.

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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub