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

Single price grid component

vite
Reza Jaber•200
@rezajaber
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey! I am Reza 🙂 I just recently started to learn web-development and would like to get every little help out there. So if you have the time, feel free to look over my project/projects and give me some advice to get better as fast as possible.

Project #10: Some questions for this "Single-Price-Grid" project:

  1. Did I center everything right, or was there a easier way?
  2. Was there a easier way to design some things in way less code?
  3. What did I do completely wrong, and just have luck within this project?
  4. What would you do different?

I appreciate it✌️

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gregório Francisco•235
    @gregoriofrancisco99
    Posted over 2 years ago

    Hello, Reza! Gotta tell you, loved your solution. And the comparison screenshot speaks by itself! Congratulations! Even tough the design looks really good, I took a look at your code and I will raise some points.

    You should try to wrap all your main content inside a <main>.

    And if you have more than one <section> you should consider wrapping them inside an <article>.

    <h1> are the top level heading in a page, and there should be only one of it. and <h2> is what follows it on the heading hierarchy. Clique here to get to know them all (from <h1> to <h6>) and what are they meant for.

    And I saw you used a <button> for the sign up. And it's not really wrong, but for me, I think you should use an <a>. Because it seems it will take the user somewhere else, or open some other content.

    I saw you used an <ul> for the last card. That was awesome!!! 🎉

    Well, those are my comments for this solution. And remember... Keep 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

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