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

Four Card Feature Section

pheight-89•250
@pheight-89
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 am most proud of learning how to use Tailwind CSS v-4 as it is the first time I have used Tailwind in general

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

Working with the Tailwind framework. The setup was pretty straight forward. However, I had a hard time added the custom colors, and grid layout with Tailwind. However, after reading Tailwind documentation I was able to work through the issues.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Weyehn Reeves•190
    @WeyehnR
    Posted 3 months ago

    🌟 What’s Good:

    • Clean Structure: The project is organized well. The use of folders for images and a clear naming of files (like style.css, index.html) is a nice touch.
    • Semantic HTML: The HTML seems to use proper tags (section, h1, p, etc.), which helps with accessibility and structure.
    • Visual Consistency: The layout appears clean and aligned well with the original challenge design. Spacing and typography look well-balanced.
    • Responsive Effort: There’s an attempt at responsiveness (which is key for any front-end project). The layout doesn’t completely fall apart on smaller screens.

    🔧 What Could Be Improved:

    • More Comments: Adding some comments in the CSS would help readers (and future you) understand the layout choices faster.
    • Mobile Optimization: While there's some responsiveness, you could enhance the mobile view a bit more — maybe stack the cards vertically or adjust the padding/margins for better spacing.
    • Class Naming: Consider using more descriptive class names (.card-wrapper vs something like .container-2). It helps others understand what each class does at a glance.
    • Alt Text: If there are images, make sure alt attributes are filled meaningfully — this helps with accessibility and SEO.

    💡 Suggestions:

    • Try adding a little hover effect on the cards (like a subtle shadow or scale-up) for better interactivity.
    • Look into using CSS variables for colors and spacing if you’re planning to expand this — it makes maintenance much easier.
  • Shakiba•130
    @Shakiba-Alipour
    Posted 3 months ago

    Good job!

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

Oops! 😬

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

Log in with GitHub