Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Single price grid using grid

Letícia Fernanda•190
@Leticiafbm
A solution to the Single price grid component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am proud of how I used grid and of understanding better the measurements.

What challenges did you encounter, and how did you overcome them?

I had trouble making the website be responsive.

What specific areas of your project would you like help with?

I need help making it responsive.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Peter Wahu•290
    @Pe-te-r
    Posted about 1 year ago

    Hey buddy, about your question on making it responsive, you don't have to rewrite css for every media screen. You can always adjust the display mechanism for each box. You could have displayed using grid where the top box-1 takes a span on two columns and the other two boxes share each it's own column, then on responsive you just adjust what each box has two occupy. Try researching more about grid display system, it will be a better choice.

  • Bernardo Poggioni•6,770
    @R3ygoski
    Posted about 1 year ago

    Olá novamente Letícia, primeiramente, parabéns pela conclusão do seu projeto.

    Abri um issues desse projeto lá no Github, pra poder dar algumas dicas quanto ao seu projeto. Eu também respondi sobre a parte de responsividade, e refiz alguns trechos do seu CSS, recomendo humildemente que dê uma olhada.

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