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

CSS flexbox and BEM methodology

Ramiro Solano•35
@ramirisho
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


Second project that I do, I will appreciate any advice, criticism and recommendation :D

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jonathan•105
    @JonMStevens
    Posted almost 4 years ago

    Hey this looks good so I'm just going to point out some small details about the button links that you could look at if you want.

    1. the hover states look to be sharing a few style properties. You could group these in one selector that they share so that you can easily change them all at once. The selector could be something like ".container-columns a:hover {" and contain all of those shared properties.

    2. the hover states seem to overwrite some of the properties on the anchor selector, even though they aren't changing the value. For example the anchor selector and the hover selectors both have: height: 47px; width: 150px; You don't need rewrite those properties.

    3. On hover the borders on the buttons seem to pop into place suddenly at the end of the transition. In my opinion this could look smoother if: they weren't included as part of the transition, and instead the transition was something like "transition: 500ms background-color ease-in" so only the background-color was part of the transition. OR you could outline the buttons with something that isn't part of the box model and won't take up space on the page like a box-shadow.

    Hope this is helpful, and thanks for your response on my project.

    Marked as helpful
  • Erick F. Felix•265
    @efs0-cod3
    Posted almost 4 years ago

    For the html issue you should have you div’s inside a main tag (landmark).

    Looking pretty good on desktop view.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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