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

Styled and structured component using semantic HTML & CSS

Paloma-Cardozo•50
@Paloma-Cardozo
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 of how I structured my CSS using Flexbox to create a clean and responsive layout. It was a great way to practice organizing elements efficiently.

Next time, I would like to explore more advanced CSS techniques, such as Grid, to enhance my designs and improve responsiveness.

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

One of the main challenges was ensuring that the layout looked consistent across different screen sizes. I initially struggled with spacing and alignment, but I overcame it by testing different Flexbox properties and adjusting margins and paddings.

Another challenge was properly linking fonts within my project, which I resolved by experimenting with different font import methods and verifying the file paths.

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

I would appreciate feedback on best practices for structuring CSS files to keep them organized and scalable.

Additionally, I’d like guidance on how to optimize font loading to ensure better performance and compatibility across browsers.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Ant105•110
    @Ant105
    Posted 4 months ago

    Disclaimer: I'm very new to web development, so please don't take my feedback seriously.

    I think considering that the site only needs two text elements, it might be better to use Static font instead of the Variable font, maybe it will optimize the fonts a little.

    Also .ttf format is not the best for web, better use .woff2 or .woff, as far as I know Google Fonts doesn't provide these formats, but I use CloudConvert to change formats, I think it's better than using .ttf, but i'm sorry if i'm wrong.

    You created a great code btw!

    Marked as helpful

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

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.

Oops! 😬

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

Log in with GitHub