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

Single Price Grid Component - HTML/CSS

P
Julie•150
@jclegg31
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Getting a bit easier, would love feedback on how to improve code. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rebecca Padgett•2,100
    @bccpadge
    Posted over 1 year ago

    Hello @jclegg31. Congratulations on completing this challenge!!!🎉

    Your solution looks really good and I have few tips you might be interested in to improve your solution.

    • On smaller devices your component is cut off due to height:100vh; and to fix the issue you can do min-height: 100vh; on the body
    • Also you can add spacing using padding and margin

    Updated code below

    body {
        font-size: 16px;
       /* height: 100vh;*/
        max-width: 375px;
        display: grid;
        align-content: center;
        margin: 0 auto;
        background-color: var(--clr-lightgray);
        min-height: 100vh;
        padding: 1rem 0; 
        margin: 0 1rem; 
    }
    
    

    HTML 📃:

    • I see that you wrapping everything in div which isn't good for accessibility. A div doesn't have any semantic meaning.

    More info📚:

    • HTML Semantic Elements

    CSS 🎨:

    • Font size shouldn't be in pixels because pixels are absolute unit and doesn't scale when users want to change their font size in their web browser setting.

    More info📚:

    • Font size shouldn't be in pixels

    Here is my solution to this challenge Single price grid component using Tailwind CSS

    Hope you find this useful and don't hesitate to reach out to me if you have any questions

    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
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