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

@traez's Single price grid component using HTML and CSS

Trae Zeeofor•490
@traez
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What I learned:

  1. Neatest and most efficient code written thus far
  2. Use combined selector (chained selectors) instead of unnecessary Classes/Ids
  3. Adhered to best practice for h1-h6 heading semantics

Continued development [Would appreciate any answers to below 2 questions]

  1. Smarter way to make CSS Grid responsive dimensions (height and width) when switching between mobile and desktop (using media queries)?
  2. Changing text (format) when switching between CSS Grid mobile and desktop (using media queries)?
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hello, Trae Zeeofor! 👋

    Regarding the CSS selector, I would argue that using a single class selector would be a better approach. I agree that id should be avoided but should be used instead. In this case, it might be possible to style all elements without id or classes. But, when you start working on a larger project, it will start getting harder to select the element that you want.

    Regarding your questions,

    • For responsiveness you have done a good job by using min-width media query and using em unit. But there are a couple of things that I'd to recommend.
      • Setting a max-width to the card and removing the width and the height properties. The only thing that the card needs to be responsive is a max-width to prevent it from filling the entire page. For the height, let elements inside it control it.
      • Setting only grid-template-columns. In this case, there's no need for rows since the element only spans through the column. Also, grid-template-columns: repeat(2, 1fr); is enough.
    • I would guess that "text-format" means the font styling like font size. I recommend simplifying it. There is a common font size like 1.2rem. You can set it as the body's font size. This way, you can just update the body element and then most of the elements will follow it.

    Hope this 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

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