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

Responsive card component using CSS Flex and pseudoclasses

Marcos Valenzuela•100
@MarcosAvg
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I liked the use of flexbox for the layout from the container to the child elements, sectioning with BEM.

What challenges did you encounter, and how did you overcome them?

In the author element, I found that I could not reduce the size of the image with flex-shrink. I solved it by putting the image in a and it could be reduced without problems.

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

I would like help with CSS structure. I use Flex and utilities, but I am not clear if I have omitted some good practice or if it can be optimized in some way.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Luiz Felippe•80
    @luizfbn
    Posted 9 months ago

    Good solution. I found some stuffs that you can improve.

    About HTML:

    • You can wrap your img with figure tag: https://www.w3schools.com/tags/tag_figure.asp
    • Inside content section, you can wrap the learning stuff and the publish date inside a header;

    About style:

    • The card shadow needs to be bigger;
    • On card hover, the shadow needs to expand (you can see this on Figma's prototype presentation) and cursor needs to be pointer;
    • The typography needs to be reviewed. For exemple, the card content paragraph have wrong font weight.

    Tips:

    • Always check if your solution is responsive, it's very important;
    • Avoid using width and height based on percentage, it is very situational and if you don't use wisely, this can break your style on different screen sizes;
    • Flex it's an awesome tool, but you don't need to use on everything. For this design, for example, you could use only blocks and inline blocks elements and you could be fine.

    Good job and keep studying! :)

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