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

My solution

Yuniac•65
@Yuniac
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 and all feedback is welcomed. I don't think I got the colors quite right and perhaps the height isn't like the design but I tried to make it as close as possible. And one thing I noticed is the preview here isn't accurate for some reason, but feel free to view it live.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Szymon Rojek•4,540
    @SzymonRojek
    Posted over 4 years ago

    Hi Yuniac,

    Good job! :D

    I have checked your project by the inspector, a few tips for me:

    • remove this <div class="container"> and create the main tag with the class;
    • generally you have used so many unnecessary nested divs (try to change it);
    • inside of the main tag I could use the section tag, and then three divs for these three boxes;
    • about this code below:
    div class="wrapper sub-price"><span class="dollar-sign">$29</span><span id="permonth">per month</span></div>
    

    Instead of this div you I'd recommend using the p tag with two spans (ID's are unnecessary here => it is good to use them with JS); Below will be the *p tag with this text: Full access for less than $1 a day

    • what do you think about the link instead f a button? (this on click doesn't have to be here);
    • third box: Why us => you can use the h2 tag;

    Design:

    • check your project on different devices by the inspector in your browser, there is lots of to do: play with the size of the text, margin (especially the top, right, left), padding, the footer;
    • text in the first box: these two paragraphs under the green color text should be on mobile treat as a one text but later you can get this solution => separate sentences one under each other;
    • per month: color of this text is not very well (check the design file);
    • this is single page component so you can add overflow hidden to the body (eliminate the scroll);
    • the bg-color of the third box: I gave them the same color for the second and third box but additionally I have added pseudo-element after to the third box with the gray color => I called it "overlay";

    That's from me.

    Greetings :D

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

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