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

Single price grid component

Veronika•110
@designver
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    You've done an awesome job with this challenge! Well done on making the page look like the design.

    I noticed that you hard-coded the width for the .container element at smaller screen sizes:

    .container {
      width: 19.4375rem;
    }
    

    This causes some overflow issues on screen sizes where the viewport width is smaller than the width of the .container element.

    It's generally not recommended to hard code a width as it isn't responsive to changes in viewport width.

    If you want the width of this element to be limited to a certain value, you can do this instead:

    .container {
      max-width: 19.4375rem;
    }
    
    @media (min-width: 39.6875em) {
      .container {
        max-width: 39.6875em;
      }
    }
    

    This will allow the element to shrink as much as its contents allow it to, which is more responsive and therefore better for user experience.

    The button does not react to being hovered over, which makes it difficult to tell that you're interacting with the button.

    To fix this, you can change the button's background colour upon being focused on or hovered over:

    .sign-up {
      cursor: pointer;
    }
    
    .sign-up:hover,
    .sign-up:focus-visible {
      background-colour: #9ccc4c
      color: #eee;
    }
    

    cursor: pointer; changes the user's cursor to a pointer to make it clearer that you're hovering over a clickable object.

    :hover is a pseudo-class which allows you to style the button when it's being hovered over, and focus-visible is a pseudo-class which allows you to style a button that's been focused on via keyboard navigation.

    I've used these two pseudo-classes to darken the background colour and font colour of the button to make it more obvious that the button is being interacted with.

    These changes are not only good for visual reasons, but also make your site more accessible and user-friendly.

    This is a very minor thing, but you could also consider adding some whitespace on either side of the .container element by applying margin or padding to the body element.

    Whitespace is good for visual balance, which improves user experience as well.

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