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

VS Code, Chrome, Stack Overflow, Favicon Generator

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

Solution retrospective


Hello,

I'm struggling with how the page responds to the web page being reduced. I think it may be down to my use of PX vs REM/EM/% but confirmation of this would be appreciated.

This is my fist attempt at building a feature page without a tutorial on Udemy or Youtube. Any feedback on how I should continue/ progress my learning is appreciated also!

Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yasmina S•110
    @yvsminvs
    Posted over 4 years ago

    Hi Craig!

    Congratulations on your first attempt, it looks pretty good!! You can also try to do it for desktop using media queries and, in this case, CSS Grid :)

    I checked your code and I'd suggest you to remove the width and the height assigned to these boxes. Instead, use min-width and min-height.

    When you assign a determined width/height you are fixing these values. That's why when you reduce the page, the boxes don't ''shrink''.

    Hope it helps you!

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