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

Single Price Grid Component Using CSS Grid

Kingsley Arinzechukwu•40
@ArthurKingDev
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone! I think I did my best on this. Feedback on how I can improve will be much appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • romila•3,550
    @romila2003
    Posted almost 3 years ago

    Hi Kingsley,

    Congratulations 🎉 for completing this challenge, the chart component looks great and responsive. There are some issues/suggestions I want to address:

    1. The a tag cannot be nested within the button tag therefore I would recommend you choosing one of those options.
    2. To make your button look more like a button, you can use the cursor property so that it looks clickable e.g. cursor: pointer;
    3. For your media query, the value of your min-width property is too large therefore I would recommend you using a smaller value such as 1000px or 900px. It does not have to reach 1440px until you make the card responsive.
    4. In mobile screen, the cards don't have enough padding therefore the texts and elements are all on the left side. Also, you can give your cards a border-radius like you used in desktop mode.

    Overall, great attempt and wish you the best for your future projects so keep coding 👍.

    Marked as helpful
  • Jeffery Evbodi•110
    @maro-og
    Posted almost 3 years ago

    Good job bro. I like how your codes are arranged. I'm a newbie in the web dev community and i'm also a student PT at BUK. I'll be glad if we can link up on twitter. Looking forward to your reply.

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