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

Single price grid component

Alexandar Živkovič•70
@stashix
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Looking for any feedback.

A specific question - is there a way to only declare the border-radius on the card container without having to re-declare it on the individual sections and resetting it in a media query when the view switches to desktop? Apparently padding and border-radius don't play nice, but I didn't want to introduce extra divs.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bryan Li•3,530
    @Zy8712
    Posted over 1 year ago

    Your site looks pretty.good. If I'm reading your question right, you should be able to just declare border-radius for the parent container that holds all three sections and then just use overflow: hidden to make the individual sections seem curved in the proper places as well.

    Hope this helps

  • Marzuk Sanni•1,360
    @Zukizuk
    Posted over 1 year ago

    Hello there

    Congratulations on completing this project

    I have few suggestions about what you asked about that might be of help to you:

    When you set border-radius on the parent, it doesn’t automatically apply to the child unless you explicitly define it. This allows for flexibility in styling, as you might want the child to have a different border-radius than the parent for design reasons.

    If you want the child to inherit the border-radius from the parent, you can use the inherit value like this border-radius: inherit so that it takes the border-radius of it's parent without have to type it.

    Also you can consider using properties like the following together with border-raduis: unset;

      border-bottom-left-radius: 2rem;
      border-bottom-right-radius: 2rem;
      border-top-right-radius: 2rem;
      border-top-left-radius: 2rem;
    

    this way you can unset the value and specify exactly where you need the radius without having to do something like border-radius: 0 0 0 0;

    I hope this feedback helps.

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