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

Blog Preview Card

P
Emanuel Barcenas•170
@eman2point0
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shanxx191919•60
    @Shanxx191919
    Posted 9 months ago

    The HTML structure is good overall, using semantic elements like <header>, <main>, and <footer>. However, you could improve accessibility by adding more descriptive alt attributes to the images and using aria-labels or role attributes for better screen reader support. Consider adding more semantic tags like <article> or <section> for improved SEO and readability.

    For responsiveness, the layout is flexible due to the use of flexbox, but you might want to add media queries to fine-tune the layout on smaller screens, especially adjusting the card width and text size. The code is clean and readable, but splitting the CSS into a separate file could improve maintainability, particularly for larger projects.

    Marked as helpful
  • Felipe Mata•250
    @BoxyPipesnake
    Posted 8 months ago

    Hi! Great job on your project!. I did notice a small issue when viewing it on mobile: there’s a bit of horizontal overflow, which causes a slight scroll.

    One way to fix this would be to adjust the .card class. Instead of using width: 384px, try using max-width: 384px. This allows the card to shrink appropriately on smaller screens. Additionally, adding margin will give it some breathing room on the sides, keeping it from touching the edge of the screen.

  • Rodolfo C•80
    @rodolfohgc
    Posted 9 months ago

    Hello, Emanuel!

    Your solution was nearly there, but I recommend some enhancements:

    The border radius and shadows on the card are significantly smaller in your rendition. Please refer to the Figma file, which contains a comprehensive design system; it will provide you with additional details such as colors and font styles. Rather than using the <h2> tag, it would be more semantic and appropriate to use <h1>.

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

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