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

css and html

Langlois Titouan•80
@LostProcessor
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 challenges did you encounter, and how did you overcome them?

i was not sure how to do this kind of design which looks like a cross, i used a tool to find the right grid layout and it was it .

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

i'm not sure that my mobile version is good , any suggestions or critics are welcome

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • KennethVelazquez•170
    @nadielotiene
    Posted 2 months ago

    Hello Langlois, most of the design looks good and the code looks clean and organized but there are some issues:

    1. Make sure you use the right tags for sections like the header, main, sidebar, footer, etc. for accessibility and screen readers. Make sure you check the markdown report on the code preview page, and read the articles on the issues, they are very helpful.

    2. The text on the header is missing the right font even though is in the main section. The "Reliable, efficient delivery" font needs to be thinner. The header is also missing padding on the sides.

    3. You need to add some padding on the cards, the contents are too close to the edges.

    4. You need to eliminate the viewport width vw on the containers to avoid side scrolling, use percents % IF you have to.

    5. On the desktop layout you need to use max-width to control how wide you want the cards to be.

    I can't recommend enough Kevin Powell's Conquering Responsive Layouts, It has helped me so much, and I understand everything so much better.

    Congrats on completing the challenge, have a good day and keep on coding!

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