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

single price grid component (mobile first)

Pierre Fraisse•330
@PierreFrs
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Beginning to figure out responsive design. Just a question : what is the most important ? Getting as close (pixel perfect) to the design as possible or having an easily manageable code (with as few media queries as possible) ? The too things seem a bit antagonist.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dusan Brankov•860
    @dusan-b
    Posted over 2 years ago

    Hi Pierre,

    When building a web page, it's important to follow the most essential design guidelines like colors, fonts, sizes and spaces. They are designed a certain way with a specific purpose, be it functional or aesthetic. However, with so many devices and browsers, rendering websites differently, it is actually impossible to create a consistent look and feel. I think it's more reasonable to build a web page wich is fairly close to the original design.

    Joshua Comeau has written an interesting article about it you may find interesting:

    Chasing the Pixel-Perfect Dream

    As far as your code is concerned, you should avoid skipping heading levels and only use them if it really is a heading that indicates a new (sub)section. Otherwise it would cause confusion to screen reader users who are used to navigating through the headings of a page.

    I would consider something like this:

    <section class="community container">
      <hgroup>
        <h1 class="main-heading">Join our community</h1>
        <p class="guarantee">30-day, hassle-free money back guarantee</p>
      </hgroup>
      ...
    </section>
    

    Also, the text right after the "Why us" heading is actually a list of reasons why one should choose the company. Therefore, the paragraph should be transformed into a list using the elements <ul> and <li>.

    I hope I could help. Keep going, and 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
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