Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 5 years ago

Mobile-first solution using CSS Grid

Simon Hernandez•615
@simonhernandez
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Guys!

I would really appreciate some feedback on the HTML Markup of my solution.

If there's a more Semantic way of marking up this component, please let me know so that I can improve my HTML skills. Thanks so much in advance!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mark Mitchell•1,820
    @markup-mitchell
    Posted almost 5 years ago

    Hi Simon. This is a really close implementation of the design!

    I don't claim to be an expert on HTML semantics, but from my own experience and research here's what I'd suggest:

    Imagine there was no styling whatsoever - what would this information look like in, say, a MS word doc?

    You'd probably want "Join our community" to be your main heading (<h1>). You should have exactly one <h1> on a page.

    It's great that you're using <section>s, but you only have one and it's immediately inside <main>, so at best it's serving no real purpose, and at worst it could be confusing because one section implies the existance of others (which there aren't!).

    I would make the outermost div of each box into a section tag and give it an appropriate heading level:

    h1 - join our community h2 - monthly subscription h2 - why us

    I wouldn't make "30 day..." a heading because it doesn't directly relate to the content beneath it. Just because text is big, bold or eyecatching doesn't mean it's a heading! It took me ages to decouple those in my head!

    Lastly, I'd be tempted to represent the content in the 2nd and 3rd sections as unordered lists, since they'd make more sense that way than as prose.

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