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

Responsive single page price grid

bootstrap
Kritika•20
@11Kritika11
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 try my best to make it responsive as i can, i guess everything is almost fine i just have a mini problem with button shadow.It would be great if any one can help me with that

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lord Robins•610
    @ZenitsuAg
    Posted over 2 years ago

    Hi Kritika, you've done a great job and your code is responsive. Some tips to help you improve your code.

    • It's better to wrap the entire code in a main tag for accessibility purposes
    • Also, the entire code cover the entire screen so we can't really see the body tag. We can change this by setting a width value maybe to 80% or something else, depends on you.
    • Heading tags should also increase in a logical order, that is h2 after h1, h3 after h2 like that. This is because of screen readers to make the page easy to navigate. You can read more about it here.
    • Then you can center it using CSS Flexbox with this code body {display: flex; justify-content: center; align-items: center} and that's it.
    • For the button shadow, you can solve that by using the box-shadow property. So something like box-shadow: 0px 6px rgba(0, 0, 0, 0.2) should do it, but feel free to edit it as you want. -Also in the "Why us" section, you should use a separate p tags for each item.
    • In your CSS where you called body, h1, h2 etc to remove the margins is okay but preferably you can use the universal selector to do it. Like this
    * {
    margin: 0;
    }
    

    Overall you did really well.

    Happy Coding :)

    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