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

Using SCSS and BEM naming

SuzuMantan•370
@agusthas
A solution to the Profile card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone, this is my solution to the challenges. I would love some feedback or advice on:

  • Background Image Position. (is using vw and vh the right way to position the background? or should i just use position absolute and use top, left, right, bottom ? )
  • BEM Naming classes. (its my first time using BEM naming, any advice on how i should named the class would be appreciated).

Thank you!.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted about 4 years ago

    Hi

    This looks really good! Viewing on mobile the top left bg circle isn't visible but the rest looks spot on.

    BEM naming looks fine ☺

    But html markup needs some attention:

    • alt text should be intentionally blank on meaningless / decorative images like the bg pattern.
    • if that meaningless image happens to be an svg you should also include aria-hidden true on it
    • meaningful images (like the profile picture do need alt text, but it needs to be readable text describing the image. So in this case it should be his name
    • not sure why your first heading is a h4? What three levels of headings would you expect to come before this if it was included on a webpage? Remember heading levels are 100% about semantics and 0% about styling.
    • similarly, would numbers like 80k make sense on a contents page as headings for an element? Nope. So they shouldn't be headings. Their meaning is tied very closely to the word that accompanies them so the html elements chosen need to reflect that. Think list items or paragraphs with spans inside, think the description list element, think tables with the numbers as tds and words as ths.... Any of those would be valid semantic html to present this information.

    I hope that all makes sense and helps you

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.

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