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

Single Price Grid Component

Canti•110
@Canti21
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I think the result is ok, but... How can I center both horizontal and vertical an element (div for example) the most optimal way? (If possible without using flex, grid or position)

Anyway, any feedback, comment or question is welcome :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hey, Canti! 👋

    Congratulations on finishing this challenge! 🎉

    You have an interesting question. I never thought about how to center a div without using flexbox, grid, and position property. So, I did some research and it turned out that it is possible. You can use display: table to do it. But, keep in mind that I have never tried doing this so I am not sure it will work well. (reference: https://www.tutorialstonight.com/how-to-center-a-div-in-css#using-display-table-cell-v)

    But, I would recommend using either flexbox or grid. It's a more robust solution to center the card and also both have good support.

    • CSS Grid Layout | Can I use
    • CSS Flexible Box Layout Module | Can I use

    So, there is no reason to not use flexbox or grid. 🙂

    Taking a look at your solution, you use flexbox to center the card. However, I would prefer making the body element as the flex container and then making the main element as grid container.

    You can set the flex-direction to column to make the attribution below the card. For the main element, you can use grid-template-column to control the layout of the card.

    That's it! I hope you find this useful! 😊

  • ...•600
    @HatimHJ
    Posted almost 3 years ago

    This comment was deleted almost 3 years ago

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

Oops! 😬

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

Log in with GitHub