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

Pure HTML css Four card feature section solution

Thomas Burette•190
@tburette
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Root and default font-size

Instead of setting the font-size to 15px (as mentionned in the style guide). I used 16px*0.9375 = 15px.

:root {
    font-size: 0.9375rem;
}

I use a value relative to rem that equals to fifteen if the default font size is 16px instead of 15px directly. I do this to take into account the default font size set by the user agent. It is 16px by default but user may override that value in browser settings.

It allows to take into account the wish of a user to have smaller/bigger text

Not setting font-size on all header elements

I set the font size for h3 but use default UA style for h1 h2.
It works where I tested it but it could be a problem : a user agent could have values that make h2 bigger than h1 or h2 for example. A safer thing would be to define it explicitely for h1 and h2

h3 {
    font-size: 1.3em;
}

max-width on content instead of fluidly increasing the margin

In the last challenge I did. I used a system where the margin slowly increase as the viewport widens.

This time I just set a fixed margin. There is a maximum width for the content. It is only when that max width is reached that the margin increase.

It is simpler at the cost of being slightly ugly when the viewport is wide but not wide enough to have reached the max width of the content.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Thomas Burette's solution.

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.