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

Only basic CSS, using Flexbox

Ozan GOKDEMIR•50
@ozangokdemir
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi I'm Ozan,

It's my first exercice to use what I recently learned about HTML/CSS. I'm trying to get good habits starting now, for example by trying to use SMACSS methodology.

I'm pretty satisfied with the result I get, but I didn't manage to stick my footer line to the bottom of my box without moving it when resizing my window in landscape mode...

I will take any advice on this, every remark you can do will help me !

Thank you

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, great work on this one. The layout both desktop and mobile is good and it responds and scales very well on screen changes.

    Also, great that you adopting certain methodologies, although I don't know what is SMACSS but hey, if you got it, that's really great.

    Some suggestions would be:

    • Always have a h1 element on a webpage. On this one, the h1 would only be a screen reader text. It might seem new to you, but this is intended for screen reader users. The h1 element would look like:
    <h1 class="sr-only">Frontendmentor car collections examples</h1>
    

    The sr-only class is just a css stylings, you can search some up in google. This h1 would be the first text element inside the main.

    • Avoid using height: 100% or height: 100vh on an element. This will make the element's height limited to the viewport's height. On your body and main remove those css styling. That is a bad practice. Instead, on your main element. Add these:
    align-items: center; # centers the content vertically
    min-height: 100vh; # makes sure it have necessary height and will expand
    
    • On the section elements, you don't need to use transform on those element. Let the main flex container centers them properly, just add padding to a certain parent element.
    • An a tag doesn't have a type attribute. Remove those, button element and input have those.

    Overall, it looks good. Great work again.

    Marked as helpful

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, SASS, 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