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

Website build for the first project using Flexbox

Heriberto Fabian Santiago•20
@HeribertoFabian
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 completed my first Frontend Mentor project and was able to submit it correctly. I learned how to set up the project structure, upload my solution to GitHub, and publish it using GitHub Pages.

If I were to do it again, I would focus more on refining my layout using better spacing, box shadows, and more attention to design details. I also plan to get more comfortable using CSS Grid and improving my responsive design skills in future projects.

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

The biggest challenge was understanding how to correctly translate the provided design into code, especially getting the spacing, alignment, and sizing to match as closely as possible. I also had to adjust my understanding of how to center elements vertically using Flexbox and vh units.

I overcame these challenges by researching best practices, reading documentation, and getting feedback during the process. I learned a lot about using box-sizing: border-box and how important consistent spacing is to achieve a better visual result.

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

I would appreciate any feedback on my layout structure and CSS organization. Since this is my first Frontend Mentor project, I'm still learning how to improve my spacing, centering, and general code cleanliness. Any tips on better practices for Flexbox and how to structure CSS for small projects would be very helpful.

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 Heriberto Fabian Santiago'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.