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

CSS Flexbox

bem
josip-h•90
@josip-h
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?

Building the QR code challenge is a nice and easy introduction to learning the whole process of working on a project. For me the biggest thing I got out of the project is that I got introduced to design tools like Figma and how to use design files to efficiently complete the project. Also, by using the provided README template I learned how to structure and what to include in the project documentation.

As of now I have not used the git and GitHub that much and in the upcoming projects i will take more care of when to push changes to the repository so as not to push major changes to multiple files at once.

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

1. Learning how to use Figma

By reading articles included on the learning path and by watching a youtube video I've got a good enough introduction to Figma to use the design files provided. Link to mentioned YouTube video: Intro to Figma for Developers

2. Using git and GitHub

Also by reading through articles included in the course I refreshed my knowledge about how to use git and Github and was able to do what was needed.

3. Making README.md file

By using the provided template for readme file I learned how to structure and what to include in readme file.

4. Publishing solution on GitHub Pages

By going through the tutorial on the GitHub Pages homepage, creating a live page for the solution was easy.

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

1. Is there a way to make an HTML card component code more accessible?

2. Did I use the BEM naming convention in the right way?

3. Would you consider my CSS code to be readable?

Since I am somewhat new to coding any suggestions on how I can improve my code would be greatly appreciated. Thanks!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on josip-h's solution.

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.