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

Blog preview card using Flexbox

bem
P
Raul Galicia•230
@raulgaliciab
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?

Proud of the (almost) pixel-perfect implementation, the BEM classes and the use of Flexbox.

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

I still struggled with how to justify and align the elements—especially the text. It was basically trial and error until I found the correct way. In some cases the problem was the display.

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

Should I need to use media queries for the responsive design?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vasu Vallabh•190
    @coding-vasu
    Posted 12 months ago

    Overall Looks Good !

    Feedback on Your Solution

    Accessibility

    • The alt tag is blank for the "Card-autho" image. Always include descriptive alt text for images to improve accessibility.

    Font Size

    • You've set the base font size to 62.5%, which results in a 10px base font size.
    • While this works for this project, it may cause issues when:
      1. Integrating design system libraries
      2. Following general web standards (16px is typically used as the base font size)

    Interactive States

    The following interactive states are missing from your solution:

    • Tab index
    • Focus state
    • Hover state
    • Active state

    Consider adding these to improve user interaction and accessibility.

    Responsiveness

    • The challenge specifies that font sizes should be slightly smaller on smaller screens.
    • To achieve this, you can simply update the base font size to a smaller value for mobile breakpoints.
    • Your current solution doesn't adapt the font size for smaller screens, affecting its responsiveness.

    Tip

    Use media queries to adjust the base font size for different screen sizes. This will help make your design more responsive without needing to change individual element sizes.

    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

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