Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 3 years ago

attempting to use css grid :D

Khadija Hashmi•200
@khadijahashmi2
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


any feedback will be much loved! and i'll give you a cookie 🍪

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ahmed Bayoumi•6,700
    @Bayoumi-dev
    Posted about 3 years ago

    Hey Khadija, It looks good!...

    My suggestions:

    • Document should have one main landmark, Contain the component with <main>.
    <main>
       <div class="container">
          //...
       </div >
    </main>
    
    • Page should contain a level-one heading, Change h2 to h1
    <h1>Join our community</h1>
    

    You should always have one h1 per page of the document... in this challenge, you will use h1 just to avoid the accessibility issue that appears in the challenge report... but don't use h1 on small components <h1> should represent the main heading for the whole page, and for the best practice use only one <h1> per page.

    • Also, I suggest you center the component on the page, by giving the parent element <main> the following properties:
    main {
       display: flex;
       justify-content: center;
       align-items: center;
       min-height: 100vh;
     }  
    
    .container {
        width: 350px;
        /* margin: 0 auto; */   <--- Remove
        //...
    }
    

    I hope this is helpful to you... and I want a cookie 🍪

  • Abdul•8,560
    @Samadeen
    Posted about 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="container"> instead of <div class="container">.
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <p>Join our Community </p> should be <h1>Join our community</h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    This should fix most of your accessibility issues.

    • You can use flex or grid to center your container horizontally and vertically.

    . Regardless you did amazing... hope you find this helpful... Happy coding!!!

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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