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

Responsive Single Price Grid Component using HTML, CSS

Anisha Singla•55
@anisha463
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 appreciated :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Agata Liberska•4,075
    @AgataLiberska
    Posted about 4 years ago

    Hi @anisha463! Well done on this challenge, it looks great and it's very nicely responsive. I would just suggest adding a max-width to the card so that it doesn't stretch too much on big (big) screens.

    One thing that I think could be worked on is the way you use heading elements. Headings in general should make sense in the hierarchy of the document. So here, the main heading of your card is 'join our community' and not really the price of the subscription, even though the price font size is bigger. I realise that this can be confusing since the default browser styling shows h1 as the largest, h2 a bit smaller etc. but try to look at the logical structure of the content, you can always change styles with CSS.

    I just came up with this wild metaphor that you may find helpful:

    Think about your page or component like it's The Lord of the Rings - that's h1, the main title. Then you've got parts - so The Fellowship of the Ring, the Two Towers and The Return of the King would all be h2. Chapters within those parts - h3. Titles of scenes within those chapters would be h4. If you wanted to divide those scenes into smaller parts and give those titles, that would be h5. You get the gist :)

    Here's an article talking about why getting the headings right is important

    Hope this helps, let me know if you have any questions :)

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