Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 4 years ago

Four Card Feature Section

Eugene Goh•10
@AlexChann
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Tell me what do you think about this project? Your feedback is much appreciated. Feel free to open up an issue if you find anything wrong. Have a good day.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Folarin Akinloye•1,240
    @folathecoder
    Posted over 4 years ago

    Hi Eugene!

    Cool attempt, keep it up! I can tell this is your first challenge on frontendmentor.

    For easy implementation, always use the index.html file provided in the zip file because it has all the details you need to get started, like:

    1.) The text content 2.) The copyright text at the bottom of the page, etc.

    It will save you valuable time!

    Also try to make sure your implementation closely resembles the mock-up on both desktop and mobile.

    When you are done coding, compare your design by placing it side-by-side with the mock-up to know if it is visually === .

    On mobile - You need padding on the left and right sides, to prevent the cards from touching both sides of the screen. Also, take note of the font colors, and font sizes.

    Your font size across all devices ought to be different. (e.g, Desktop (2 rem), Tablet (1.6 rem), Mobile (1.2 rem)). Your font size must be relative to the screen!

    I only viewed it on my phone, so I only have a mobile feedback. 🙂

  • Loris DUCAMPS•425
    @LorisDucamps
    Posted over 4 years ago

    elements positioned with 'relative (top: 'number'px etccc) or absolute or float' are no longer part of the vertical rhythm and therefore can potentially overlap at resize. that's what I wanted to explain

    when you resize your browser, img elements go out of their containers

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