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

single-price-grid-component

brian•630
@brian-maker
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


should i set the height for the whole card or i can set the height for each and every small card while in mobile format

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Divine Obeten•2,415
    @Deevyn9
    Posted over 2 years ago

    Hi Brian, there's and issue with the github pages and the site isn't loading.

    Marked as helpful
  • vabel17•120
    @vabel17
    Posted over 2 years ago

    I'd say avoid setting height on elements that not necessarily need it. Let your content shape its container.

    Marked as helpful
  • Adán Estévez•320
    @rafdidact
    Posted over 2 years ago

    Hey, Brian! I got a few suggestions that would make your solution even better.

    • You should add a padding to each one of the sections inside of your card. In my solution for this challenge, I gave each section a padding of 2rem for the mobile version, and 4rem for the desktop version. You can check the code visiting my repository.

    • Your card component and your button should have a box-shadow property matching the shadow effect they have in the design. Again, you can check my repository for reference.

    Feel free to reach out if you need help!

    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