Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Order summary card solution

Marija Havaic•150
@marijahavaic
A solution to the Order summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • How do you name your classes and is there any naming convention I could follow?
  • Is it better to have a descendant combinator (body p) or class (.text) for styling?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • alfred thompson ovie•820
    @alfredthompsonOvie
    Posted almost 3 years ago

    There are a couple of naming convention you can follow, but i could suggest using BEM..

    I always take specificity into account when choosing between classes, IDs or descendant selector because i aim to reduces the specificity as much as I can

    Marked as helpful
  • Mic-Saw•360
    @Mic-Saw
    Posted almost 3 years ago

    Once you have mastered the BEM notation (and Sass), I suggest you familiarise yourself with the 7-1 method of organising code; it is very useful for more complex projects.

    https://www.learnhowtoprogram.com/user-interfaces/building-layouts-preprocessors/7-1-sass-architecture

    Marked as helpful
  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    Hello Marija Havaic, congratulations for your solution!

    Answering your question:

    1.Naming classes: I mainly try to name my classes, trying to be clear about what these classes do or for which kind o element block I'm using. For example, a class called .rounded adds border-radius in various elements or the class .container, which is used to group some elements and give them properties like margins, paddings, background, etc.

    You consider using the BEM methodology for CSS class naming, is widely used in the dev community and maybe the most famous of all methodologies.

    You can read more about BEM here: http://getbem.com/introduction/

    2.Class x Descendant Combinator: I think that if you're coding something simple like this card, maybe you can use the element itself like an img or a p, but if something complex with many elements that repeat over the page like images, headings and etc. It's better to use class and manipulate each element separated.

    I hope it helps you; happy coding!

    Marked as helpful
  • Yokke•620
    @Jexinte
    Posted almost 3 years ago

    Hello @marijahavaic ,

    There is convention use with SASS Pre-processor called BEM , more details here :

    https://en.bem.info/methodology/

    In hope it helps !

    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

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

Oops! 😬

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

Log in with GitHub