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

Responsive design, CSS Flex box

Purushotham Sirasapalli•30
@purushotham91
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my second challange on front end mentor. I would like to know if there are any better way to name my class names. Most of the time i am stuck in deciding the class names for the elements. Is there any way or practice to write the class names without wasting much time or does it get better with more practice?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lakhvider Singh•170
    @Ls6375
    Posted over 3 years ago

    Hey there I have checked your css code & I have found that you have given class name to each and everything in you html. Listen it is not necessary to give name to each class you can just use selector to select that element for example

    <div> <p>hi <span> There </span> </p> </div> you can simple use div p span to access the particular element in you stylesheet

    you can also see my Respostry where I have completed the same project using very few classes

    https://github.com/Ls6375/Frontend-Projects_Frontend-Mentor/tree/main/4.%20nft-preview-card-component-main

    Marked as helpful
  • James F. Ciskanik•200
    @JamesTheLessFC
    Posted over 3 years ago

    Hi @purushotham91, Nice job on this! I remember wondering the same thing. I've found that naming classes does get easier with time (I don't spend more than a few seconds thinking about it now.) However there are a few things I do keep in mind. When a project is especially complex and you come back to it after a break, you'll thank yourself for giving your classes names that make sense and are easy to tell what they are. For instance if it's a div element functioning as a wrapper/container, include that in the name (i.e. "gallery_container"). It's also a good idea to be consistent with your naming, like sticking to camelCase or using underscores to separate words. Or if you're giving class names to your buttons, you could do something like "submit_button" and "delete_button", etc. Naming these "button_1" and "button_2" will be confusing once you have a lot of classes in your project. Above all, it should be easy for someone reading your code to figure out what the class name refers to.

    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