Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

3-column-preview-card-component-main

Thabiso•270
@SefalaThabiso
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had a bit of a problem with html class names. I didn't know how to name my elements. Im curious as to how proffesional come up with names for their id, class or variables

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Eileen dangelo•1,600
    @Eileenpk
    Posted over 2 years ago

    Hi Thabiso,

    To make naming easier I use BEM. BEM, which stands for Block-Element-Modifier, is just one of many front-end development methodologies, and whether or not it is the best choice for a particular project will depend on the specific needs and goals of that project. However, it is a popular and widely-used approach that many developers find helpful in keeping their code organized and maintainable.

    BEM is a way of writing HTML and CSS that is designed to make it easier to understand the relationships between the various parts of a web page or application and to make it easier to reuse and maintain code over time.

    To use BEM, you first identify the major "blocks" or standalone components on your page. These could be things like a header, a footer, a menu, or a search form. You then identify the smaller "elements" within those blocks, such as a logo within a header or a search button within a search form. Finally, you can use "modifiers" to indicate variations on a block or element, such as a different color or size.

    In terms of actual code, BEM uses a naming convention to make it easy to see which elements belong to which blocks and which modifiers are being used. For example, the class for a block might be "header", the class for an element within that block might be "header__logo", and the class for a modifier might be "header__logo--large".

    Cheers!

    If you found this helpful please mark it as such :)

    • Let's connect on LinkedIn! - @Eileenpk
    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
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.

Oops! 😬

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

Log in with GitHub