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

Separations of Concerns (HTML & CSS)

sass/scss
Eugene Clark•50
@clarkjr2016
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 most proud of downloading and learning SASS to build this application. I am also proud of myself for relearning git/github. Finally, I'm proud of myself for attempting to follow the workflow that front end mentors suggested. It's given me a systematic way to approach front end development.

I would be more strict with the application of the workflow.

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

The challenge that I face is my own frustration that I feel when things aren't "pixel perfect". I also faced a challenge of installing SASS. I struggled to utilize it when installing it in my Windows PATH, but I switched to using the "Live SASS Compiler" extension on VS code.

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

I would like help with project management. I would like help in better developing workflows to systematically complete projects.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • CecDor•60
    @CecDorWEB
    Posted about 1 year ago

    Hello, Congratulations on your solution !

    Things you could improve ✍️:

    • Use the font indicated in the style guide with the link to go to the web site. It's possible to use <link> or @import to retrieve the font.
    • Try using semantic HTML elements like main, section and article.
    • I suggest using clear descriptive CSS classes like .card, .card-title and .card-description.

    Happy coding! 😎

    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