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

Simple price grid component using html and css

Paras Sharma•700
@imparassharma
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Can this be done in more efficient way?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rafal•1,395
    @grizhlieCodes
    Posted almost 4 years ago

    Yes it can!

    First of all, great question. I don't see people asking if something can be done more efficiently, something I'm a big fan of, I learn how to make code more efficient daily. So in my opinion - great attitude 👍

    It can be much more efficient. This is looking like an 'older' way of positioning things. The newer technologies CSS offers us are:

    1. Flexbox
    2. CSS Grid

    Edit: I did see you used display: flex; but I don't think you understood its power in this attempt. So hopefully the below helps a little.

    Both are necessary to learn in my opinion so you're safe focusing on either. I'd say learn Flexbox first though as you can get most simple layouts done quite quickly with it. Grid is amazing and gives you insane control but it's for (optionally) more complicated layouts.

    AS to how exactly can this be done more efficiently:

    You positioned a lot of things 'absolutely'. This is unnecessary in a layout like this. It's unnecessary in most basic layouts actually. I wrote up a super simple example of how to position this with flexbox.

    I did not give the bottom 2 flex-items identical widths to illustrate how you can use flex-basis to style things a bit better.

    Further resource is Kevin Powell, a great teacher and YouTuber. I actually am doing a course on Flexbox from him (1 year after I learned flexbox I'm still learning new stuff about it...)

    I would write more things but I don't want to 'word-vomit' here. Have a look at what I created for you and ask any questions you'd like. Awesome start, I hope to see more solutions from you in the future.

    Marked as helpful
  • Paras Sharma•700
    @imparassharma
    Posted almost 4 years ago

    Thank you for taking out time and helping me out. It means a lot to me and yes you are right I know a very little about flexbox actually I took the Angela's webdev course & later found out that there is much more for positioning so I think & also by your suggestion, I should first study about it more. I looked at your codepen example and it was so exciting that I can do that type of layout more efficiently all thanks to you.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub