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

Four card feature section using Flexbox and Grid

Tatyane Gonçalves•520
@tatyanepgoncalves
A solution to the Four card feature section 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?

Esse projeto foi realizado usando Grid que é um tópico que ainda não tenho prática. O resultado ficou um pouco parecido com o da imagem.

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

Minhas dificuldades foram em grid-template-columns e grid-template-rows.

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

Gostaria de dicas de como organizar melhor os elementos utilizando os comandos acima.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • DNel2•210
    @TechEdDan2
    Posted over 1 year ago

    Perdón por escribir en inglés, pero deberías poder utilizar el traductor integrado de Chrome.

    I used Flexbox to create my project, so I do not know how helpful I can be with grid... I am also learning to be more comfortable with it, too. I tried experimenting with your .team{ grid-row: 1; grid-column: 2; } and .karma{ grid-row: 3; grid-column: 2; } class selectors, but couldn't get the centering of the cards to quite work. Have you checked out https://css-tricks.com/snippets/css/complete-guide-grid/ as a resource? I also really liked watching Kevin Powell's videos, like: https://youtu.be/8QSqwbSztnA?si=_a5qbm0rswUVVAXr or https://youtu.be/rg7Fvvl3taU?si=cHi2dcHCp6OotGjD where he goes over a Frontend Mentor Project using grid. Good Luck!

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