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

Single Price Grid Component using Sass & Grid

Elena Stagg•220
@elenastagg
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I didn't have the design sketch so matched the styles & measurements as best I could. I struggled with making the project mobile-first and adapting the code for larger screens - so I'd be keen to have feedback on the media queries - do they look a bit hacky? I'd also like feedback on making my CSS cleaner in general.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shahar Levy•85
    @monodonBrand
    Posted over 5 years ago

    Hey. My only suggestions for you for this task is to use pixelperfect extension for your browser so you can really be accurate in sizes and spacing.

    I would not use utility classes in a project of this scope, they add duplication if you are already using variables.

    And finally use some kind of a reset.css file to change browser default styles (such as list styles), and that will add clarity to your code.

  • Gerben Dol•3,115
    @GerbenDol
    Posted over 5 years ago

    Cool to see you use utility classes on here - great small scale challenge to practice! 😁

    There are some things I think you may have over-complicated a bit:

    • I feel like centering the component-container could've been easier using grid or flexbox, which will give you a bit more flexibility compared to absolutely positioning it.
    • Set your border radius on the component-container and use overflow: hidden; to stop the inner boxes from overlapping the rounded corner. That will save you writing the specific border radius for each box in your different media-queries.

    I think your media queries look just fine! Adding the grid on bigger screens I think is the perfect solution here, so you did really well! 💪🏻

  • Sebastian•65
    @primocodetoday
    Posted over 5 years ago

    Mobile-first approach. Very nicely.

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