Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

single-price-grid-component

Hossam Zayed•110
@hossamzayed201
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Venus•1,790
    @VenusY
    Posted over 1 year ago

    Great work on this challenge! You've done a good job of replicating the design of the page.

    I noticed that the card isn't centered properly on smaller screen sizes/viewports because of the default margin added to the body element by the user agent stylesheet in combination with the width: 100vw property you've added.

    To fix this issue, you could use the following code:

    body {
      margin: 0;
      width: 100vw; ❌
    }
    

    margin: 0 removes the margin added by the user agent stylesheet.

    I also removed width: 100vw as it's redundant. The body element takes up the entire width of the viewport by default, so it's not necessary to specify it to do so.

    I also noticed that the entire card, including the text, shrinks when the viewport's height is reduced.

    While this technically makes your page responsive, it isn't ideal for user experience or readability because it means that the font size is based on the viewport's size, causing the text to be unreadable at smaller viewport heights due to how small it is.

    Not only that, because you've set the font size using vh values, the user can't change the size of the font through their browser settings, which is crucial for accessibility.

    It's important to allow users to increase the font size of your page as needed so that they can view the content comfortably, especially for those who have vision problems.

    Finally, there's no indication that the button is a clickable element because there are no changes in styling, which is important to improve the user-friendliness of your site.

    To improve this aspect of your page, you could change the font and background colours on hover, as well as the cursor type:

    .container .card .buttonSection .leftSide button {
      cursor: pointer;
    }
    
    .container .card .buttonSection .leftSide button:hover,
    .container .card .buttonSection .leftSide button:focus-visible {
      background-color: #9ab22a;
      color: #ccc;
    }
    

    Other than that, this is a very good solution!

    Hope this has been helpful! If you need me to elaborate on anything, please feel free to message me. :)

    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