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

Four card feature section

sass/scss, vite
Darek•140
@DarekRepos
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?

i created flexible font sizes (fluid typography) and media queries. I used Flexbox and CSS Grid. Next time, I will use more JavaScript to my solution.

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

The challenge I encountered was combining grid with Flexbox to achieve the most optimal solution. I believe I chose a very flexible approach.

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

I want to learn more about Dynamic Component-Based Architecture. Is my solution with Flexbox and Grid the optimal one? There's definitely still a lot to learn in this area. If you have any suggestions for improvement or find any mistakes in my code, please let me know. I'd be very grateful for the feedback!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Erratic Enigma•200
    @erratic-enigma
    Posted about 1 year ago

    Hello, nice job on the project!

    The card grid on the desktop viewport sizes looks good, but at smaller viewport sizes (such as around 590px), the cards reach their minimum width and cause horizontal scrolling. You could either reduce the minimum width of the cards, or increase the media query width to around 650px.

    A few other points:

    • On small viewports, the heading text needs to be center aligned.
    • I would recommend using em units for media queries; here's an article that covers why.
    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